•  Active Activities Definition exists in the system

• Not Applicable

• Not Applicable

• Not Applicable

• Mandatory fields must be defined

• Not Applicable

• Contact Information and Activity Type cannot be changed once the Activity is created
• Activities that are assigned on a specific Unit and not on a specific User, meaning that they are pending acceptance, can be modified, but the assigned to User cannot be set or modified. (Has to 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

• Life Cycle State:
  • Pending
  • In Progress

• Not Applicable

• Existing life cycle state is Pending

• 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 the 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 allowed to be saved unless an "Accepted" or "Pending" Resource Requests exists.

• Validation on mandatory services are 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

• Not Applicable

• All users can accept an Assignable Entity in CRM.COM if they are allowed to do so by the security profile assigned to them. For example, users can accept the assignment of an activity if the security profile assigned to them has enabled the "accept activities" additional process.
• The unit that the user used during log in should be the same as the assigned to unit or it should be within the same group and higher in the units hierarchy.

• Not Applicable

• The activity should not have life cycle state Completed

• Any resource requests that were submitted against services of that activity should be Rejected or Cancelled

• Not Applicable

• Existing life cycle state is in progress

• 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 on the activity
• Business rules and restrictions applied through active activity definitions
• Business rules and restrictions applied through the activity type 
• Business rules and validations applied through resource scheduling definitions

• Not Applicable

• Active Communications Definition needs to exist in the system

• Mandatory fields must be defined

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

• 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 key dates of the Activity which include the following:

• Start date: Defaults to the date that the Activity is created, although it is editable
• Estimate completion time: Defaults to the estimated completion time as set on the related Activity Type, although it is editable, 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 that the Activity is expected to be completed and it equals 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 manually set. Automatically calculated or Manually Set
• Actual completed date: The date that the Activity is actually completed. The actual completed date is read-only and is set automatically on completing the Activity i.e., on setting the Activity on a status which is mapped on the completed life cycle state. Automatically calculated
• Time to completion: The time that is left up to the expected completion date. Automatically calculated
• Time overdue: The time past the expected completion date. This information is calculated dynamically, based on the expected completion date and the date of execution, if the Activity is not completed yet and has passed the expected completion date.Automatically calculated

The services that will be 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 can be specified, which should also be included in the list of the 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, which is always set to "To Be Billed" if the Activity is performed for a job having a job type classified as billable. Finally services might be added automatically if they are configured to do so, again 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 for the Activity. Each time the notes are amended, the user and the date are logged.

• Unit:The Unit to handle the Activity order 

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

The action that provides information regarding the Activity, related to:

• 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