Project and Portfolio Management Practitioners Forum
cancel
Showing results for 
Search instead for 
Did you mean: 

Certain rules do not fire on request field changes in 7.5

Highlighted
Alan Delimon
Regular Collector

Certain rules do not fire on request field changes in 7.5

We have some requests that have an "assign to self" dropdown validation. When "Yes" is selected, a rule fires that changes the assigned to user to the user creating the request. When "No" is selected afterwards, the assigned to user is cleared.

In 6.0, this works flawlessly.

In our 7.5 install, this partially works. You can assign to user when the validation is set to "Yes", but when it is set to "No", the assigned user stays the same.
5 REPLIES
Niraj Prabhu
Frequent Visitor

Re: Certain rules do not fire on request field changes in 7.5

Alan,

Please try and see if the rule is fired at all when you change the field value from Yes to No.

Secondly check on the rule if you have said explicitely the results on selecting either Yes or No.

Regards,
Niraj
Niraj P.
Alan Delimon
Regular Collector

Re: Certain rules do not fire on request field changes in 7.5

Yes we have definitely done that. Nothing was changed from the 6.0 install to the 7.5 install. The rules weren't modified at all.
Darshan Bavisi
Occasional Visitor

Re: Certain rules do not fire on request field changes in 7.5

Hi Alan,

Can you send the screenshots and the rule sql? Thanks.
Alan Delimon
Regular Collector

Re: Certain rules do not fire on request field changes in 7.5

The rule SQL is quite simple:
select '', '', '', '' from dual

It's setting the assigned to to null basically. this works in 6.0 but not 7.5.
Alan Delimon
Regular Collector

Re: Certain rules do not fire on request field changes in 7.5

The solution to this is a bit complicated but I found it.

I was able to do a full scale debug on this today, and observed that the call to autoPopulate.jsp (Kintana's AJAX engine) was not calling the rule that did the unset.

It was calling Rule 6, which did an on field change for the assign to self. Then, process subsequent rules was set to "no". Seeing that it was no allowed to check for subsequent rules, it did just that, and never bothered to fire rule #7, which was the check for Assign to self = no. So, the assigned user was never cleared.

In 6.0, there is a "Apply on field change and stop processing further rules" option. But it was ignoring the second part it appears. In 7.5, this has changed to "Apply on Field Change" and "Stop processing further rules" as individual options. And, the "Stop processing further rules" actually works. So it stops processing further rules and doesn't unassign as a result.
//Add this to "OnDomLoad" event