• Mandatory Fields must be defined.
• A unique Name and Alternative Code is required.
• In relation to Status Transitions:
  • Any Status included in Status Transitions of an Entity Type is also included in the Entity Type's Allowed Statuses.
  • There is one Status Transition for each of the Allowed Statuses of Entity Types which are not final (i.e. not Completed).
  • There are no Status Transitions related to an initial ('Draft') Status which is related to a final Life Cycle State.
  • There are no duplicate Statuses among the initial Statuses in the Status Transitions, the destination Statuses or the initial and destination Status of a single Status Transition.
  • One Status Transition should be present for each (available) Life Cycle State Transition, i.e. two Status Transitions with initial Life Cycle State 'Draft' and destination Life Cycle State 'Pending' can be present provided they have distinct Allowed Organisational Units.

• Mandatory Fields must be defined.
• A unique Name and Alternative Code is required.
• In relation to Status Transitions:
  • Any Status included in Status Transitions of an Entity Type is also included in the Entity Type's Allowed Statuses.
  • There is one Status Transition for each of the Allowed Statuses of Entity Types which are not considered as final (i.e. not 'Completed').
  • There are no Status Transitions related to an initial ('Draft') Status which is related to a final Life Cycle State.
  • There are no duplicate Statuses among the initial Statuses in the Status Transitions or the destination Statuses.
  • One Status Transition should be present for each (available) Life Cycle State Transition, i.e. two Status Transitions with initial Life Cycle State 'Draft' and destination Life Cycle State 'Pending' can be present provided they have distinct Allowed Organisational Units.

The Importance Level that the Lead should automatically be set to for each Lead Type. The Importance Levels are standard and pre-defined in the System but Users can define supported Levels, their labels and the default Level, through the Lead Definitions.

View Configuring Lead Definitions for more information.

The Priority Level that the Lead should automatically be set to for each Lead Type. The Priority Levels are standard and pre-defined in the System but Users can define supported Levels, their labels and the default Level, through the Lead Definitions.

View Configuring Lead Definitions for more information.

This information, measured in minutes, hours, days, weeks, months or years, is used to set the Estimated Completion Time for Leads of each Type.

The Lead Statuses which can be used in Leads of each Type. At least one Status per Life Cycle State should be specified in this section. The default Lead Status is also specified in this section.

Defines which Physical Goods and Product Types can be added to Leads of each Type as Physical Goods that the Lead is interested in. If nothing is specified, then all are available.

Defines which Services and Product Types classified as Services can be added to Leads of each Type as Services that the Lead is interested in. If nothing is specified, then all are available.

Defines the Activity Types which can be scheduled through Leads of each Type to conduct tasks that are needed for the Lead to be completed.

The Events that will trigger a Communication, if enabled.

• • On Create: A Communication will be sent whenever a Lead is created.
  • On Start Progress:  A Communication will be sent whenever the Lead starts to progress (i.e. the Life Cycle State changes to 'In Progress').
  • On Lost: A Communication will be sent whenever a Lead is won (i.e. the Life Cycle State changes to 'Won')
  • On Win: A Communication will be sent whenever a Lead is lost (i.e. the Life Cycle State changes to 'Lost')
  • On Update: A Communication will be sent whenever a Lead is updated.
  • On Cancel: A Communication will be sent whenever a Lead is cancelled (i.e. the Life Cycle State changes to 'Cancelled').

The Template that is used to create the Communication for the Trigger/Event.
Only 'Effective' Communication Templates with an 'Outgoing' Direction can be selected.

The initial Status of the Lead for which the allowed transitions are defined. Only one initial Status can be defined per Status Transition per Lead Type.

A list of Statuses that can be used as destination Statuses when the specified Status must be changed. Each entry consist of the following:

• To Status:The Statuses available for selection.
  One or more Statuses must be defined.
  
• Allowed Organisational Conditions: The Units or Users allowed to change the specified Status. This condition is optional; if no Organisational Units are defined then all Users are allowed to change the Status of the entity.