Found out that I cannot trigger a workflow rule off another workflow or approval process. Who else thinks that salesforce should recognize a field update by human hands the same as by workflow/approval process?
Example: I have a picklist field Status which starts out as "Not Submitted". After the employee submits it thru the Approval Process, the Status is changed (by the Approval Process) to "Waiting for Approval" (and from there the Approval Process will change the field to "Approved" or "Rejected" according to the AP). The Status field is Read-Only to the users, so that they can't approve their own items (obviously).
I created a reminder email workflow to go out to the owner if it's "Not Submitted" after 24-hrs. But, because salesforce does not recognize the field update made by the workflow, the reminder email goes out FOR ALL (regardless of the Status). To be sure, I updated a few Statuses automatically, and they pull out of the queue just fine.
I'm sure that others have great use cases for workflows triggering other workflows, as well.
So just to reiterate - salesforce, please recognize field updates made by human hands the same as field updates made by your computer system!
4 Comments » Posted by joyd
Posted 11/07/08
Categories: Customization, Force.com Platform, Administration & Sharing