IFS Applications 10

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

Add connector

1. Select Connectors in Hub menu and select Add Connector.

   
2. Select IFS Applications 10.

   
3. Enter the name and optionally a description.

   
4. Enter the configuration values for different environments.

5. Select Save.

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	Optional command to execute immediately after successful login
Cleanup Command	An optional command to execute on the database after the operation has been completed.
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

Edit connector

1. Hover over the connector card and the context menu will appear, select Edit.

2. You can now change or the configuration values for different environments name, description.

Delete connector

1. Hover over the connector card and the context menu will appear, select Delete.

2. Confirm and the connector will be deleted.

Deleting a connector can not be undone.

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.

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.

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.

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.

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.

Make sure you check the "Expect Signed" checkbox to make sure the :ifsUserId value received from this step can not be tampered with when running it in the Flow Client.

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.