Hi Evan,Thanks for looking at this and taking an interest. It would be great if the workflow module really worked. It has great potential. However so far my experience has been quite mixed. [LIST] [*]Lack of documentation - there is no detailed technical documentation about the workflow processing module. Not even as much…

Julie, Does the transition fire when the case is updated or do a bunch of transitions happen on half hour intervals? Prior to 2011.1 you could set up a transition with no "transition on" value and if the condition was a saved search it would be evaluated once every half an hour. That technique "blew up" with the 2011.1…

One workaround is to change the Trigger On to Scheduled which will run every 30 minutes. Using this workaround you are introducing an undesired potential delay of 30:00 minutes from the time the condition is actually met (i.e. subscribed to record is changed) I still with Evan or someone from NetSuite would comment on this…

Recall you don't have criteria for a state -- you have criteria for a transition. In your case it sounds like the test state would need 3 transitions. One scheduled with delay of 1 day to go to the cycle state One on entry to test {today} = '05/31/2011' to take you to the end state. One on entry to test whatever criteria…

... Is there no way to curate a transaction and react to changes in Document Status? -Darren Hi Darren, You can use the strategy I outlined in this thread Basically you'd have a transition that checks the document status on entry to the state and a delayed transition that sets the state to cycle. (see the link for terms).…

Not picking your pattern apart, I used the same one and thought it was fine, but now I'm thinking the Scheduled Trigger may be cleaner. Thoughts? No worries. I developed this after an NS upgrade when it appeared that scheduled triggers were quite broken. They seem to work reliably now and I hope never to use this pattern…

Oddly enough I just figured out a pattern for this sort of test today. It's a bit odd but here goes. Basically you want to be able to have a transition not based on a user event or straight calendar delay. Like you, I had a workflow where the transitions should occur on pre-calculated dates. The pattern is like this: You…

Actually trying to use a formula causes an unexpected error. The way I found to do this is to [LIST] [*]create a stored field on the state that is list record of workflow target type [*]create a custom workflow script that returns the current record id [*]create an action that uses the custom script to set the state field…

I think it was a change in behaviour that occurred between 2010.2 and 2011.1. In 2010.2 I could have a transition that didn't include any "Transition On" value and a configured saved search and it would run once every half an hour and process the transition. This was discovered through trial and error. I presume this was a…

To go dynamically to a record you choose a field in the "ID" field. With a child record, the parent field should be one of the fields available. Thanks, -e I'm just not seeing this. How do I open my current record (the target of the workflow) in edit mode as a workflow action? Scenario: I add a button to a form via a…

Hi Evan, Thanks for looking at this. We're still 2 weeks away from 2011.1

Another workflow on the child record that does a go to record after submit? Evan, How do we dynamically specify the record Id for a Go To Record action? It seems like the only way this works is to create a new record or hard-code a record id. I've been able to work around this (sub-optimally) a couple of times. It struck…

Thanks. That's more or less the workaround I've adopted. It's a PITA though since the way to Approve or Reject a task is different. i.e. I have a button for Approve which shows up whether the record is in view or edit mode. The task is rejected only when the user is in Edit mode and enters a rejection note and saves the…

Yes but I need the reject reason. Once the task has been rejected it is assigned back to the original assignee. I need to either: [LIST] [*]only show the Reject button when the reviewer is editing the task [*]force the task into edit mode (with the field made mandatory and enterable) when they click the reject button.…

Hi Malin, Only production workflow so far (so definitely my coolest!) has 8 states and 14 transitions. A couple of those transitions are to handle the case of existing orders being added to the workflow "mid-process". The customer sends out glasses frames to customers for home try on. The customer has a limited time in…

I've had good luck with the curly braces. Remember if your workflow subject type is sales order then in order to include a customer's first name you'd have to do: {entity.firstname} I've no idea at this point how you'd include the sales rep's standard signature.