Hello guys,
We have move Sugar 7 Pro to Sugar 7 Enterprise.
Now, we can use Process module instead of Workflow module.
This is Workflow, we need to migrate to Process (Opportunity Module):
Hello guys,
We have move Sugar 7 Pro to Sugar 7 Enterprise.
Now, we can use Process module instead of Workflow module.
This is Workflow, we need to migrate to Process (Opportunity Module):
I think you cannot compare the current value with old in advance workflows.
However, you can follow this link (http://support.sugarcrm.com/Documentation/Sugar_Developer/Sugar_Developer_Guide_7.8/Architecture/Advanced_Workflow/Exten… ) extend the process author.
I did by creating a new module called previous_values. Add the fields you want to compare into this module then use a logic hook on the saved module to store the "fetched" value into the previous value field. Then you can compare the previous_value.field with the module.field to see if it was changed inside process author.
Not ideal but it's a workaround.
Thanks for Brad.
But I need to solution with automation via Process. Because I have talked one example, but I need more other same type of field.
Similar situation here. Would like process to do the following:
- Start - Detect Opportunity records with updates
- Was update made to Sales Stage field?
- If yes, send email.
- If no, end process.
Our process triggers an email alert to managers when opps are updated. However, the update is really only relevant if certain fields are changed. For example, if the Sales Stage was upgraded from RFP to Won, that's something managers care about. If the sales stage doesn't change, but the user updates something inconsequential (adds a sentence to the description field, for example), that creates a lot of unnecessary emails.
Change detection for specific fields would be a very useful feature to add to process author. I'm not keen on workarounds that require us to create a bunch of extra custom fields to keep track of changes.
I think this will help you http://support.sugarcrm.com/Knowledge_Base/Advanced_Workflow/Recognizing_To_and_From_Field_Values_in_Advanced_Workflow/i…
Thank you
Am I interpreting this correctly? It seems like you need a single "from" value to be defined in the start-event step, with subsequent actions covering each potential "to" value. If you have a drop-down field with, say, 15 values, that means you'd need 15 distinct process definitions covering each potential "from" value.
Create before Save Logic hook...
in before save Logic Hook u can compare Old value and new value (updated)..