Assumptions and Prerequisites
Before you can configure inflow, you need to check that your system meets the inflow system requirements. You also need to configure your environment and carry out a number of pre-configuration tasks.
System Requirements
|
Requirement |
Comments |
|---|---|
|
Temenos Transact (R19 upwards) |
Inflow works with Transact and the products listed below. |
|
Process Workflow (PW) |
PW for inflow is designed using process definition. |
|
Inflow Product IR and IE |
Inflow Product IR is used for inflow runtime and IE for inflow designer. |
|
Integration Framework (IF) |
Use IF if there is a requirement to trigger events for inflow. |
|
Runtime |
R19 TAFJ. Inflow is designed to work with TAFJ only. |
Configuring Environment
Start the database and the application server when using TAFJ. You also need to ensure that axis2.war with the landscape service, flow service and inflow service is up and running.
Preconfiguration Tasks
Before you can configure inflow, you need to define a process definition using the Process Workflow (PW) module of Transact with the following limitations:
- Use zero authoriser versions.
- Do not use enquiries. Enquiries are not supported in inflow.
- Because inflow only needs zero authoriser versions, use the status complete and the transition rule record authorised.
- We recommend that you provide the same user name in both the activity and the process definition.
- Only the recursion type of looping is supported.
An inflow defined without PW supports any version except for comma version. The version does not need to be an 0 auth version. Also, the version cannot be a comma version, for example: CUSTOMER.
In this topic