timvero.comMaven Repository

timveroOS workflows - [Beta]

Participants and assets automatic scoring/ decision algorithms are set up using a specialized tool called Workflow

This tool allows Financial Institution (FIs) to design a scoring process for participants using the features mentioned earlier. When a feature is included in an algorithm, the system retrieves and processes the corresponding data source response:

General functionality description

The Workflow consist of Tasks and Logic functions.

Tasks types and their functions:

  1. Expression - Python or JavaScript, mathematical-functions based expressions allowing logical and logistical expressions implementation

  2. Load datasorce - interface allowing to fetch the transformed ready-to-use data from the connected thought the datasources Working with the Data sources

  1. Save to profile - interface to save outputs on the workflow (context) to the associated with this workflow execution participant or asset. These profile outputs later can be used for the pricing caluclations, documents and other process.

  2. Save alert fact - interface to save the alerts = red zone = decline with the decline reason from the Catalogs

  1. Save warning fact - interface to save the warnings = yeollow zone = manual review Manual Decision-Making Process in timveroOS

  2. Save info fact - interface to save any information as a fact to the particpant/ asset workflow execution

Logic functions types and their functions:

  1. Switch - function to create brunches with various logic

  2. Interrupt workflow - function to stop the execution at that point (for example after setting task Save alert fact)

Example of implementation

Here is an example of pulling the Experian data source with the Past Due feature using Load Datasource interface:

After receiving the value of the feature into the workflow you can build various Expession implementing your logical/ logistical model:

When needed use Switch to create various exclusive branches:

When you have all your Profile parameters being calculated use Save to profile interface to transfer values of the outputs to the particiapnt/ asset profile in the LOS/ LSS:

Similary to the Save to Profile interface use Save to Alerts fact for automatic declining and Save Warning Fact for manual review of the relevant business unit of the FIs:

Alert fact with option to select the decline reason for this fact according to records in the Decline reasons catalog.
Warning Fact with option to select the responsible for this exception business department (right side)

Important

However, not all client profile attributes can come from the decision algorithm. Depending on the business logic of the process, some attributes might result from user actions. For example, if a borrower disputes the offered amounts and provides details of additional income sources, this information, once verified by a designated user, becomes part of the client profile, prompting the system to automatically update the offers.

Additionally not in all cases all datasources can provide a response with all data for every participant and the system' isn't able to extract and transform data from response for setting client profile. It's managed by setting the form scheme for task Save Warning Fact.

Warning Fact with option to select the form scheme to fill in during manual review

Also important

More on how you can use saved to the Profile outputs here

Profiles formalization and mapping entities with workflows

More on the workflow interventions for the manual review here Manual Decision-Making Process in timveroOS

More on setting and using form schemes here Form builder

More on setting catalog here Catalogs

PreviousLow-code Decision processes/ WorkflowsNextManual Decision-Making Process in timveroOS

Last updated

Was this helpful?