About workflow rules based on custom views...

Although I'm working with Sage CRM for 7 years now I still discover new things every day.


Today I've remembered that we can create a workflow rule based on a view instead of a table, and it lead me to some new thoughts and I need a few answers to see if it can be done or not.

Considering the Opportunity Workflow, I'd like to create qualification rules that would integrate fields from other tables than Opportunity.

Let me explain :

1) Create a custom view that joins Opportunity, Company, Person, Address, Phone and Email

2) Create a Qualify Company rule, a Qualify contact rule, etc.

3) On these rules I would display Company, Contact, etc. fields and make them mandatory.

My question is : is it possible ? If so does it mean that we can manage Company, Person, Address, Phone and emails fields (ie update any field from these tables) through the Opportunity workflow without needing to duplicate the required fields into the Opportunity table and adding a Execute SQL action to update the related fields in the linked records ?

This would mean I can guarantee in a single process that data (company information including address, contact name, phone and email) is properly qualified before going further in the process for each Opportunity

  • 0

    Views used in Workflow Rules are useful because they allow us to reference a wider set of fields within the JavaScript condition. If we work on the Opportunity we can check the company status too.

    We can imagine the view in the JavaScript condition like

    select * from vsummaryopportunity where....

    BUT, when it comes to updates it is not possible to update a view(*) so the update action will only occur against the main focus of the workflow. That might be the opportunity or case table.

    If you want to update multiple records at the same time then you can use either an ASP page or an Execute SQL workflow action.

    * - Strictly speaking I think it is possible to update a view but all the columns updated must be in the same table.

  • 0

    Thank you for your answer Jeff.

    I was expecting more about CRM and was dreaming about that possibility of implementation but that sounds normal regarding the technical abilities of a SQL view.

    Maybe that could be a major improvement of the solution for the Workflow functionnalities ? This would not be easy to implement but I think it would add a huge advantage upon other solutions for implementing great integrated processes across all departments of companies.

    I would recommend that as data quality and how data driven culture is difficult to understand for users is a major threat to the success of crm implementations. If we could add full control (ie being able to update fields without setting up "tricks" to do so) over other type of records inside the worklow itself would be great !

    Proconsult