Document & activity variant are very nice features in KTA. It has great developmental advantages. It saves the lots of development time.
Scenario: Document Variant
Assume We have 10 different document Types and each as around 10 fields. Most of the fields are common for all the document types and some are not common.
Solution:
In the straightforward way, we will create 10 document types and 10 validation form for each document type. This is very time consuming and has repetitive tasks. And If we make one changes in one form. It needs to be followed all the forms. It’s very cumbersome.
In the other way, we will create one validation form and enable/ disable the controls per the document type.
Document Variant eases the second option with just a configuration. So, the solution is creating the root document type with all the fields.
And enable or disabled the fields for each document type in the Document Variant configuration.
This eliminates the lots of development efforts
Scenario: Activity Variant
Now, we have 2 levels of validation, first validation is for users who has less privileges they shouldn’t fill some critical fields Cheque no, amount. And 2nd validation user can see those fields and enter it.
Solution:
The quick solution is Activity Variant. The above said Document Variant further drill down to set the fields for each activity.
So, some fields in the first validation activity will be disabled. And the same will be enabled in the second validation activity configuration.
Both document and activity variants can be configured in the document variant section. And the configured activity variant needs to be mapped to the validation control in the activity Form.
Things to consider:
While configuring the variants, validation rules need attention. Because, if we configure the validation rule with visible and hidden fields, validation won’t work out.
So, validation rules should be configured with visible fields. If the requirement can’t fit into this rule, we can apply the workaround