Lead workflow. Location of insert fields view

Help please!  I need help determining where the system stores the view associated with workflow emails for leads.

One of my collegues created a custom workflow to be used for leads.  When I attempt to add fields to email created within a workflow, I only have lead fields available.  Therefore, I was going to track down the associated view and see if I can modify it.  After looking into it, it appears for the out of the box workflow the view would be vNotificationsLead and it is a CoreView.  Since it is a CoreView, it cannot be modified.  However, when I review the view, it appears to be exactly what I need.  However, it does not appear to be what is being used as I only see lead table fields.

I am assuming this is stored somewhere in the database for the workflow.  However, I have not yet been able to determine where.  Does anyone know where the view is defined for usage with the workflow email insert fields.  

Any assistance would be greatly appreciated.  Thank you!

Parents
  • Not sure how it derives the merge list, but it does utilise vNotificationLead. so you can use manually insert fields from that view... e.g #comp_name# if its matched to a company

  • Thank you Shaun!  I believe I have figured where it knows which fields to use.  Sharing here in case someone else has the same question.  :-)

    It appears to derive the merge list from the WorkflowRules table.  When creating a new rule, you are able to choose if you want to use a table or a view.  In the above screenshot, the Lead table was selected.

    When I take a look at the WorkflowRules table, for this install, if I filter the wkrl_entity = 'Lead', I can see that the rule that I want to create the email for is set to use a table (Lead) and not a view.  Therefore, wkrl_table = 'Lead'.  Since the Lead table is being used and not a view, I am only able to see fields from the Lead table.  If this becomes wkrl_table = 'vNotificationLead', I am then able to access all the fields in that view for my email.  Yeah!  :-)

Reply
  • Thank you Shaun!  I believe I have figured where it knows which fields to use.  Sharing here in case someone else has the same question.  :-)

    It appears to derive the merge list from the WorkflowRules table.  When creating a new rule, you are able to choose if you want to use a table or a view.  In the above screenshot, the Lead table was selected.

    When I take a look at the WorkflowRules table, for this install, if I filter the wkrl_entity = 'Lead', I can see that the rule that I want to create the email for is set to use a table (Lead) and not a view.  Therefore, wkrl_table = 'Lead'.  Since the Lead table is being used and not a view, I am only able to see fields from the Lead table.  If this becomes wkrl_table = 'vNotificationLead', I am then able to access all the fields in that view for my email.  Yeah!  :-)

Children
No Data