It is possible to enhance the standard Transport Form, Business Task and Project screens with Custom fields. Custom Fields are a popular way for ActiveControl customers to tailor the out-of-the-box product to their individual processes. Custom Fields can be used to drive ‘Skipping’ rules within an ActiveControl workflow, and are also available in most ActiveControl Reports.
Custom Fields are created and edited by ActiveControl Administrators on the [Fields] tab of the Windows GUI configuration screen.
The following custom field types are currently supported:
|Field Type||Transport Form||Business Task||Project|
|Selection List||Supported||Supported||Not Supported|
|Section Header||Supported||Supported||Not Supported|
|Dynamic Dropdown List||Not Supported||Supported||Supported|
All custom fields can be marked as optional, mandatory or hidden. Other options are also available for specific custom fields, such as to limit the number of characters of a text field.
Make custom fields read-only after a certain Deployment or Planning status
It is possible to make a custom field (on either a Business Task or Transport Form) become read-only after a certain Deployment or Planning status has been reached. This configuration is done via backend table /BTI/TE_CF_STYLE in the ActiveControl domain controller.
|FIELD_ID||This is the number of the custom field that you want to make read-only, you can get this number from the Windows GUI Configuration screen.|
|DSID||This is the Deployment Status (you can select the status from drop-down during configuration, you do not need to get the long GUID from another table).|
|PSID||This is the Planning Status (you can select the status from drop-down during configuration, you do not need to get the long GUID from another table). Note, most customers do not use Planning workflow so this field will be blank.|
|READONLY||You need to tick this box to ‘activate’ your rule.|
(1) Read-only custom fields only works on custom fields. It does not work on standard fields.
(2) You must configure all statuses where you want the field to be read-only. You cannot just enter the first status in the sequence where it should become read-only.
(3) The sequence of statuses is based on what you have defined in [Task Statuses] configuration screen.
(4) User with authorization object Y_TEUSER for field ‘/BTI/TE_AC’ should have the value ‘EDITCUSTFIELD’ to edit the configured field to edit the custom fields at any point, regardless if they are read-only due to the configuration.
(5) This functionality relies on a Deployment Status being defined for every target/location in your workflow. This should be done any for effective Reporting within ActiveControl, but it becomes even more important with this functionality. If you have not set Deployment statuses for some of your path/target/locations – you will see spurious results. Please refer to Defining Task Statuses section of this Administration Guide for more information on how to create these.
(6) This functionality uses the Task Statuses calculations (“Use latest step in sequence” or “Use earliest step in sequence”) defined in Windows GUI Configuration [Other] tab as part of its logic. This means that if you have more than one transport against a Business Task, you may see unexpected results depending on how you are calculating the status. Similarly, you may also see unanticipated results in the event you link a Transport Form to more than one Business Task as part of your process. It should be noted that this activity is not generally recommended by Basis Technologies for most customers.