(v1) .The Cart v2020.3

The Cart

To open the Cart, just click on the  button.

From the Cart, a User can manage Pending Requests and submit/delete one or more Requests. The User is also given the option to Select All Pending Requests, Deselect All Pending Requests (Select None) or  Select All Pending Requests of one type.

To Select a Pending Request, the User must the small box in the corner of the Request. After a Request is Selected,  it is just the click of a button to  or.

To Delete just a singular Rquest, the User just needs to click the  icon.

In Order to find Pending Requests more quickly, a User can utilize the search bar. The Pending Request search bar works slightly differently than other search bars within PCR-360 in that it will only match based on the Request's Title.

The Cart will only load four (4)  Pending Requests initially.  If more exist a User can load more with the below button, which is located underneath the last loaded Request.

When no more Requests are present to be loaded, the button will display a message for no more Requests in its place.

Types of Pending Requests

• Ready to Submit - These Requests are completed, and are ready to be submitted
• Incomplete - These Requests are missing Required pieces of information and require further action by the User. These Requests are usually marked with the  icon.

Request Management

To add New Services and Equipment and (v1) Packages, see their respective articles for information for adding them to the Cart. 

Each Request is Editable from the Cart. The User can update the Urgency, Owner, the Charge Account, the Description, manage Attachments, and any other User-Defined Fields on the Request. The User can also update Changes to the Service and related Equipment/Packages.

Each Request can also be Titled uniquely to help group the details for each Request.

At the bottom right corner of the Request, a summary of the Charges will be displayed.

Title

A Request can be uniquely named and updated to help a User differentiate multiple Requests being worked on (such as setting up Orders for multiple different Users). To edit the title, click the  icon.

Urgency

Urgency allows the User to indicate how important a Request is. Examples of Urgency are Low, Medium, and High. Depending on Organizational needs, the system may be configured to behave differently depending on the Urgency.

Owner Information

The Owner Information fields are comprised of two separate fields.  The Who Owns This one and the actual Owner one. Together they enable the application to determine who the Own of the Service should be.

Who Owns This

This dropdown consists of three options. Contact, Department and I Can't Find.

• Contact - Selecting this option means the Owner is an individual person.
• Department - Selecting this option means the Owner is a Department.
• I Can't Find - Selecting this option means the Owner is not setup in the application yet, such as a new hire, or a pending new Department.

Owner

The Owner picker is filtered depending on the Who Owns This field.  When set to Contact, the picker will only display Contact records, while when set to Department, the picker will only display Department records.

When Who Owns This is set to I Can't Find the picker becomes a free text field for the User to enter the Owner manually.

Charge Account

The Charge Account is always a Required field if the Service Catalog for the selected Service is "Billable". The GLA picker is restricted by the owner's GLA permissions. The owner is restricted by the logged in user. If the logged in user is not a coordinator, the user becomes the contact owner. Otherwise, the user has access to both the contact and department pickers.

For more information on how the Department Hierarchy or a Contact's association affects GLA permissions, please see the Department Hierarchy and People page.

Description

The Description field is used to describe the need for the Service or any other details related to the Request, but will not necessarily appear on the final product of the Request itself.

Attachments

Any file less than 10Mb in file size can be attached to the Request for review.

Items on the Request

Each individual Service, Standalone Equipment or Package is hidden by default on the Request.  A User can view them by clicking the  button.  They can be hidden once more by clicking the  button.

When expanded () all associated change items will be displayed for that expanded category, and a User will be able to edit the item (), remove the item () or expand () /collapse () a summary of the item's details.

When editing one item in the category, the User can click the button and then navigate directly to others using the andbuttons.

The Cabling Picker will appear on all Service Add Actions, as well as, on Packages. The Cabling Picker is restricted by location on Service and Package Actions. The picker is also restricted by the Service's catalog location restrictions on service actions. The Cabling Picker is not a Required field and will only appear if CC_SHOW_CABLING_PICKER is true.

Services

There are a number of available items available for a Service Request or Equipment Installation.

For new Services being Requested, the most common Service Changes are Add/Install. Other items are more common when a User desires an update to an existing Service.

For Services and Equipment that require a Location, a User has two options:

• Find Existing - This allows the User to select an existing record from the system.
• I Can't Find - Selecting this option means the Location is not setup in the application yet, such as a new building.

For Services being Changed or Moved, the Reference Field is available. This is a free text field for the User to enter information specific to the Action.

Standalone Equipment

Standalone Equipment is any piece of Equipment that is not associated with any specific Service. Equipment that is associated with the Service will appear in the Service Changes section.

Related Packages

(v1) Packages are bundles of related Services and Equipment that your Organization has defined as being needed together.  Packages expedite a User's ability to request multiple commonly needed items at once.

User-Defined Fields

Association Criteria vs. Second Association Criteria

The Service Catalog is the criteria and it can be empty. The Service Desk Action Type is the Second Association criteria and it cannot be empty. The Second Association criteria will default to the "Add" action type.