Workflow Steps
A workflow consists of multiple workflow steps. A step is a single unit of execution in a workflow. Steps are actions that are executed. Before you define a workflow, create all the workflow steps that you want to use in the workflow. Out-of-the-box workflow steps are configured in the
FASt and are available for use in the synchronous workflows. The
Workflow Steps page lists all the steps that are defined. Use the
Create Workflow page to link the workflow steps so as to create a relationship between all the steps in the workflow. The relationship must follow the business process that is used to process a credit application.
The following table lists the types of workflow steps:
Step Type |
Description |
---|---|
Action | Step invokes an activity that is configured in the FICO Application Studio. |
Condition | Step is used when a workflow needs to branch along different routes based on the value of a decision parameter or user action. |
Service | Step sends a SOAP request. |
Stop | The step is used for two purposes: to navigate to the user interface to indicate the end of the workflow or to indicate a point in the workflow where human intervention is required before the workflow can proceed to the next step. For example, the initial rules check whether the application is worth processing and if another application has been already submitted with the same details. If a duplicate is found by the duplicate check service, then manual intervention is necessary to resolve the duplicate issue and continue with the application processing. |
REST | Step sends a REST API request. |
DM | Step invokes the Decision Module web service. |
DAM | Step invokes the Data Acquisition Module web service. |
AM | Step invokes the Analytic Module web service. |
Parallel | The steps are executed parallelly instead of sequentially. |
Out-of
![]() | Note: By default, commit is done after each workflow step is complete.
|
Related Information
- Covered Topics
- Action Steps
Actions steps are the actions configured in the FASt. The APM is built on the FASt. The logic and functionality for the action is written in FASt. Examples of actions are ApprovedfromReview, ObtainCRA, ObtainRiskScore, and so on. To use an action in a workflow, create a workflow step of the type Action. Action steps can be used in parallel steps, where you select a number of steps that can be executed in parallel. - AM Steps
The Application Processing Module uses the Analytic Module to obtain SBSS scores and notification reasons. Analysis requests are submitted to the AM. The AM response contains data which is then used for further processing of the credit application. Apart from the AM actions that are configured in the FASt, you can create additional AM steps. When you use the AM step in a workflow, APM uses the AM parameters from the om_apm_am_adapter espace to invoke the module. - DAM Steps
The Application Processing Module uses the Data Acquisition Module to obtain consumer credit report data from credit reporting agencies (CRAs). Data acquisition requests are submitted to the DAM. The DAM response contains credit report data, which is then used for further processing of the credit application. Apart from the DAM actions that are configured in the FASt, you can create additional DAM steps. When you use the DAM step in a workflow, APM uses the DAM parameters to invoke the module and references these parameters from the om_apm_dam_adapter espace. - DM Steps
The Application Processing Module uses the Decision Module for various application and applicant data calculations, such as determining applicant age or run post-bureau rules, which ensure that applications meet automatic decline rules. Apart from the DM actions that are configured in the FASt, you can create additional DM steps. When you use the DM step in a workflow, APM uses the DM parameters to invoke the module and references these parameters from the om_apm_dm_adapter espace. - REST Steps
A REST step calls a REST service in a workflow. The GET, PUT, POST, and DELETE methods are supported. - Web Service Steps
A step that calls a SOAP service in a workflow is a web service step. - Conditional Steps
Conditional steps are used when you require the workflow to branch along different paths. A conditional step requires resolution before the workflow can proceed to the next step. When you create a conditional step, the workflow will evaluate or test the value of the field. Based on the value, the workflow gets routed along a specific path. You must configure a minimum of two outcomes. All outcomes must be unique. - Parallel Steps
A parallel step is a group of steps that are executed parallelly, instead of sequentially. Normally, as the workflow processes, each step is executed one after another. With parallel steps, more than one step can be executed simultaneously. The steps grouped in a parallel step must be independent of each other. When you include a parallel step in a workflow, all the grouped steps are executed before the next serial or sequential step is initiated. You can use only simple steps in a parallel step. You cannot use condition, stop, and parallel type of steps in a parallel step. - Stop Steps (for User Interaction and to End a Workflow)
Stop steps either indicate the termination or end of the workflow, or they indicate a step where the workflow stops and does not proceed further until a certain human activity is done. Stop steps move the processing back to the APM user interface. When there is a human activity in the workflow, you must configure a stop step.