function readOnly(count){ }
Starting November 20, the site will be set to read-only. On December 4, 2023,
forum discussions will move to the Trailblazer Community.
+ Start a Discussion
GuillermoPGuillermoP 

Re-Evaulate WF Field Update, Triggering WF with Time-Dependent Email Alert

I'm using salesforce Entitlements and Cases in our org. I'm stamping the a field called "Triage Violation D/T" via a field update as part of an Entitlements Violation Action. This works flawlessly when things get violated, and can be pulled into a base report when it actually was violated. My support team triages a case (identify products and other details) which fires another field update on a field called "Triage D/T". This works flawless too. 

 

I'm trying to setup another Workflow which is using Time-Dependent actions, 2 email alerts. One should fire after 1 hour from the Rule Trigger Date, and the second email will fire 4 hours after the Rule Trigger Date.  The point of this is to let management know when things get violated and are still outstanding 1hr and 4 hours after the voilation has occured (not been resolved, aka no Triage D/T). This effectively gives support a buffer to finish the triage before management gets the email. The time stamping still allows management to see what was violated at any point in time. I've got the below Workflow setup on the case with the following Rule Criteria:

 

Evaluation CriteriaWhen a record is created, or when a record is edited and did not previously meet the rule criteria

 

(Case: Case Record Type EQUALS Support)

AND

(Case: Triage Violation D/T NOT EQUAL TO null)

AND

(Case: Triage D/T EQUALS null)

 

The alerts work great if I manually modify the the case fields "Triage Violation D/T" to any value, and leave "Triage D/T" blank. I check the Monitoring Time-Based Workflow section of setup and everything is firing correctly. 

 

But, when I let the whole system take its natural course, creating the case and letting the violation happen without triaging the case nothing queues up for the email alerts? I know its not the Entitlements Violation Actions Field Update as it is firing fine on all my test cases (Triage Violation D/T), so thats not the problem. I even had the Field Update set to "Re-evaluate Workflow Rules after Field Change" to TRUE. Anyone have an idea of whats going on? I'm guessing im missing one simple switch somewhere?

 

Seeing is believing:

 

 

 

The Triage Workflow:

WorkFlow

 

 

 

 

The Entitlement Milestone Action:

 

Milestone Actiion

 

 

 

 

The Field Update from the Milestone:

 

Best Answer chosen by Admin (Salesforce Developers) 
GuillermoPGuillermoP

The answer to my problem is this a known bug. 

 

When creating Entitlement Processes, it's possible to configure Field Updates on the Milestones that are related to an Entitlement Process. If the "re-evaluate Workflow Rules after field change" option is selected on the Field Update related to a Milestone, the Field Update action does NOT re-evaluate other workflow rules on the same object as expected.

 

IF anyone else cares or uses this function, please vote this bug up!

 

http://success.salesforce.com/issues_view?id=a1p30000000SU70AAG

All Answers

SF7SF7

Mu guess is the field updates are not happening with an edit , and time based triggers does not go into queue until you edit the record . you can check the last modified date if it is changing when fieeld updates happens.

 

 

GuillermoPGuillermoP

The field update is hitting the last modified action. See the time stamp. But, the workflow is not re-evaluating to trigger the notice.

 

Case Screenshot

GuillermoPGuillermoP

The answer to my problem is this a known bug. 

 

When creating Entitlement Processes, it's possible to configure Field Updates on the Milestones that are related to an Entitlement Process. If the "re-evaluate Workflow Rules after field change" option is selected on the Field Update related to a Milestone, the Field Update action does NOT re-evaluate other workflow rules on the same object as expected.

 

IF anyone else cares or uses this function, please vote this bug up!

 

http://success.salesforce.com/issues_view?id=a1p30000000SU70AAG

This was selected as the best answer