[progress Communities] [progress Openedge Abl] Forum Post: {!nextstatus} Is Empty When...

[alank@daitangroup.com]

I have triggers set up for Workflow Status changes. Since some of my Workflow Actions do not change the Status, I needed to set up a "Before Update" Trigger that listens to the Workflow Status field. If {!nextStatus} is blank (meaning that the status won't change, and the Updated Status trigger won't fire), it calls the "Updated Status" trigger by hand. This was working fine, until I made a mass update to change multiple records' Status. In the Mass Update case, {!nextStatus} shows as blank, so the Before Update trigger manually calls the Status Changed trigger. Then, the Status are all changed to a new value, and the Status Changed trigger is invoked once again - causing duplicate action, which is undesirable to me. How do I solve this? {!nextStatus} shouldn't be blank, in my opinion. Thanks

Continue reading...