Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

Type definition

Updated on May 25, 2021

The Type Definition tab allows maintaining questionnaire level configuration. The configuration presented is of different nature and used in a very different manner by the run time engine.

The Type Definition contains the following main elements of configuration:

Applies when condition

The KYC Engine determines in run time which of the available KYC Types are applicable in each specific business scenario. This determination can be driven in two different ways: using standard applicability conditions or the Applicability Matrix (see Defining applicability conditions). If you use standard applicability, you can set here the decision rule type and instance that will determine the applicability of this specific KYC Type. If you use the Applicability Matrix, this configuration will have no effect as the applicability of the rule will be determined by the matrix.

By default, the KYC Types are not applicable when using this configuration if no condition is configured. If there is a condition configured, the KYC Types are applicable when the configured rule returns a value true.

You can use several types of decision rules, including when, map value, decision table, and decision tree rules. For ease of configuration, a condition of Always is available to specify that the KYC Type must always be selected for every case.

Display Order
You can use this attribute to configure the horizontal (or vertical) display order for the KYC Type in the case user interface. Multiple KYC Types can share the same ordering sequence number. In this case, the second sequence is alphabetical, from lowest to highest (A-Z). To view the ordering of all available KYC Types, click on the Info icon, which will display the list of all the KYC Types in the system as they would appear if they were all applicable at the same time.
Read Only Condition
This attribute controls when the entire KYC Type (all KYC Items) should be read-only to the end-user. Use when rules, map values, decision trees and decision tables to drive this behavior. When the selected rule returns true, the questionnaire is presented as read-only. If no decision rule is configured or the rule configured returns false, the KYC Type is displayed as editable.
Data Transform
This data transform is invoked when the KYC Type is loaded into a case. It is used to initialize KYC Items, usually by pulling data from the case data structure or other data sources. This feature is used to prevent users from re-entering data that is already available in the system. For example, if there is a KYC Item where the users are asked to enter the full name of a customer, and the name is already available at the case, there is no point in asking the user to enter the data again. This data transform can take the value available in the case and map it into the property associated with the mentioned question.
Refresh Data Transform
There are situations when a KYC Type does not need to be initialized from the ground up, but that requires the re-initialization of only certain data elements. For example, let’s say there is a KYC questionnaire with a question asking for the list of customer-related parties and, at a certain point in time, that list changed in another case. If we applied the initialization data transform, values entered by the user might be overwritten. To avoid this data loss, you can configure a refresh data-transform to only overwrite those data elements that could have changed externally.
Post-processing Data Transform
When a data-transform rule is referenced in this field, the rule runs immediately after the KYC Type is submitted; that is to say, after the data collection step in the case flow. The data transform can be used to propagate the answers to questions to related cases, to a customer master profile, or to other interested components that might need to continue with the assessment of the customer.
Profile suites & Profile lists

These two configuration elements support the use of due diligence profiles in the KYC Type. For detailed information about this functionality, see Due diligence profiles.

The Profile suites is a list of all the profile suites that will be considered during the execution of the KYC Type. When the KYC Type is created, the list is initialized with a default profile suite called Default. You can add additional profile suites to add more dynamism to your questionnaire.

The Profiles list that appears on the right of the screen is a consolidated list of all the profiles defined in the profile suites. The order and consolidation process is driven by the order in which the suites appear in the profile suites list. Profiles defined in suites at the top of the list take precedence of profiles of the same name defined in suites down below. In addition to the profiles inherited from the profile suites, you can also define local profiles that will take precedence over those coming from the suites.

You can expand Profiles by clicking on their name, which will reveal a few definition elements. Those elements include the decision rule that determines when that specific profile is active and therefore can be used to drive the visibility and mandatory conditions of the KYC Items, which is nothing but the ultimate purpose of the due diligence profile.

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us