Adding Attributes

To add new custom attributes to an entity, from the Edit Business Entity page, expand the Data Model section by clicking on it, then click the Insert button. The Add Attribute page appears where you will provide the properties.

Based on the attribute type you select from the Attribute Type drop-down list, you need to provide details corresponding to that specific attribute. For more information, see the Types of Attributes.

This is the generic list of properties you need to provide when adding a new attribute (field).

Property Description
Name The name of the attribute. This is used to identify the attribute in the data model when you design the user interface, for instance to specify which attribute is displayed in a specific field.
A naming convention is an important part in a well-built data model; therefore, we recommend you to use PascalCaseNames (upper camel), except for the first letter. The Name starts with a lowercase letter and all additional words start with an uppercase letter. Example: accountId.
Attribute Type From the drop-down list, select the type of attribute you want to add.
Display Name The name of the attribute that will be displayed on the data form in the user interface. You can overwrite the Display Name using other commands directly in the HTML data form.


Insert the proper description.


Insert the tooltip to be displayed. The message inserted here will show when the user will hover over the attribute in the FintechOS Portal.

Tooltips can be a powerful UI pattern which help you guide your users to take specific actions within the product; thus, enhancing the user experience.

If tooltips are activated on data form driven flows, for all attributes to which you want to show tooltips in the Digital Experience Portal, in the Tooltip field, provide the tooltip text.

Optionally, you can add tooltips to specific attributes which can be shown in the Portal UI on data form driven flows.


This is the name of the table column.

Required Level From the Required Level drop-down list you can choose if a specific attribute (field) is going to be mandatory, recommended or optional:
  • None – The field is optional. No error message will be displayed if the field is not completed by the end-user.
  • Recommended – A blue dot will be displayed on the upper-left corner of the field in the user interface to indicate that it might be useful to fill in the field.
  • Required - A red dot will be displayed on the upper-left corner of the field in the user interface to indicate that it is a mandatory field. The end-user will not be able to add a new record if the field is not completed.
  • You can only add required attributes to entities which have no records (empty entities). If you try adding a required attribute to an entity for which you already have required attributes stored within the database, you'll receive an error message.
  • You can add required attributes without creating constraints in the database, from the Forms section by using the After generate events field and the capabilities of field options.


The attribute is readonly if true, i.e. the front-end user will not be able to insert any data in this attribute.

Well-designed onboarding is vital for streamlining the user experience. Imagine users being lost within the app, having no clue what specific items on the UI mean or what actions they should take. If only they had the possibility to hover over specific fields and see some tips on what they should be doing.

Always make sure to save your configurations by clicking one of the save icons displayed on the top-right corner of the page.