PPM Support Tip: PPM updating front end Token values after the processing of Rules
A new KCS article was published: KM00574112
When using a User Interface (UI) Rule that uses a Token of a Field updated by a previous Rule, then an incorrect value for the Token is used in the UI Rule due to the backend just being updated
The following is an example of the current process logic for the sequence of Rules.
Suppose there are 2 Rules. The first is to set Field "Project Health" to "Green". The 2nd Rule is when "Project Health" is NOT "Green", then make "textarea" Required.
1) When the first Rule triggered, it only set the value to "Green" in the back end, so the Token [REQD.P.PROJECT_HEALTH] has been set to "Green", though it did not refresh the User Interface (UI) in the front end.
2) The 2nd Rule is triggered and checks the value in Field "Project Health". This Rule triggered after the first Rule finished, though the first Rule did not populate the value in front end, so the value is still null, so it did not equal to "Green", and then the "textarea" is set Required.
3) After all the Rules are finished, Project and Portfolio Management (PPM) calls back and populates the value in front end (the browser), and fills in "Green" in "Project Health"
Example of Workaround:
A) In the Rule that is setting the "textarea" to Required if "Project Health" is NOT "Green", please change the Dependency from:
'project health' condition 'is not equal to' a constant value 'Green'
'project health' condition 'contains any value
B) And then in the UI Rule, please change the code from:
'setFieldRequied('[REQD.P.PROJECT_HEALTH]' != 'Green')'
// Assuming the token for 'project health' is 'REQD.P.PROJECT_HEALTH', please change it if settings are different
If you find that this or any post resolves your issue, please be sure to mark it as an accepted solution.”