•  Active Activities Definition exists in the system

• Not ApplicableNot Applicable

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

• Not Applicable

• 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 on to a specific Unit and not on to a specific User , meaning that they are (pending acceptance, can be modified, but the assigned to User cannot be set or modified. (Has to ) can have all of their fields modified except the 'Assign To' field (must be done through the respective Action)
•  Completed Activities cannot be modified

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

• Editable Fields:

  • Contact Information 
  • Status
  • Category
  • Performed For
  • Services To Be Provided
    • Resources
  • Key Dates
  • Owner Group

• Completed activities cannot be deleted.

• Not Applicable

• Pending
• In Progress

• Not Applicable

• Not Applicable

• Existing life cycle state is Pending

• None of the submitted resource requestsResource Requests should be in a Pending life cycle state'Pending' Life Cycle State.
• Business rules and restrictions applied through active activity definitions 'Active' Activity Definitions.
• Business rules and restrictions applied through the activity type throughthe Activity Type.
• Business rules and validations applied through  resource scheduling definitions Resource Scheduling Definitions.
  • If "Conditions Forcing Resource Requests on Activity Services" are met then, the activity Activity won't be allowed able to be saved unless an "Accepted" or "Pending" Resource Requests existsis present.

• Existing Life Cycle State is 'Pending'.

• Validation on mandatory services are Services is not applicable while the activity Activity is in this life cycle stateLife Cycle State.
• It is not mandatory to specify the time spent on each activity service Activity Service while the activity Activity is in this life cycle stateLife Cycle State.

• Not Applicable

• All users Users can accept an Assignable Entity in CRM.COM if they are allowed to do so by the security profile assigned to themprovided they are authorised through their Security Profile. For example, users Users can accept the assignment of an activity if the security profile assigned to them has enabled the "accept activitiesActivity if the "Accept Activities" additional process is 'Enabled' in their Security Profile.
• The unit that the user used during log in User's Unit during login should be the same as the assigned to unit 'Assigned To' Unit or it should be within the same group and Group or higher in the units Units hierarchy.

• Not Applicable

• Not Applicable

• Any resource requestsResource Requests that were submitted against services Services of that activity Activity should be Rejected or Cancelled.

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

• Not Applicable

• None of the submitted  resource requestssubmitted Resource Requests should be pending.
• All mandatory services Services should exist.
• The time spent should be specified for each service Service that was added on to the activityActivity.
• Business rules and restrictions applied through active activity definitionsthe 'Active' Activity Definitions.
• Business rules and restrictions applied through the activity type to the Activity Type.
• Business rules and validations applied through  resource scheduling definitionsthe Resource Scheduling Definitions.

• Existing Life Cycle State is 'In Progress'.

• Not Applicable

• Mandatory fields must be defined.

• 'Active' Communications Definition needs to  must exist in the systemMandatory fields must be definedSystem.

• If tags will be Tags are used, you must first define the Referring to To Entities must be defined first.
• If unrestricted tags will be Tags are used, you must then define the values of each unrestricted tag under Unrestricted Parameters must be defined.

• Not Applicable

• The Activity life cycle state Life Cycle State is set to "'Completed"'.
• Each activity service Activity Service has a billing directive Billing Directive which defaults to "'To Be Billed" ' by the systemSystem. 
• The rates for each service Service are specified in the price plan Price Plan which is selected in the job billing termsJob Billing Terms. 
• The price plan Price Plan rates for activities Activities are configured using the following price plan 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 key significant dates of the Activity which include the following:

• Start dateDate: Defaults to the date that on which the Activity is created , although it is editableEstimate completion timeand which can be modified.
• Estimated Completion Time: Defaults to the estimated completion time as Estimated Completion Time set on the related Activity Type, although it is editable, . 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 Start Date and Expected Completion Date and is updated automatically whenever the expected closing date is modified.
• Expected completion dateCompletion Date: The date that on which the Activity is expected to be completed and it equals is equal to the start date Start Date plus the estimated completion time. Estimated Completion Time.
  It is calculated automatically when the estimated completion time Estimated Completion Time is set or modified, although it can also be set manually set. Automatically calculated or Manually Set
• Actual completed dateCompleted Date: The date that on which the Activity is actually completed. The actual completed date is read
  It is Read-only and is set automatically on completing the Activity, i.e. , on setting when the Activity on a status which is mapped on the completed life cycle state. Automatically calculatedis set to a 'Completed' Life Cycle State.
• Time to completionCompletion: The time that is left up to the expected completion date. Automatically calculatedExpected Completion Date.
• Time overdueOverdue: The time past the expected completion date. Expected Completion Date.
  This information is calculated dynamically, based on the expected completion date Expected Completion Date and the current date of execution, if the Activity is not completed yet and has passed the expected completion date.Automatically calculatedby the Expected Completion Date.

The services Services that will be are provided as part of the Activity and the time that was spent on each one, measured in minutes, hours, days, weeks, months and years. Only one time services
Only One-Time Services can be specified, which should also be included in the list of the allowed services 'Allowed' Services as specified in the related Activity Type.Services are optional, although they should be specified if they are defined as mandatory in the related Activity Type. All services have a billing directive

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

• Pending
• In Progress
• Completed
• Cancelled

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

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

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

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

The action Action that provides information regarding the Activity, related toconcerning:

• Communications
• Approval Requests

Applies a single fixed price based on the duration of the servicesServices, which starts from a base rate and changes as the duration that was required to provide the service 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 Service increases. Multiple tiered levels are supported.