Skip to content

Known Limitations

Following are the list of restrictions that need to be aware of when working with the Workflow tool:

  • According to the Workflow transaction management policy, it is not allowed to call APIs which having the implicit commit, rollback, savepoint, or Pragma Autonomous blocks, through a Workflow.

  • Not support LOV (List of Values) in Workflow User Form.

  • It is possible to add static enumeration to the Workflow User Form. However, enumerations defined in IFS Cloud are not supported currently in the Workflow User Form.

  • Authentication for Workflow IFS Rest Connector requires the Workflow author to create and manage authentication manually. It does not support OAuth authentication to create tokens when calling external APIs.

  • Blob, Clob, GIS, and File datatypes are not supported currently. However, calling projections that manipulate them behind the scenes are supported.

  • The Query Builder filter tool in IFS API Task supports Enum type attributes. However, it is important to note that it works with DB Enum value and not with client Enum value. Query Builder filter displays the client Enum value in the dropdown. But it has to change for DB Enum value by modifying the filter text field value. For an example,

Assume the “approval_status” Enum attribute has client value as “APPROVED” and DB value as “APP”. Then client value is displayed in the drop down as below.

​ After submitting, it needs to be changed to DB Enum value as below to filter the record(s) correctly.

​

  • Workflow can be triggered from a Mobile App transaction via a custom event, but the workflow must fire asynchronously to work.
  • Workflow only supports attributes that have a maximum character length of 2000.

  • There’s a limitation when a high number of Workflows are triggered simultaneously when processing large volumes of data in situations such as Data Migration. Therefore, it is recommended to disable the Workflows to avoid disruptions during the Data Migration process.

  • The maximum number of Workflows that can be executed in a single transaction is limited to 20. This means if a certain action causes to execute 20 or more Workflow instances in a chained manner, it will give an error as "Potential infinite recursion detected in cascading BPAs".

Ex: There are two Workflows where one Workflow modifies all the customer order lines of a particular customer order, and the second Workflow is triggered for every line. This error will occur if there are 20 or more customer order lines in a single customer order.

If there is a possibility of reaching 20 Workflows in a single transaction, the following actions can be taken:

  1. Use Asynchronous Workflow where this limitation will not exist.

  2. It is possible to override the default number of Workflows allowed in a transaction by adding a record to BPA_SYSTEM_SETTINGS_TAB. Add "Variable" as "CASCADE_LIMIT" and "Value" as a higher number that suits your scenario. Then restart the ODataProvider container.

Note: Override the default value of this configuration responsibly since it might lead to transaction timeouts and performance issues, negatively impacting the system.