This is a follow-up notice for the deprecation of the pre-transition trigger runtime which is planned for deprecation in LTS14. Prior to LTS11, users were allowed to have more than one transition trigger as part of an if/then clause which could cause problematic behavior.
You may have seen this image in your Tulip Instance urging you to migrate any apps with this faulty logic.
In most cases, Tulip will be able to remediate the issues automatically. Please read this KB article for additional information, post any questions below or contact your Tulip representative with any questions.
It maybe better if our message also notify that the app would not be runnable anymore.
I know the support was deprecated, but we were using the Apps at our own risk.
Since I now know that you have a plan to archive the Apps (and it cannot be unarchived), we will start considering the migration plan more seriously.
Is there a way to find out which App still need republishing? (I know we have “Warning” folder but the App disappeared from that folder only by “Convert”ing it.)
What will happen if we do republish after converting but try to run the old version of the app.
What will happen if we do republish after converting but we try to restore the old version.
There isn’t a way to see converted apps that haven’t been published.
The old version is still migrated and is forced to run under the new transition runtime.
The old version is still migrated and is forced to run under the new transition runtime.
Old versions will still exist and be viewable, but transition actions in triggers for example are coerced into the proper ordering. Essentially, this is a warning to convert over and identify any key issues that we can’t automatically resolve.
You would not need to republish before converting - our recommendation is that you convert then publish the latest version.
The main risk that we’re seeking to help mitigate here is twofold:
For triggers that we can automatically migrate, you are aware of the change so we aren’t changing apps in production without warning.
For triggers that we cannot automatically migrate, you decide what the desired behavior is before we forcibly change them and create undesirable behavior.
Hmm… It is still unclear to me why we need to republish all those Apps.
Anyway, I believe you. We must convert+republish all the Apps until LTS14 (if we want them to be still runnable).
In that case, we have a problem.
There isn’t a way to see converted apps that haven’t been published.
Many users already converted their Apps several months ago, without knowing that they had to also republish the Apps after conversion.
Please could Tulip provide us a way to get the list of Apps which haven’t been published after the conversion ?
The risk is that the logic hasn’t been properly saved and that some of the logic isn’t automatically translated properly.
If you’d like to get the list of Apps that have been converted, please message me the name of the instances and I can get you that list of all converted apps (it includes both published and unpublished).
