ActiveControl 7.1 introduces the ability to make custom fields read-only at a defined point in a workflow.

This is based on configuration of the fields and the status (either Deployment or Planning) at which the field should be locked down and become non-editable.

It is possible to set rules for custom fields existing at either Business Task or Transport Form level.

Configuration Steps

The 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.


(i) The sequence of statuses is based on what you have defined in [Task Statuses] configuration screen.
(ii) 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.
(iii) 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.
(iv) 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. For the same reason, 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.


Was this helpful?

Yes No
You indicated this topic was not helpful to you ...
Could you please leave a comment telling us why? Thank you!
Thanks for your feedback.

Post your comment on this topic.

Post Comment