Publisher Action unexpectedly triggering Workflow
Last updated 2017-04-14 ·Reference W-1792258 ·Reported By 0 users
When a user updates a Case status to "Closed" using Chatter Publisher/Case Feed Actions, the previous value of the status field appears to be evaluated, causing a workflow to trigger unexpectedly.
NOTE: This issue is intermittent and cannot always be reproduced.
- Create a Workflow that triggers (on creation) based on Case Status of "New"
- Verify that Workflow triggers as expected on Case creation
- Using Chatter Publisher Actions, update the Case status to something other than "New"
- Workflow incorrectly triggers a second time
The only workaround at this time is to avoid changing the Case Status using the Chatter publisher actions.
Reported By (0)
Is it Fixed?
Any unreleased services, features, statuses, or dates referenced in this or other public statements are not currently available and may not be delivered on time or at all. Customers who purchase our services should make their purchase decisions based upon features that are currently available.