Custom IML functions have been disabled for all customers and partners. We needed to take this action in order to address a potential vulnerability and, out of an abundance of caution, prevent any potential malicious actor from exploiting it.
On this page you can learn more about what can be your next steps.
What actions will Make take to resolve the situation with disabled Custom IML Functions
We are gradually migrating apps onto a new improved version of the platform. This process is mostly invisible to end users. We will re-enable custom IML function editing for an app once all its modules have been migrated in all scenarios.
Most apps can be simply migrated without any further user action required. In some cases, though, the migration may result in a potentially breaking change (example: a data type of a particular field might change after the migration). If such an app was used in an active scenario, it could produce a somewhat different output after the migration. Therefore, we won't be migrating such apps automatically.
These are the next steps we take in Make to re-enable custom IML functions and ensure their compatibility for affected apps:
All new apps run on the new technology. Only new apps have the custom IML functions enabled (provided that the developer has the permission to use custom IML functions).
Switch all compatible apps to run on the new technology and re-enable custom IML functions for them.
Gradually migrate scenarios containing remaining incompatible apps to the new technology if there are any. Users may be asked to test and migrate their scenarios on the new technology.
Gradually switch the rest of the apps to run on the new technology and enable custom IML functions editing for them.
Which apps are compatible and which are incompatible
Compatible apps produce the same results and behave the same way on both the old and new technology.
Any new apps will be automatically compatible with the new technology, as well as apps with no custom IML functions.
Incompatible apps use custom IML functions that modify input parameters. Support for such functions is different on the old and new technology, producing different output in the scenarios in certain cases.
We are continuously improving the detection of the custom IML functions which are incompatible with the new technology. It might happen that some functions (and with that, apps) Make marks initially as incompatible, but can end up being classified as compatible later (we are taking the safer approach).
When Make enables custom IML functions for my Make app again
Compatible apps
As soon as Make determines that an app is compatible with the new technology, Make switches that app to the new technology and enables custom IML functions.
Incompatible apps
If there are any apps which remain incompatible when we are finished with improving the detection mechanisms, we will update the information on what will be done in their case.
What are the options to re-enable custom IML functions sooner
Make a copy of your app
When you make a copy of your incompatible app, your copied app will be using the new technology automatically in all scenarios. Make will consider the copy as a compatible app and enable the custom IML functions for the app. The copy is intended for you to test the app and check if the IML functions work as intended.
Once you test the app and make changes if necessary, you can request updating the original, incompatible app with the code from the compatible copy of the app. To request the update, create a ticket to update custom IML functions for the app.
Enforce use of the new technology for your app
If you control the use of your app (e.g. it's only in your scenarios or in scenarios of customers you know), we may decide together to enforce use of the new technology for your app. That would make your app compatible. It would also likely break some of the scenarios or make them unreliable. This is not preferred and would be considered an edge case.
Last updated