• Mandatory Configuration Entities must be configured before you start to use Jobs. Refer to Jobs - Configuration Requirements.

•  All mandatory information is specified

• The Job's Life Cycle State is:
  
  • 'Pending'
  • 'In Progress'

• Jobs that are assigned to a specific Unit and not to a specific User are 'Pending' acceptance. They can be modified, but the Assigned To User cannot be set or modified (Must be done via the respective Action).
• If the Life Cycle State is 'Draft'
  • The requested Physical Goods, Expenses and Activity Services are included in the list of Allowed Attributes of the Job Type
  • If the job is Billable then the specified Job Billing Term Scheme and Price Plan are allowed to be used
• If the Life Cycle State is 'Pending'
  • Customer Information, Location, Job Terms should exist
  • Mandatory requested Subscription Services, Physical Goods, Expenses, Activity Services should be part of the ordering information
• If the Life Cycle State is 'In Progress'
  • Customer Information, Location, Job Terms should exist
  • Activities which are created as part of the Job are validated. Resource Requests which are forced on those activities are also validated.

• The Job's Life Cycle State is:
  • 'Pending'
  • 'In Progress'

• Related entities (i.e. Activities, Resource Requests) are also cancelled or deleted.

• Assigned to User field is empty

• Allowed by the User's Security Profile. For example, Users can accept the assignment of a Job if the security profile assigned to them has enabled the ACCEPT JOB additional process
• The Unit that the User used during login should be the same as the Assigned To Unit

• The Job's Life Cycle State is Pending

• All mandatory information is specified
• Mandatory requested items are specified
• If the Job type requires approval based on a Workflow Rule then
  • All Approval Requests are either Accepted, Rejected or Cancelled (i.e. there are no 'Pending' Approval Requests)

• The Job's Life Cycle State is 'In Progress'
• The Activity Types which can be used for Activities performed for the Job are filtered based on the Allowed Activity Types specified in the Job Type.

• Not Applicable

• The Job's Life Cycle State is 'Completed.'
• The Job is set as 'Billable'
• The rates for each provided information are specified in the Price Plan which is selected in the Job billing terms. 
• The Price Plan rates for activity services are configured using the following Price Plan rates:
  • Flat rate, duration based
  • Tiered rate, duration based

• Not Applicable

• The Job's Life Cycle State is 'Not Completed'

• No Physical Goods (traceable or not traceable) have already been delivered by the Job
• The Job does not have any requested or provided Physical Goods that have already been sold to a customer - AVAILABLE FROM CRM.COM R10.0.0
• Subscriptions that were created as part of this Job should be cancelled
• Activities related to the Job should be completed or cancelled
• Any Resource Requests that were submitted against Services of the Job's related Activities should be rejected or cancelled

• The Job is set as 'Billable'
• The Job's Life Cycle State is 'In Progress'

• Not Applicable

The process is available only for Billable Jobs through the Action Panel and for Jobs with the following Life Cycle State is

• 'In Progress'
• 'Completed'

• Not Applicable

• The Job is set as 'Billable'
• The Job's Life Cycle State is:
  • 'Draft'
  • 'Pending'

• Not Applicable

• Existing Life Cycle State is 'In Progress'

• All submitted Activities should be 'Completed' or 'Cancelled'
• All mandatory Activities, Physical Goods and Expenses should exist on the Job
• If the job Fulfilment method is set to 'Based on Ordered Items' then:
• Physical Goods
  • All the requested Physical Goods should exist in the provided Physical Goods, and specifically installed items should exist for traceable Physical Goods
  • The provided Physical Goods should not include any Physical Goods which were not included in the requested Physical Goods
• Expenses
  • All the requested Expenses should exist in the applied Expenses. 
  • The provided Expenses should not include any Expenses that were not included in the requested Expenses
• Activity Services
  • All the requested Activity Services should exist on completed Activities which were performed as part of the Job
  • The completed Activity Services should not include any Activity Services which were notrequested,unless they are not Billable

• The Job's Life Cycle State is:
  • Draft
  • Pending
  • In Progress
• The Job Type is defined as billable
• The Job has not yet been billed

•  Not Applicable

The address that the Bill will be sent to.
If Billing Address is already defined for an existing account, then this address is selected and is Read-only. The Billing Address can be modified by clicking on MODIFY BILLING ADDRESS.

The address at which the Job will take place. For example, if it is an installation Job, this is the address the installers will be going to.
An existing Contact Information or Billing Address can be selected or details can be provided for a new address by checking the checkbox 'Same as Billing Address'.

The Type of the Job.
Types will be filtered based on:

• • The Fulfilment Scope of the Job which was selected when creating the Job
  • the Job Types allowed to be used by the User based on their Unit and the Allowed Organisational Units set at the Job Type

