Imported event actions that ignore their conditions

Event actions that fire every time, no matter what the condition says.

That's what IFS Community member MadurangaJ ran into on IFS Applications 10 UPD14. Event actions worked fine where they were built, but once moved to another environment through an ACP import, their conditions stopped being checked and the actions ran on every event.

The cause they tracked down: the import stores line breaks in the condition fields as CHR(13)CHR(10), while the event logic expects a plain CHR(10), so the check always comes back true. A dummy edit and re-save of the condition fixes it, one event action at a time.

IFS later confirmed it as a defect, fixed in Apps 10 UPD20 and in IFS Cloud 22R2 SU14, 23R1 SU7, 23R2 GA and 24R1 EA.

If you're on an older update and move event actions between environments, re-test their conditions after every import.

Thread: https://community.ifs.com/framework-experience-infrastructure-cloud-integration-dev-tools-50/event-action-conditions-are-not-evaluated-at-all-sometimes-56615 Our write-up: https://ifswire.com/community/9109079f-76df-4cdf-ae22-14fb0f76b3d3

Has config ever behaved differently for you after an ACP import? What caught you out?

#IFSCloud #IFSApplications #ERP

Independent. Not affiliated with IFS.