• Not Applicable

• 'Active' Activity Definition are present in the System.

• Not Applicable

• Mandatory fields must be defined.

• Not Applicable

• Not Applicable

• Life Cycle State:
  • Pending
  • In Progress
• Mandatory fields must be defined.

• Contact Information and Activity Type cannot be changed once the Activity is created.
• Activities that are assigned to a specific Unit and not to a specific User (pending acceptance) can have all of their fields modified except the 'Assign To' field (must be done through the respective Action).

• Not Applicable

• Pending
• In Progress

• Not Applicable

• Not Applicable

• None of the submitted Resource Requests should be in a 'Pending' Life Cycle State.
• Business rules and restrictions applied through 'Active' Activity Definitions.
• Business rules and restrictions applied through Activity Type.
• Business rules and validations applied through Resource Scheduling Definitions.
  • If "Conditions Forcing Resource Requests on Activity Services" are met then, the Activity won't be able to be saved unless an "Accepted" or "Pending" Resource Requests is present.

• Existing Life Cycle State is 'Pending'.

• Validation on mandatory Services is not applicable while the Activity is in this Life Cycle State.
• It is not mandatory to specify the time spent on each Activity Service while the Activity is in this Life Cycle State.

• All Users can accept an Assignable Entity in CRM.COM provided they are authorised through their Security Profile. For example, Users can accept the assignment of an Activity if the "Accept Activities" additional process is 'Enabled' in their Security Profile.
• The User's Unit during login should be the same as the 'Assigned To' Unit or it should be within the same Group or higher in the Units hierarchy.

• Not Applicable

• Not Applicable

• Any Resource Requests that were submitted against Services of that Activity should be Rejected or Cancelled.

• The Activity should not have a 'Completed' Life Cycle State Completed.

• Not Applicable

• None of the submitted Resource Requests should be pending.
• All mandatory Services should exist.
• The time spent should be specified for each Service that was added to the Activity.
• Business rules and restrictions applied through the 'Active' Activity Definitions.
• Business rules and restrictions applied to the Activity Type.
• Business rules and validations applied through the Resource Scheduling Definitions.

• Existing Life Cycle State is 'In Progress'.

• Not Applicable

• Mandatory fields must be defined.

• 'Active' Communications Definition must exist in the System.

• If Tags are used, the Referring To Entities must be defined first.
• If unrestricted Tags are used, the values of each unrestricted tag under Unrestricted Parameters must be defined.

• Not Applicable

• The Activity Life Cycle State is set to 'Completed'.
• Each Activity Service has a Billing Directive which defaults to 'To Be Billed' by the System. 
• The rates for each Service are specified in the Price Plan which is selected in the Job Billing Terms. 
• The Price Plan rates for Activities are configured using the following Price Plan rates:
  • Flat rate, duration based
  • Tiered rate, duration based.

• Activities are billed through Jobs.

The entities which are related to the Activity and can include one of the following:

• Subscription
• Job
• Service Requests
• Leads

The significant dates of the Activity which include the following:

• Start Date: Defaults to the date on which the Activity is created and which can be modified.
• Estimated Completion Time: Defaults to the Estimated Completion Time set on the related Activity Type. It can be edited and is measured in minutes, hours, days, weeks, years.
  It is 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 on which the Activity is expected to be completed and is equal to the Start Date plus the Estimated Completion Time.
  It is calculated automatically when the Estimated Completion Time is set or modified, although it can also be set manually. 
• Actual Completed Date: The date on which the Activity is completed.
  It is Read-only and set automatically on completing the Activity, i.e. when the Activity is set to a 'Completed' Life Cycle State.
• Time to Completion: The time that is left up to the Expected Completion Date.
• Time Overdue: The time past the Expected Completion Date.
  This information is calculated dynamically, based on the Expected Completion Date and the current date, if the Activity is not completed by the Expected Completion Date.

The Services that are provided as part of the Activity and the time spent on each one, measured in minutes, hours, days, weeks, months and years.
Only One-Time Services can be specified, which should be included in the list of 'Allowed' Services as specified in the related Activity Type.

The Life Cycle State of the Activity which can be one of the following:

• Pending
• In Progress
• Completed
• Cancelled

Notes regarding the Activity. Each time the Notes are amended, the User and the date are logged.

• Unit: The Unit which is to handle the Activity order.

• User: The User who is to handle the Activity order.

  The User field may be left empty.  Users in the defined Unit will subsequently be able to Accept the Activity. Check the respective Action below.

The Action that provides information regarding the Activity, concerning:

• Communications
• Approval Requests

Applies a single fixed price based on the duration of the Services, which starts from a base rate and changes as the duration that was required to provide the Service increases. Multiple flat levels are supported.

Applies a price which starts from a base rate and progressively changes as the duration that was required to provide the Service increases. Multiple tiered levels are supported.