LogoLogo
timvero.comMaven Repository
  • timveroOS SDK guide
  • timveroOS how-to
  • timveroOS admin-side setup
  • timveroOS Setup guides
    • v. 7.11
      • Working with the Data sources
        • Ready-to-deploy Data Providers
      • Low-code Decision processes/ Workflows
        • timveroOS workflows - [Beta]
          • Manual Decision-Making Process in timveroOS
        • Profiles formalization and mapping entities with workflows
        • User's Assignement to Warning (-s)
      • Credit products and additives, collateral
        • Credit products
          • Additives
        • Collateral/ securitization setup
      • Configuration of the pricing algorithms
        • Deal block
      • Documents
        • Generated documents
          • Signing of generated documents
        • Required documents
      • Roles creation
      • Notifications
      • Counters
      • Servicing
      • BI
      • Other useful features
        • Catalogs
        • Form builder
    • v. 7.10
      • Admin-side system setup
      • Data sources and BPM / Underwriting setup for Dynamic Profile formation
        • Selecting integrated data sources and Feature set management
          • Ready-to-deploy Data Providers
        • Developing of Participants' or Collateral's evaluation algorithm
          • Manual Decision-Making Process in timveroOS
          • User's Assignement to Warning (-s)
        • Mapping Participants' or Collateral's evaluation algorithm
      • Credit products and additives, collateral
        • Credit products
          • Additives
        • Collateral/ securitization setup
        • Deal TnC
      • Configuration of the Offer Generator Script
      • Documents
        • Generated documents
          • Signing of generated documents
        • Required documents
      • Roles creation
      • Notifications
      • BI
        • Adding custom chart to BI Dashboard
      • Servicing
      • Catalogues
Powered by GitBook
On this page

Was this helpful?

  1. timveroOS Setup guides
  2. v. 7.10

Configuration of the Offer Generator Script

PreviousDeal TnCNextDocuments

Last updated 4 months ago

Was this helpful?

Business context:

The Offer Generator Script allows FIs to define rules for calculating terms and conditions through a low-code interface. By utilizing attributes from various underwriting processes and specific product features, including additives, the tool enables FIs to create precise formulas for determining terms and conditions for both the application and the participant. These formulas are developed using an algorithmic programming language.

An Offer Engine can be connected to multiple products, or each product can have its own dedicated Offer Engine. Separate scripts must be created for each scoring stage, with clear markers indicating their respective stages.

Configuration:

The script creation interface includes a built-in validation feature. Users can test the script's output by selecting the relevant product and additive, then entering client profile data. This data is typically drawn from and, at times, with .

After the script is created, the system can run a test before deploying it in a live process. The user must select a product, additive, and participant for the script to be tested on:

If the test is successful, the system will display the test offer data for the specified participant, product, and additive:

If the test fails, the system will display an error message:

Examples of potential error causes include:

  • The script references a product attribute that does not exist for the selected product.

  • There are syntax or logical errors in the script.

  • The attribute referenced by the script is missing from the participant’s profile.

In the screenshot, an example of a simple error is shown: the method profile.get("disposableIncome") is used instead of the correct profile.get("disposableIncomes"). The profile attribute “disposableIncomes” does not exist.

Additionally, it is possible that no offers are available for the selected participant, product, or additive based on the conditions defined in the script.

Rendered script

The script is designed to generate an offer within the additive, outlining the credit terms available to the client based on their established profile. If the offer is deemed unsuitable—such as in cases of insufficient solvency or a poor credit score—the system will not generate it. However, the system is set up to generate offers for each available additive.

step
this step