Form builder
Last updated
Last updated
Not in all cases can the system determine a feature value for a participant at the workflow level, resulting in the inability to save a required attribute in the client profile. For instance, responses from data sources sometimes contain incomplete information requiring manual intervention. For these situations, Financial Institutions (FIs) can utilize the Form Builder tool.
At the workflow level, users can configure an exclusive gateway: one branch for cases where a complete response was received, the feature was calculated, and the client profile attribute is saved; and another branch for when the response lacks the necessary data.
For such warnings, in a Save warning fact task, the user can specify a Form scheme that a user from the responsible department will need to complete when approving this warning. In other words, the system provides the opportunity for manual resolution of an automatically unresolvable issue and allows users to set client profile attributes manually in such cases. The required form must be created in the Form Builder before setting it in a Save warning fact task.
In the Catalogs you can create a new form:
Create any custom fields relevant to your business logic:
It is crucial when configuring the form to specify the client profile attribute name where the value entered by the user in this form should be saved. The name must match the one used at the flow level to maintain the correct operation of the Offer Generator script.
When form building is finished the only required action is to connect it from timveroOS workflows - [Beta] to the specific Warning fact. timveroOS automatically appliies styles and renders these forms, no additional front end work required.
Note: One form scheme should consist of only one field because the value of this field is connected with only one attribute of the client profile.
When a workflow concludes for a participant with a warning that has a defined form scheme, the warning approval action form will include a field for specifying a value, without which approval is not possible. After confirmation of approval, the system will save the entered value to the client profile.
In the screenshot above, the workflow cannot determine the participant's work status (type of work status), and the user from the Underwriting department needs to enter the type if they want to approve this warning.
After that, timveroOS updates the client profile and can calculate offers for the participant (if necessary).
We utilize Form.io library to power this Form-builder. Detailed documentation can be found here: . Leveraging Form.io open sources integrated libraries you can assemble custom Form scheme relevant to this Warning Fact:
