> For the complete documentation index, see [llms.txt](https://help.novacuraflow.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.novacuraflow.com/release-information/connector-services/ifs-odata-connector/2.1.19.md).

# 2.1.19

### New features

* Support for $batch calls on Create and Update operations

You can now select the iterator option "Batch with single change set" when creating or updating multiple entities via the iterator feature. In practice these will make the connector send all the create/update requests in one single $batch request to IFS - which has **significantly** better performance. The "single change set" also implies an "all or nothing"-operation - either all entities are created/updated - or none are. This is, however, dependent on the implementation of $batch on the endpoint that receives it. All tests we have done has followed this rule, but we cannot garantuee it. 

<figure><img src="/files/0krZ97W8BxI7U5Mzj3Bl" alt=""><figcaption><p>$batch</p></figcaption></figure>

* Order by name in communication log. A small feature to make it easier to work with the communication log

<figure><img src="/files/oGRTAEOOrt0ZON6NHmXL" alt=""><figcaption><p>Order by</p></figcaption></figure>

* This version of the connector is based on newer version of the connector service infrastructure which includes several new features.&#x20;

  * Configurable http timeout. You can now configure the http timeout on poll worker services. Setting the value to lower than 100 seconds is not recommended.  New installations will have the default value of 100 seconds, upgraded ones will have 43200 (12h).
  * Faster scaling. The connector will scale it's running workers up and down much more quickly and predictable. Each running worker consumes memory and CPU, so having the right amount of workers running is good for the overall performance of your machine hosting the connector. &#x20;
  * Execution monitor

    A new section which can be reached from here:

    <figure><img src="/files/nEyftm6b1yvtAyiJMFdS" alt=""><figcaption><p>Exec. monitor</p></figcaption></figure>

    In this section you can monitor the part of the connector that handles communication with the external system, IFS in this case. The image below is from a load test, **not** normal load. The green color indicates how much requests are in the internal queue of the connector, ready to be processed. The black line shows incoming requests to the connector. This particular load test had much less number of running workers compared to incoming load, so the green area was expected to go up as shown below. Below the graphs for incoming/outgoing you can see all currently running workers, and what they are doing. You can also get sense of the execution times and how many jobs they have done.

  <mark style="color:red;">**NOTE**</mark>: Do not leave the monitoring page open in production. It consumes resources from the connector.&#x20;

  *

  ```
  <figure><img src="/files/NeyzpadT8lqte41I0etO" alt=""><figcaption><p>Execution monitor</p></figcaption></figure>
  ```

### Bug fixes

* Fixed a bug where filtering on expand members caused an invalid error message
* Fixed a bug where custom requests could not be used in a subscribed workflow if IFS endpoint differed. Note that when opening the machine step in subscribed workflow the url will point to the url of the published workflow. The correct url will be used at runtime though.
* Fixed a bug which gave an "Filter on unknown member"-error when the name of an entity property was the same as the name of the entity
* Various minor bugfixes&#x20;


---

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

```
GET https://help.novacuraflow.com/release-information/connector-services/ifs-odata-connector/2.1.19.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.