☁️
Flow IFS Cloud Development Guidelines
  • Flow IFS Cloud Development Guidelines
  • 👶Getting started
    • OData Basics
    • IFS Cloud
    • Terminology
    • Useful Applications
    • IFS documentation
      • IFS API Explorer
      • Entity details
    • Setting up the OData connector
      • Configure connection between Flow Server and IFS Cloud
      • Selecting which configurations are visible in Flow Server
  • 👩‍💻Flow Development with OData
    • Architecture
    • Flow development and distribution strategy
    • Implementation
      • Operations in OData machine steps
      • Missing operations
      • Translations
      • Iteration
      • Join data sets
      • Misc Tips and trix
      • Document / Media Library Management
      • Response status handling
        • Errors from IFS
      • Operation specific notes
        • Set input parameters using flow script
        • Update
        • 🛠️WIP - Create
        • Read
    • Configuration
      • Authentication models
        • Setup Client credential flow
        • 🛠️Setup Password credentials flow
        • 🛠️Setup Authorization code flow
        • 🛠️Setup OpenID flow
        • Obtaining Authentication related URLs from IFS Cloud
      • Projection administration
        • Administrating new projections
        • Administrating updated projections
      • Configuring projections in IFS
        • Custom Entities
        • Custom Projections
        • 🛠️WIP - Query Designer
        • Quick Reports
    • Trigger Flows from IFS Cloud
      • Trigger User Flows via External Navigation Links
      • Trigger Machine Flows via BPA using commands
      • 🛠️Trigger Flow via Event Action
    • Debugging and Testing
      • Aurena debugging
        • Inspect in web browser
        • IFS debug console
      • OData Connector Log
  • 🪄Advanced
    • Custom Request
    • C# usage in the OData connector
      • Different methods
      • Building request
      • 🛠️WIP - Code examples
Powered by GitBook
On this page
  • Why are operations missing?
  • Example of missing operation
  • Solution

Was this helpful?

  1. Flow Development with OData
  2. Implementation

Missing operations

PreviousOperations in OData machine stepsNextTranslations

Last updated 1 year ago

Was this helpful?

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:

  1. Use Custom request feature (available from OData connector version 2.11.13) for configuring single API call or

  1. In more complex cases create custom C# in Code section to call the missing API.

👩‍💻
Custom Request
C# usage in the OData connector
Public API specifications
Click + to create new task
Request URL from Chrome log
Missing operation
Code section