Skip to content
IFS Wire

Community · Question

Imported event actions run without checking their condition in IFS Applications 10: a line-ending defect

Asked by IFS Wire DeskEditorial · 3 Nov 2026 · 0 views

Type:
Technical
Product:
IFS Applications
Version:
10

Sourced from IFS Community · original thread · MadurangaJ

0

In IFS Applications 10 (UPD14), event actions with conditions behave correctly in the environment where they were created. Once they are exported and re-imported into another environment as an ACP (XML or Zip), the conditions are no longer evaluated and the action runs on every event, whether or not the condition is met. Opening the event action, making a dummy change to the Condition and saving it again restores the expected behaviour.

Investigation showed that the XML import stores line breaks in the Condition_type and Condition_Value fields as \r\n (CHR(13)CHR(10)), because that is how they are written in the exported XML. The evaluation logic in Event_sys and Fnd_Event_Action_API expects a plain CHR(10), so the condition check always returns TRUE. The same scenario does not occur in IFS Cloud 23R2, where the exported XML uses \n (CHR(10)).

How can this be fixed in IFS Applications 10, and is there an update that corrects it?

Technical details Products: IFS Applications 10 UPD14 (affected); IFS Cloud 23R2 (not affected). Fields: Condition_type, Condition_Value. Line endings: \r\n = CHR(13)CHR(10) vs \n = CHR(10). Packages: Event_sys, Fnd_Event_Action_API. Transport: ACP export/import (XML or Zip). Fixed in: Apps10 UPD20; IFS Cloud 22.2.14 (22R2 SU14), 23.1.7 (23R1 SU7), 23.2.0 (23R2 GA), 24.1E.0 (24R1 EA).

Any attachments are visible to signed-in members.

1 answer

0

✓ Accepted answer

Confirmed by IFS (as relayed in the thread): this is a product defect, and it is fixed in a later update.

  1. IFS Applications 10: the fix is included in UPD20. Upgrading to UPD20 or later resolves it.
  2. IFS Cloud: the fix is included in 22.2.14 (22R2 SU14), 23.1.7 (23R1 SU7), 23.2.0 (23R2 GA) and 24.1E.0 (24R1 EA).
  3. Until you can take the update, the workaround described in the question applies: after each import, open every affected event action, make a trivial edit to the Condition and save it. Re-saving stores the condition with CHR(10) line breaks, which the evaluation logic reads correctly.

Why it happens: the imported condition keeps CHR(13)CHR(10) line endings from the XML, while Event_sys and Fnd_Event_Action_API expect CHR(10), so the condition always evaluates to TRUE.

Prerequisites and limitations The permanent fix needs Apps10 UPD20 or later, or one of the listed IFS Cloud service updates. The re-save workaround has to be repeated for each affected event action after every import. The fix information was reported in the thread as coming from IFS; there is no public defect reference in the thread.

Sourced from IFS Community · original thread · MadurangaJ

Answered by IFS Wire DeskEditorial · 3 Nov 2026