Question
Cognizant Technologies
IN
Last activity: 28 Feb 2017 22:03 EST
Make History Tab - Description and Usage fields Mandatory for all the rules in application while save/SaveAs
Tried to add validation steps for pyDescription and pyUsage properties checking null values. and referred into PreSave activity rule. But, it didn't work out as the PreSave rule is in different classes for respective rule instances, and also the error messages are getting cleared in the later steps of Rule-.Save activity.
Please suggest. Thanks!
***Updated by moderator: Lochan to update Categories***
Accepted Solution
Pegasystems Inc.
IN
Any of the extension activities will have the same problem that you mentioned. PreSave, pyPostSave, CheckForCustomWarnings etc....
If they are specialized for some rules they will not be picked from Rule-. You can use pyPostSave or CheckForCustomWarnings if you are fine leaving out few rules.
Let us know if this helps :)
Incessant Technologies
GB
You Can Customise RuleHistoryForm_Description Section and Make Usage and Description fields as mandatory. This will not allow you to save the section unless usage and description is added.
Pegasystems Inc.
IN
Hello,
We have tried adding them as mandatory feilds in RuleHistoryForm_Description Section, and yet we are able to perform save/save as of the section rule. I am looking into this behavior at my end. I will keep updating the progress of my research.
Best Regards,
Mounika
Areteans Technology Solutions
AU
Hi Shoyeb,
You can make use of the CheckForCustomWarnings activity which will be called before an instance is saved. Here you can check the relative properties and set the warning messages with severity as required. When the severity is high. This way one can regulate the users by providing mandatory fields. Hope this helps.
Regards,
Ratan Balaji
Cognizant Technologies
IN
Thanq, Its working for CheckForCustomWarnings activity as well as pyPostSave avitivity by saving into respective generic classes .... :)
Accepted Solution
Pegasystems Inc.
IN
Any of the extension activities will have the same problem that you mentioned. PreSave, pyPostSave, CheckForCustomWarnings etc....
If they are specialized for some rules they will not be picked from Rule-. You can use pyPostSave or CheckForCustomWarnings if you are fine leaving out few rules.
Let us know if this helps :)
Cognizant Technologies
IN
Yes it worked for Rule-.pyPostSave or CheckForCustomWarnings respectively... But we have to skip the validation if its in specification or requirement rule types as History Description is not present for them. Thanks :)