You can display a warning message in a rule based on criteria that you define. By calling attention to configurations that do not follow best practices at design time, you can help users improve their compliance score before they take their application to production.
Open a warning message that matches your use case by doing one of the following:
On the Message form, take note of the message definition and the type of input parameters that the message supports, because you need this information when you call the message from another rule.
Find and open the rule that detects the warning conditions, by searching for the rule or using the Application Explorer.
Update the rule to call the standard pxAddGuardrailMessage function.
The syntax for calling a function can vary, based on the type of rule that you are updating.
Pass a parameters to the function, by using a tab-delimited string that begins with your message name and ends with values for input parameters.
For examples of correctly formatted strings, see Messages.
At run time, your application displays warning messages in the header of a rule form. Users can choose to follow the guidance in the message to resolve the warning, provide an explanation that justifies the warning, or ignore the warning.