When we have defined some conditions in an Event action they work fine in the environment in which they were defined. But when they are exported and imported again as an ACP, (as xml files or a Zip file) we’ve noticed that the conditions stops getting evaluated and the Actions are run regardless what is in the conditions.
For example, say we have below event action with below condition, and it was created by importing it from an ACP. Then despite what is in the condition it will execute what is in the Action Details.
However, if you open this event Action in the application and do a fake modification to the Condition and do a re-save the issue is gone and the Events are only executed if the conditions are satisfied.
When investigating further we realized that this is due to a discrepancy in the NEWLINE character when Event Conditions are saved in the database. When importing the ACPs through an xml it saves the newline characters in the Condition_type and Condition_Value fields as ‘\r\n’ (CHR(13)CHR(10)) characters, because this is how it appears in the xml file.
But in the Event_sys and Fnd_Event_Action_API logic when extracting these condition_Type and Condition_Value attributes its expecting the NewLine character to be just CHR(10). Because of this it always return TRUE to event Condition evaluations and runs the Event always.
This issue is in IFS Applications 10 UPD14, but when I check this with an IFS cloud application 23R2 the issue isn’t there because there the exported xml file has NewLine character as ‘\n’ (CHR(10)) and therefore doesn’t have this issue.
Does anyone know how to resolve this in Apps10 and is it something resolved in a later Applications 10 Update?
Thank You!