We are attempting to automatically create sales orders from estimates. We have a workflow setup that will successfully transform the estimate into a sales order based upon a saved search.
The problem is, the saved search will continue to show the estimate after the workflow has completed and created the sales order. If the workflow was released as opposed to being in the testing state, the estimate would get multiple sales orders created because it would always show in the saved search the workflow uses as criteria to run.
We have tried every Workflow History criteria we can think of to get estimates to disappear from the saved search after the workflow has completed. None of them have work. The estimate always stays in the saved search, so it creates a new sales order every time the workflow runs on the schedule.
What criteria can we use on the saved search to get it to exclude the estimate after the workflow has completed? Every option we have tried has not been successful.
Saved Search Criteria:
Main Line is True
Type is Estimate
Formula (Text) Description is Closed Won; Formula {entitystatus}
These options will get the estimate to show up in the saved search once the estimate has been moved to the closed won status. This will then allow the workflow (which will eventually be scheduled to run on a set time frame (TBD)) to create the sales order from the estimate.
After the workflow completes and creates the sales order, we need some kind of criteria from the estimate to show that the workflow has completed and the estimate should no longer show in the saved search.
Any idea on what criteria could be used on the saved search to get estimates to no longer be present after the workflow has successfully completed? We have a custom body field on our estimates named Internal Notes (custbody_internalnotes). This is used for internal communications from the sales staff to the warehouse staff with specific information related to the order.
We thought, maybe, we could append text to that field on the estimate as the very last thing the workflow did. We could then update the saved search criteria to exclude any estimate that contained that text. We were not able to figure out how to append text to the field, though. We could set the field in the workflow, but it is used quite often, so we do not want to overwrite existing data. We just wanted to append additional text to anything that might have already been there.