Following are the list of restrictions that needs to be aware of when working with Workflow tool.
According to the Workflow transaction management policy, it is not allowed to call API's 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 Workflow User Form. But enumerations defined in IFS Cloud are not supported currently in 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 token when calling external APIs.
Blob, Clob, GIS and File datatypes are not supported currently. however, calling projections which manipulate them behind the scenes are supported.
The Query Builder filter tool in IFS Projection Delegate 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 “approval_status” Enum attribute has client value as “APPROVED” and DB value as “APP”. Then client value display in the drop down as below.
After submitting, it has to be changed to DB Enum value as below to filter the record(s) correctly.
- Workflow only supports attributes that have a maximum character length of 2000.