Task and Service Properties

task and service properties provide the foundation for how analytics in activate categorises, measures, and reports on activity across the platform these properties define key metadata such as reporting groups, service level expectations, automation indicators, and cost assumptions for both services and tasks by configuring these properties, organisations can ensure analytics reflects how services and tasks are structured, how performance is assessed against slas, and how value and cost savings are calculated this document outlines where these properties are defined, how they are maintained, and how they are used by analytics to generate consistent, meaningful reporting the following properties are used by analytics on tasks and services the properties are configured at //resources/properties/serv and //resources/properties/task they are stored in the sql tables serviceproperties and taskproperties reporting groups the reporting groups are also collected and stored under //resources/configuration/analytics these reporting groups are used as drop down lists on the web forms to allow users to select updating properties these tables store a cached snapshot of the current task and service property values at the time they were last collected the snapshot is refreshed during the nightly analytics background process, which runs //tasks/analytics/background/scripts/backgroundscript analytics queries read from this snapshot rather than directly from live configuration data, ensuring consistent and performant reporting if property values appear out of date in analytics, confirm that the backgroundscript is correctly referenced and included in your nightly processing schedule service properties property name description reportgroup this is the report group that the service will be reported under this defaults to the top level service name under //services for example, 'applications', 'hardware' etc a special reportgroup of 'none' can be used to exclude the service from analytics sla approval the length of time in business minutes that an approval by the business should take before the request is considered out of sla the default value is 1080 minutes which is 2 business days sla fulfillment the length of time that the service should take to provision in business minutes the default value is 15 minutes this is assuming the request is automated isorderable can users order this service this is based on the permissions on the service isautomated is this request considered automated this is used to group some reports the default value is based on =/orderprocess/isautomatated isoption is this a child option for a grouped service orderonly is this an order only service this is based on the flags on the service costperrequest the total cost savings for this service task properties property name description reportgroup this is the report group that the task will be reported under this defaults to the top level task name under //tasks for example, 'distribution lists', 'passwords' etc a special reportgroup of 'none' can be used to exclude the task from analytics sla,approval the length of time in business minutes that an approval by the business should take before the request is considered out of sla the default value is 1080 minutes which is 2 business days sla fulfillment the length of time that the task should take to provision in business minutes the default value is 15 minutes this is assuming the request is automated costperrequest the total cost savings for the request per item the default value is $20 costperjob the total cost savings for the request the default is number of items costperrequest