• Mandatory Fields must be defined.
• A unique Name and Alternative Code is required.
• At least one Status for each Job Life Cycle State should be specified in Allowed Statuses
• Communication Settings
  • APPLICABLE UP TO CRM.COM R9.0.0You are only allowed to either check the box for sending a Communication via the Type or "Same as Definition"
    i.e. If the "On Creating" box is checked, then the "Same as definition" box cannot be checked
• 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.
• If the Billing Directive is Billable:
  • A Billing Term Scheme must be added and a default scheme must be selected

• Not Applicable

• Not Applicable

• 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.

• Not Applicable

• Not Applicable

• Job Types cannot be deleted if they are being used by Jobs which are not yet completed

• Not Applicable

• Deleted Job Types are still visible on Jobs which were created using those Types. 

Determines if the Jobs related to this Type are billable or not. The supported values are the following:

• Billable
• Not Billable

The scope that Jobs of this Type should follow in order to deliver a Job. The following Job Fulfilment Scope options are available:

• Generic Purpose: Jobs created using this Type will be used to deliver Services and Physical Goods as part of a generic purpose Job
• New Subscription: Jobs created using this Type will be used to deliver Services and Physical Goods as part of signing up a new Subscriber
• Activate Subscription: Jobs created using this Type will be used to order a Subscription activation
• Deactivate Subscription: Jobs created using this Type will be used to order a Subscription deactivation
• Cancel Subscription: Jobs created using this Type will be used to order a Subscription cancellation
• Add Subscription Services: Jobs created using this Type will be used to order Subscription Services addition
• Cancel Subscription Services: Jobs created using this Type will be used to order a Subscription Services cancellation
• Change Subscription Location: Jobs created using this Type will be used to change the location of an existing Subscription
• Swap Subscription Installed Items: If selected then any jobs created using this Type will be used to swap installed items on an existing Subscription
• Swap Subscription Services: If selected then any Jobs created using this Type will be used to swap services on an existing Subscription
• AVAILABLE FROM CRM.COM R11.0.0 - Replace Physical Goods: Jobs created using this Type will be used to replace Traceable Physical Goods which have been sold through a Job. (It cannot be used for replacing Subscription Physical Goods)

The method that should be followed in order to Fulfil the job. The supported methods are the following:

• Based on Ordered Items: If selected, then the delivered Services and Physical Goods should include all the products that were initially ordered by the customer. Additional Services and Physical Goods are not allowed to be delivered. All delivered Services and Physical Goods are billed if the Job is defined as 'Billable'
• Based on Delivered Items: If selected then it is not mandatory to include the ordered products in the delivered Services and Physical Goods. Additional Services and Physical Goods are allowed to be delivered. All delivered Services and Physical Goods are billed are billed if the Job is defined as 'Billable'

Determines when in its Life Cycle a Job can be billed. The supported methods are the following:

• Bill on Starting Progress: Job can be billed when its Life Cycle State is set to "'In Progress'".
• Bill on Completion: Job can only be billed once its Life Cycle State is set to "Completed".

The Products and Product Types classified as Physical Goods that can be added to Jobs of that Type. The following information is specified on each allowed Physical Good:

• A Product or Product Type classified as Physical Goods
• Classification: Mandatory or Optional

The products classified as Expenses that can be added to Jobs of that Type. The following information is specified on each allowed Physical Good:

• A Product or Product Type classified as Expense
• Classification: Mandatory or Optional

Defines the Types of Activities can be applied on this Type of Job. The following information is specified:

• Activity Type
• Classification: Mandatory or Optional
• Billing Directive: Defines if the activity should be Billable or Not billable. This information is available only if the Job Type is billable

Determines the Type of Subscriptions that can be maintained through Jobs of this Type. Multiple Subscription Types can be added, but each Subscription Type can be added only once.

This information is visible and applicable only if the Job Type Fulfilment Scope is one of the following:

• Activate Subscription
• Deactivate Subscription
• Cancel Subscription
• Add Subscription Services
• Cancel Subscription Services
• Change Subscription Location
• Swap Subscription Installed Items
• Swap Subscription Services

The Billing Term Schemes that can be used by Jobs of that Type. The default Billing Term Scheme is also specified in this section.

Mandatory on Conditions: This section is mandatory if the Billing Directive is set to 'Billable'.

The Type of Subscription that can be managed by Jobs of this Type
 

Defines the Billing Term Scheme to be applied on the Subscription that will be created through the Job. The available Billing Term Schemes are filtered based on the selected subscription Type.

Defines the Billing Term Scheme to be used by Jobs of this Type and is set as the default Billing Term Scheme.

The Type of Subscription that can be created through Jobs of this Type.

Based on the Job Type's Fulfilment Scope, some of the following Subscription Action Types will be available as selection box in order to select the subscription action Type to be used while performing the subscription action related to the Job's Fulfilment Scope.

The available Subscription Action Types are the following:

Based on the Job Type's Fulfilment Scope, some of the following Subscription Sub-Action Types will be available as selection box in order to select the Subscription Sub-Action Type to be used while performing the subscription action related to the Job's Fulfilment Scope.

The available Subscription Sub-Action Types are the following:

These are the events for which a Communication will be automatically triggered.

• • On Cancelling: If enabled, then a Communication will be sent whenever a Job is cancelled (i.e. the Life Cycle State changes to 'Cancelled')
  • On Completing: If enabled, then a Communication will be sent whenever a Job is completed (i.e. the Life Cycle State changes to 'Completed')
  • On Creating: If enabled, then a Communication will be sent whenever a Job is created
  • On Starting Progress: If enabled, then a Communication will be sent whenever the progress of a Job starts(i.e. the Life Cycle State changes to 'In Progress')
  • On Updating: If enabled, then a Communication will be sent whenever the requested information of a Job is updated

The Communication template that will be 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 Job for which the allowed transitions are defined. Only one initial Status can be defined per Status Transition per Job Type.

A list of Statuses that can be used as destination Statuses when the specified Status needs to 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.