The phone number of the customer that the Job is created for and to which all Communications will be sent (if mobile). The retrieved phones are those related to the specified customer. The selected phone can also be edited, although this will not be reflected on the Contact Information.

If no phone number is defined, communications with SMS Media will not be created.

The email address of the customer that the Job is created for and to which all communications will be sent. The retrieved emails are those related to the specified customer. The selected email address can also be edited, although this will not be reflected on the Contact Information.

If no email address is defined, communications with Email Media will not be created.

The terms that are applied on the Job and include the following:

• • Scheme: The Billing Term Scheme which will be used for billing the Job
  • Price Plan: The Price Plan from where the billing rates of Physical Goods, Expenses and Activity Services will be taken
  • Agreement Date: The date the job was registered

The Subscription Type which will define the overall behaviour of the Subscription.
This is a Read-only field and is set automatically by selecting the Job Type.

The Billing Term Scheme which will define the billing rules for the Subscription.
This is a Read-only field and is set automatically by selecting the Job Type.

The important dates of the Job which include the following:

• • Start Date: Defaults to the (editable) date that the Job is created
  • Estimated Completion Time: Defaults to the estimated completion time as set on the related Job Type. It is editable and measured in minutes, hours, days, weeks and years. It is calculated as the difference between the start date and expected completion date and is updated automatically whenever the expected closing date is modified.
  • Expected Completion Date: The date that the Job is expected to be completed. It is equal to the start date plus the estimated completion time. It is calculated automatically when the estimated time of completion is set or modified, although it can also be set manually.
  • Read-only fields
    • Time to Completion: The time left up to the expected date of completion
    • Time Overdue: The time past the expected completion date. This is calculated dynamically based on the expected completion date and date of execution, if the Job is not completed and is past the expected completion date.
    • Actual Completion Date: The date that the Job is actually completed. The Actual Completion Date is Read-only and is set automatically when the Job is completed i.e. when setting the Job on a status which is mapped to a 'Completed' Life Cycle State.

Distributorsare available when a Subscription Physical Good or a Subscription Service must be defined. The Distributor must be selected before the Physical Good or Service, as Subscription products are filtered according to their Distributor.

The Physical Goods that the customer requests. eg. A Smartcard and Decoder.

The Installed Items that are provided to the customer.
The associated Distributor must be selected to see the Installed Items that were provided to the customer.

The Services that can be requested by the customer, either for addition on the Subscription or swapping with existing Services.

The Services that are provided to the customer.

Traceable Physical Goods bought by customers and now require replacement.

The Physical Goods to be replaced

If the Physical Good to be replaced is covered by a Warranty Policy then select the Coverage Reason in order to find out whether the Physical Good Coverage:

• Coverage: Yes, means the new Physical Good will not be charged
• Coverage: No, means the new Physical Good will be charged.
  View Warranty Policies for more information

The Physical Goods that can be requested by the customer, which can either be Traceable or Non-Traceable.  Requested Physical Goods differ from Subscription Physical Goods, in that they can be added on a Job and then billed, without being associated to the Subscription.

The Physical Goods that are provided to the customer.

The Expenses that can be requested by agents, and that the customer will be charged with.

Mandatory Expenses are added automatically. Only products classified as Expense Services can be added to this list

The Expenses that the account of the customer will be charged with.

The One Time Services that can be requested by the customer and should be delivered through scheduling and performing an Activity.

The Activities which are planned for the Job, sorted by their Life Cycle State.

The attachments associated with the Job

It determines whether the Job was processed by the Billing engine or not. The available rating states are the following:

• PENDING: The Job was not rated yet
• COMPLETED: The Job was already rated

The Life Cycle State of the Job which is automatically updated when changing the status and can be either:

• • Draft
  • Pending
  • In Progress
  • Completed
  • Cancelled

Notes for the Job. Each time the notes are amended, the User and the date are logged.

• Unit: The Unit to handle the Job order 

• User: The User to handle the Job order
  User field may be left empty and then Users in the Unit defined will be able to Accept the Job. Check the respective action below.

Job actions provide the major actions that can or must be performed on a Job.

Check the related section below for more information on each action:

• Start Progress

• Schedule an Activity

  AVAILABLE FROM CRM.COM R12.0.0 'Schedule an Activity' Action is available only if at least one Allowed Activity Type is defined through the Job's Type and the Job's Life Cycle State is set to 'In Progress'

• Provide Ad Hoc Discount
• Preview Rates
• Preview Bill
• Bill Job
• Complete Job
• Cancel Job

A list of all the Communications, in which the Job is defined in the 'Referring To' field of the Communication.
View Understanding Communications for more information 

A list or Approval Requests related to the Job.
Workflows can be configured to create Approval Requests each time a User updates the Job so that a User with approval rights can approve the amendments.
View Managing Approval Requests for more information.