Hi Soniya, This is a save bug. If you have a field mandatory in a status and when ever you try to save the request by updating any value (Other than this field) or notes without filling this this particular field or if you try to click the action button this popup will come up.
If you want to avoid this popup, I have a solution, If yor question is something else please let me know.
I figured out that this coming from the Mandatory Field. Actually, since the other validations are customer specific, I could not paste them directly. You see that this field is mandatory and we can configure that. We have some fields, like suppose 5 percentages fields. Some or all of them can be populated however their sum should be 100. Now what happens is that, we get an error message in situations where percentage != 100. This message comes from a rule and is displayed in the percentage section.
This message however, does not restrict the user from going ahead and saving the project. We want to mandate that the percentage sum should be 100
We had the exact problem, where the rule can check only >100 and 100, but not <100, and if <100 then user could save the request and the workflow would move to the next step. We created a workaround for the same, which worked perfectly fine and is as below,
1. Create a read-only field above or below your percent total field (where you need to display 100%). In this field just give message to the user, that if the field is does not equal 100 then the workflow will be routed back to the same user and won't move to the next step.
2. Then we created an execution step after this decision step, where we used to see if the value in this field is 100 or not, then we route the workflow back to the previous step, i.e. to the same user, if not 100.
3. In the execution step if the value in this field was 100, then only we moved the workflow to the next step.
We also used the numeric field instead of % field. This was in 7.1, I haven't tried it yet in 7.5 for any alternate solutions.
In the earlier version of PPM(7.0&7.1) and ITG all these Java script alerts were availble in the differnt-2 location in file system as per the categories.All these alerts were bases on the field masking and checking null value or some time dependencies.
After moving to PPM 7.5 in demand Managament we have got new feature of UI Rule.In which we can also call different behaviors availble in RequestRulesSystemLibrary.js and RequestRulesUserLibrary.js files.We can also add more scripts in RequestRulesUserLibrary.js as per our requirement.
For the rest of the module you can find many .js file present in the file system serving differnt purpose.
Almost all of the PPM error messages are stored in these three locations,
1. Database table - Run query SELECT * FROM KNTA_MESSAGES and you will see all the error messages with its corresponding error codes. So you can modify the error messages in this table to suit the end user needs.
3. Java files - This I believe is least used for storing the end user related messages, but some debugging messages can be found in java files. For this you need to decompile the .class files to see the messages.
But to say, whichever message you want to customize, may be getting used at other places also in the application and may impact messages at other places. Also, this will lead to customization of the core files that may impact every time you apply a Service Pack or do a version upgrade. And you may need to reapply the customization and again test everything thoroughly. If end users can be convinced on the effort and recurring efforts required on this, probably not doing customization may be the best option as far as possible.