Missing operations
There are IFS API operations that you can find from debug logs but are not available in the Flow machine step configuration.
3rd parties (including us) rely on specifications provided by IFS which can be inspected in API Explorer.
Why are operations missing?
IFS has not added operation to API specification not to allow too recursive calls or
specification (even not being too recursive) is missing from IFS API specifications (bug).
General rule is that IFS has exposed only two levels of operation structure in API specifications.
Example of missing operation
Add new Task to a Work Order in Aurena Client.
According to Chrome log IFS Aurena page calls
PrepareWorkOrderHandling.svc/ActiveSeparateSet(WoNo=35)/WorkTaskeArray/IfsApp.PrepareWorkOrderHandling.JtTask_Default()
which initiates new task with default values related to Work Order.
Such operation JtTask_Default() does not exists under WorkTaskeArray. This might be considered a bug since there are only two levels (ActiveSeparateSet/WorkTaskeArray)
Solution
Primarily locate another operation to accomplish the task.
if no workaround two option exist:
Use Custom request feature (available from OData connector version 2.11.13) for configuring single API call or
In more complex cases create custom C# in Code section to call the missing API.
Last updated
