> For the complete documentation index, see [llms.txt](https://docs.novacura.com/flow-ifs-cloud-development-guidelines/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.novacura.com/flow-ifs-cloud-development-guidelines/flow-development-with-odata/implementation/missing-operations.md).

# 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.

<figure><img src="/files/ET4Hms2a8UUcjopqgmj3" alt=""><figcaption><p>Public API specifications</p></figcaption></figure>

## 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&#x20;

Add new Task to a Work Order in Aurena Client.

<figure><img src="/files/3lItiyNuLeOa5lyjBZ8D" alt=""><figcaption><p>Click + to create new task</p></figcaption></figure>

According to Chrome log IFS Aurena page calls&#x20;

`PrepareWorkOrderHandling.svc/ActiveSeparateSet(WoNo=35)/WorkTaskeArray/IfsApp.PrepareWorkOrderHandling.JtTask_Default()`&#x20;

which initiates new task with default values related to Work Order.

<figure><img src="/files/Td9SvTXXozakDwQQLupb" alt=""><figcaption><p>Request URL from Chrome log</p></figcaption></figure>

Such operation JtTask\_Default() does not exists under WorkTaskeArray. This might be considered a bug since there are only two levels (ActiveSeparateSet/WorkTaskeArray)

<figure><img src="/files/ia1oAgz9yurvPEwrY26g" alt=""><figcaption><p>Missing operation</p></figcaption></figure>

## Solution

**Primarily locate another operation to accomplish the task.**&#x20;

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

{% content-ref url="/pages/hO7uX1mJNYxfJLH02A5M" %}
[Custom Request](/flow-ifs-cloud-development-guidelines/advanced/custom-request.md)
{% endcontent-ref %}

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

<figure><img src="/files/5zkEueSq6vvAhmo96q4Q" alt=""><figcaption><p>Code section</p></figcaption></figure>

{% content-ref url="/pages/qd7xfxs7xXxZh7rmTgLX" %}
[C# usage in the OData connector](/flow-ifs-cloud-development-guidelines/advanced/c-usage-in-the-odata-connector.md)
{% endcontent-ref %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.novacura.com/flow-ifs-cloud-development-guidelines/flow-development-with-odata/implementation/missing-operations.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.