All product information in wiki.bizagi.com is only valid for Bizagi BPM Suite 9.1.X.
For newer Bizagi BPM Suite versions (10.X and up) please visit the User Guide.
 

How to change a Throw Validation Message

From Business Process Management, BPM and Workflow Automation Wiki | BizAgi BPMS

Jump to: navigation, search

<keywords content="keywords">ThrowValidationError, Change, message, expression</keywords> 

How to Change a Throw Validation Message 

The main idea of this article is to explain the way a user can modify a Throw Validation Message that is appearing in the Web Application. A Throw Validation Message is a message notifying a user that something is not right in the information inserted. It Is one of the basic ways to manage errors in Bizagi through validations. As shown in the next example, the process Vacation Leave Request shows a Throw Validation Message when the user is trying to advance the activity.



The validation in this case is simple. By definition, the number of days requested should be more than five in order to continue with the case. Assume that many users have had problems with the message thrown by Bizagi since it has not been clear enough. Therefore, they are asking to modify the message in this activity. In order to do that, the user has to identify how is the expression being executed. In this example, the expression with the Throw Validation Message is executed when the user is trying to advance the activity Register Vacation Leave Request. i.e. it is executed in the On Exit events of the task.



The next step is to open the expression and then the expression box. Once the expression is opened, the CHelper.ThrowValidationError sentence can be appretiated inside the logic of the rule. This sentence has the message shown in the web application.



In order to modify the message that is going to appear in the web application, the only thing that needs to be changed is the text whithin the CHelper.ThrowValidationError sentence for the one needed. In this case it is going to be changed by in order to be more explicit. After that the user has to save the changes and test.



The message in the web application should have changed as well.


<comments />