> For the complete documentation index, see [llms.txt](https://docs.novacura.com/flow-connect/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-connect/working-with-connect/connect-to-systems/connectors/ifs-applications-10.md).

# IFS Applications 10

Use the IFS 10 connector to connect to your IFS 10 instance.

## Managing Connector : Add, Edit, or Delete

Follow the [steps in the link](https://docs.novacura.com/flow-connect/working-with-connect/connect-to-systems/managing-connector) as a guideline for connector actions: Add, Edit, and Delete.

## Configuration values

| Configuration              | Description                                                                                                                                                                                                                                                                                                                                                                             |
| -------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Agent Group**            | Agent group where the connector should be executed                                                                                                                                                                                                                                                                                                                                      |
| **Server**                 | Address to the IFS Applications Server                                                                                                                                                                                                                                                                                                                                                  |
| **Global User ID**         | User ID to authenticate against the database                                                                                                                                                                                                                                                                                                                                            |
| **Global Password**        | Password for the Global User                                                                                                                                                                                                                                                                                                                                                            |
| **Connection Timeout**     | Connection timeout, in seconds, to use when executing a script or a query. If not set, the default value of 90 seconds will be used                                                                                                                                                                                                                                                     |
| **AppOwner/Schema**        | Database schema or the user account that has ownership and administrative privileges over all database objects related to the IFS application. Typically this is IFSAPP                                                                                                                                                                                                                 |
| **Initialization Command** | <p>Optional command to execute immediately after successful login.<br>Note: The user executing the Flow Connect app is available in the initialization command through <code>:FlowUser\_\_email</code> (and <code>:username</code> for backward compatibility). For automations, where no user is driving the execution, both variables are set to an empty string.</p>                 |
| **Cleanup Command**        | <p>An optional command to execute on the database after the operation has been completed.<br>Note: The user executing the Flow Connect app is available in the cleanup command through <code>:FlowUser\_\_email</code> (and <code>:username</code> for backward compatibility). For automations, where no user is driving the execution, both variables are set to an empty string.</p> |
| **Command Timeout**        | Command timeout, in seconds, to use when executing a script or a query. If not set, the default value of 90 seconds will be used                                                                                                                                                                                                                                                        |

## Run As Flow User

One of the most commonly used features in the Flow Classic IFS 10 Connector was **“Run as Flow User”.** This feature allows IFS 10 machine steps to be executed using the current Flow user by default. This section describes how you can achieve a similar functionality in Flow Connect.&#x20;

In Flow Connect, User ID will always be the User's email address and for the corresponding IFS user you can check the Directory ID as shown in below.

<figure><img src="https://1716064794-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIIgl6sNaTky0iALxYWHH%2Fuploads%2FvUZ0DHMZ8ZFvfKB3DdsG%2Fimage.png?alt=media&amp;token=f7886a62-915c-4c1f-9d01-d4c7361958d5" alt="" width="462"><figcaption></figcaption></figure>

#### If Flow User ID = Directory ID of the IFS user

If Flow User ID matches Directory ID of the IFS user, you can simply set the "Run as User" to `:userId` variable in the machine step. `:userId` represent the logged in Flow User and will always be available in every machine step.

<figure><img src="https://1716064794-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIIgl6sNaTky0iALxYWHH%2Fuploads%2FLKbU6HgBN2ycKqeNKfgv%2Fimage.png?alt=media&amp;token=b8c4b777-eff9-4fcd-8a18-48530d6a03f6" alt="" width="563"><figcaption></figcaption></figure>

#### If Flow User ID != Directory ID of the IFS user

If Flow User ID does not matches Directory ID of the IFS user, you can add the flow user email to the email field in the IFS side.

<figure><img src="https://1716064794-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIIgl6sNaTky0iALxYWHH%2Fuploads%2Fq3xhH2k2JooKIc7qDc9g%2Fimage.png?alt=media&amp;token=3c202191-8c64-4959-adf6-94a961ea7581" alt="" width="460"><figcaption></figcaption></figure>

With this setup you can write a simple query at the beginning of the app to the retrieve the IFS User ID for the logged in Flow User. Its preferable to design it as a component so the query can be re-used in multiple apps. `:FlowUser__email` represent the logged in Flow User and will always be available in every machine step

<figure><img src="https://1716064794-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIIgl6sNaTky0iALxYWHH%2Fuploads%2FdN7GmHGAnFHGRI3BWG30%2Fimage.png?alt=media&amp;token=bbc6d5b6-e23a-411f-8153-a1f059a67e36" alt=""><figcaption></figcaption></figure>

{% hint style="warning" %}
Make sure you mark the `:ifsUserId`  as [signed](/flow-connect/working-with-connect/connect-to-systems/signed-values.md) to make sure value received from this step can not be tampered with when using it with other machine steps.
{% endhint %}

Once you have this step at the beginning of the app, you can use `:ifsUserId` flow variable as "Run as User" in subsequent machine steps.

<figure><img src="https://1716064794-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIIgl6sNaTky0iALxYWHH%2Fuploads%2Fgv9qEoJGj2495DUMvfae%2Fimage.png?alt=media&amp;token=053c3408-ce8f-40b6-9394-5b361e9e0abe" alt=""><figcaption></figcaption></figure>


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.novacura.com/flow-connect/working-with-connect/connect-to-systems/connectors/ifs-applications-10.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.