Service Catalog Grid Example

The Services Catalog lists any type of Service that the User's organization could provide to Customers or other Users. If a User deems a specific type of Service necessary to fulfill an item from the Service Desk, the User can order the appropriate Service from the Services Catalog. Catalog Services can also be designated available to Customers through the PCR-360 CustomerCenter.

Adding a Service

Add New Service Catalog Example

Adding new Service

To add a new Service, click the "Add" button in the top toolbar of the main Services grid. In the appearing form, you will notice that there are three required fields that are the minimum requirements for creating a Service: 'Name', 'Type' and 'GLA'. All other fields are optional.

Form Fields

Field Name	Required	Field Description
Name	Yes	The name of the Service.
Description	No	A brief description of the Service. A more detailed description can be provided under the "Catalog" tab.
Type	Yes	The type of the Service.
Format	No	Format mask for the Service ID.
Aging (days)	No	A non-negative (including zero) number of days after the Service becomes inactive that it is eligible for automatic Service Aging . When a new Catalog is created as a child of an existing Catalog, the new Catalog will inherit the Aging value of its parent. The value may be cleared to force Services of that Catalog to use the Tenant's Service Aging Days setting, or changed to another value as desired.
GLA (Revenue)	Yes	The GLA that this Service uses for Billing purposes.
Object Code	No	The Object Code that this Service uses.
Install Time (hours)	No	The default amount of time that this Service requires for installation.
Remove Time (hours)	No	The default amount of time that this Service requires to be removed from Service.

Format

The 'Format' field will set a mask for the Service. For example, Phone number formatting would be entered into this field as: "(999) 999-9999". This will make it so the phone number will display with the correct parenthesis, spacing, and hyphen, as well as control the length of the phone number. This allows the User to simply search or add "6165551212" and get a result of "(616) 555-1212". To set five-digit dialing, another example might be "9-9999" which in turn would convert "12345" into "1-2345" when searching for the Phone Number.

As of version 2.1.4.0, the length of the Auth Code is also controlled by the Format mask. To set an Auth Code length of 7 digits, use seven consecutive 9's like this: "9999999". To create multiple Auth Codes with different lengths, create separate Service Catalogs for each required Auth Code length.

As of version 2.1.4.3, the length of the Auth Code can be allowed to have a variable length. To add a variable length to the Auth Code insert a single "?" into the normal Format string. For example, in order to make an Auth Code that can be either 6 or 7 digits long write a Format like this: "9999?9". The digit that is replaced with the "?" will determine the minimum number of digits that the Auth Code can have.

9 is a placeholder used when the Format mask needs to be set as a number.

* is any Alpha-Numeric Character [A-Za-z0-9].

Child Record's Format

As long as a Child Service record shares the same type as it's Parent Service record, the Child will inherit the format from the Parent record unless a separate format is explicitly created on the Child record.

Service Types

When setting the Service Type, the type will determine which Service grid the Catalog will display on. Phones to Phones, Data to Data and so on. The only exception is the 'Task' Type, which will never go to a grid. The reason is Task Service Catalogs will not save data to a Service when they are added to a Service Desk Action. Task Types are useful for creating any one-time Actions that should not be tracked long term. For this reason, like Orders, Task Catalogs will not be able to save Monthly-Recurring Charges.

Form Field Rules

Category

If a Service is a 'Category' it cannot be Assignable.
Category Service Catalog's can contain children nodes and can have Permissions that the child nodes will.

Assignable

If a Service is 'Assignable' it cannot be a Category.
Assignable Service Catalogs will become assignable within the Service Desk module.

Prorate

The 'Prorate' flag will allow the Service to be prorated when it is added to be billed.
The Billable flag MUST be set for the Prorate flag to be set.

Billable

This will make the Service 'Billable' by default when it is added to the Action.

Location Required

When the Service is created the 'Location' will be a required field.
If checked, this Service must be assigned to a Location.

Requires Approval

The 'Requires Approval' flag will make any Service with this flag require and approval before it can be assigned.

Orderable

If a Service is 'Orderable' it will show in the CustomerCenter.
The Orderable flag will make the Catalog tab visible. The information on the Catalog tab is what will appear on the CustomerCenter.

Report 911

The Report 911 flag will set the Service's Report 911 flag by default.
If checked, this Service's data will be included in the 911 data feed.
Only 'Phones' can have the 'Report 911' flag.

Tabs

Name	Description
Catalog	Provide a catalog description and images.
Expense Object Codes	Add any applicable Expense Object Codes.
Default Charges	Add any default Charges that correspond to this Service.
Location Permissions	Provide any Location specific Permissions that apply to this Service. Can also inherit Permissions from its parent, if applicable.
Service Host Permissions	Provide a default Service Host and any supplemental Service Hosts.
Equipment Permissions	Provide specific Equipment that can be used with this Service. Can also inherit Permissions from its parent, if applicable.
Billing Group Permissions	Provide which Billing Groups apply to this Service.
Attachments	Provide any file attachments that should accompany this Service.
Incident Codes	Provide specific Incident Codes that pertain to this Service.
User Defined Fields	Provide any custom form fields that are needed in general.

Arranging the Hierarchy

To arrange the hierarchy (parent-child relationships), please see the main Catalog page.

Browser not supported