Introducing Validation Rules

Validation Rules allow ATP administrators to configure data change policies that are system-wide and company-specific.

If your organization has strong process regulations, you can configure Validation Rules (VR's) to prevent unnecessary changes and perform necessary checks. Validation Rules allow system administrators to configure policies to prevent undesired data modifications, for example:

• Do not allow users to change custom values of an Epic when it is in the final state
• Do not allow users to change Time records when they are marked as billed
• Only allow users with the Approver role to change the Approved custom value

Validation Rules greatly increase the reliability of the data entered into the system, prevent unwanted modifications, and help with compliance. Before this feature was implemented, customers had to use unreliable workarounds to enforce data policies and detect the violations.

You can configure Validation Rules using Targetprocess DSL (Domain-Specific Language). DSL is also used for other existing ATP features, such as Metrics and Automation Rules.

Triggers

Every Validation Rule is defined as a trigger and a filter. A trigger specifies data modifications with which the rule reacts. A filter specifies whether saving the modification is allowed.

For more configuration examples and feature description, go to Targetprocess developers portal.