CRM Processes in Aurea CRM.Web

Learn about CRM process and their assignment rules.

You can assign CRM processes as defined in the Rights module to individual user interface elements. For further details, see Assigning CRM Processes. When a user logs on with a role, he sees only those elements in Aurea CRM.Web that he is allowed to see based on the CRM process definition. Elements that have no CRM process assigned are always visible unless they are hidden based on a rights restriction.

CRM processes can be assigned to the following configuration units:

  • menus (context and application menu as well as the assignment to a parent menu)
  • menu actions
  • buttons
  • tabs/groups in a Details control
  • tabs in sub-lists (Header configuration for SearchSublist and ExpandChildren)
  • nodes in a Tree view
  • items in forms (panels, tabs, rows, cards, buttons etc.)
  • queries and analyses
  • Web Configuration parameters
  • processes
  • items on ProcessAsk pages (except If...End If)

In UPDATE_DEFAULT CRM processes are assigned to menus, menu actions and buttons.

Note: Quick Search entries cannot be controlled by assigning CRM processes. You may want to define the Quick Search per role using the QuickSearch.Definition Web Configuration parameter. For further details, see QuickSearch.Definition.
Note: To hide/lock part of a global Quick Search definition, you can use the rights definition (locked info areas are not available in the Quick Search), or if you use a global CRM Process Configuration where all CRM processes are locked by default you can unlock the desired CRM processes per role and thus restrict the Quick Search to the corresponding info areas.

The SDK page ,CRMProcessesandRoles, provides an overview over the CRM processes by state, displaying their availability (Read Only/Disabled/Enabled) according to the active role(s) as well as the current info area rights settings. For further details, see SDK.