Timeline for Bests practices for handling potential errors as a result of time based workflow
Current License: CC BY-SA 3.0
11 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| S Jan 14, 2014 at 23:32 | history | bounty ended | CommunityBot | ||
| S Jan 14, 2014 at 23:32 | history | notice removed | CommunityBot | ||
| Jan 8, 2014 at 20:33 | answer | added | Tim Smith | timeline score: 2 | |
| Jan 7, 2014 at 23:16 | history | edited | Ralph Callaway | CC BY-SA 3.0 |
added 408 characters in body
|
| Jan 7, 2014 at 23:12 | comment | added | Ralph Callaway | Yep, monitoring is sweet. Just trying to see if there were any approaches to error handling in triggers, since .addError doesn't have the usual effect since no one is there to get the error. Only thought I had was email, but am curious to see if the community has any thoughts. | |
| Jan 7, 2014 at 8:46 | comment | added | Sindoora | To monitor the workflow action:Adminstration setup---monitor--time based workflow. Did u run the workflow in developer console. It is easy to debug through developer console | |
| Jan 6, 2014 at 23:06 | history | tweeted | twitter.com/#!/StackSalesforce/status/420330507365535745 | ||
| Jan 6, 2014 at 22:31 | comment | added | eyescream |
If you're OK with not performing the update at all - why not add Owner:User.CountOfActiveOnes__c < Owner:User.LimitOfActiveOnes__c to the workflow's formula? (yes, I do realize this syntax looks batsh*t crazy. Must be some recent change to finally mitigate the OwnerId = Lookup(User, Queue)).
|
|
| S Jan 6, 2014 at 21:48 | history | bounty started | Ralph Callaway | ||
| S Jan 6, 2014 at 21:48 | history | notice added | Ralph Callaway | Draw attention | |
| Dec 21, 2013 at 2:05 | history | asked | Ralph Callaway | CC BY-SA 3.0 |