(v1) .Integrating with PCR-360 v2022.1

Built-in Features for Integrating with 3rd Party Applications

Getting the most out of your available tools can greatly increase productivity and make your organization run smoothly. As such, PCR-360 has a number of useful features that can be used to Integrate with 3rd Party Applications. Your organization can utilize the Imports/(v1) Exports, the API, or other Internal Integration Systems. These features will help your organization streamline it's operational workflows by allowing the exchange of information between PCR-360 and 3rd Party Applications.

The best method for integration to use depends on how much data needs to be sent at once, how frequently the interaction needs to occur and if the 3rd Party Sending Information also needs a Response from PCR-360.

If you would like to see all examples of Customized Integration or Custom Logic designed to enhance PCR-360 functionality, please look at our Custom Logic Library page.

Import/Export Integrations

Numerous File Formats can be defined so that PCR can read-in new information or send-out current information. It can take some time for Import/Export Processes to run within PCR-360, as they run alongside all other processes within PCR-360, so this makes it a bad use if a high amount of individual communications need to be performed. But because it is its own dedicated process, this allows for a single communication to process very large amounts of data at once. This is ideal for use in nightly synchronizations when time is of little concern.

Example Formats

• Vendor Charge Import
• Calls Import
• Usage Import
• E911

API Integrations

PCR-360 has a number of defined Endpoints as well as the ability for users to create their own Custom API Endpoints. Custom API Endpoints and the SQL Endpoint can send our information to 3rd party applications, while other Endpoints will only inform the 3rd Party Application if their request to generate new information within PCR-360 was a success or not. The API Endpoints do not rely on specific PCR-360 Processes, so they make for excellent integrations using a large number of small transactions over the course of a day. This speed does come at a cost of being unable to create numerous amounts of data from a single API Call, often requiring an individual API Call for each record to be created.

Internal Integrations

There are several features within PCR-360 built specifically to allow PCR-360 to easily communicate with some types of 3rd Party Applications. PCR-360 supports Single Sign-On, Email and Call Manager integrations.

Types of Integrations

Single Sign-On Systems

About

PCR-360 can be easily configured to integrate with a number of 3rd Party Authentication Applications. This will enable your organization to manage all permissions within PCR-360 by using the same system that controls other permissions. This can improve user experience by not needing to manage multiple logins and simplifies support for things such as Password Resets and general Permission Management.

Examples

• LDAP
• Shibboleth

Ticket Interfaces

About

If your organization is already using an external ticketing system, it can be integrated into PCR-360 so new tickets created in that system can be added automatically to (v1) Service Desk. This integration will allow your current ticketing system to also be able to benefit from PCR-360's workflows within Service Desk and related Service and Equipment features, without having to require any new steps for creating a ticket.

Examples

• ServiceNow
• Remedy
• Team Dynamix
• Cherwell

Financial/Accounting Interfaces

About

Your organization's current Financial or Accounting Software can be set up to integrate with PCR-360 so that all Billing data can be exported to the Financial/Accounting System. This will help keep any 3rd Party Software your organization is using stay up to date with changes made to Charges within PCR-360.

Examples

• Banner
• Peoplesoft
• Workday
• SAP

Email Systems

About

PCR-360 supports several types of Email Protocols for integration. Please see the (v1) Configuring Email wiki article for the specific details on all protocols and information. This integration enables your organization's customers to be able to submit inquires directly into PCR-360 by sending an email.

Examples

• O365
• Gmail
• Sendmail

Call Managers

About

PCR-360 as a Communication Module for Interfacing with Avaya and Cisco Switches. This module requires a separate license. Please contact Professional Services to request a license, and confirm your system meets all requirements.

Examples

• (v1) Avaya
• (v1) Cisco
• MS Teams

Messaging Systems

About

Using PCR-360's Custom API Endpoint functionality, your organization can integrate with Instant Messaging applications, such as Slack to let users cross-communicate via alerting the Instant Messaging Users when a new Ticket is created within Service Desk.

Examples

• Slack

Scanners

About

The Barcode API Endpoint requires a separate license and can help to rapidly update PCR-360 based on changes to your organization's Inventory and Warehouse management facilities' needs. Please contact Professional Services to request a license if your organization is interested in this integration.

Examples

• Big River Barcode Scanning Apps

Custom Middleware

About

PCR-360 can use the flexible nature of (v1) AdHoc Grids to generate customized reports to translate information for multiple different kinds of consumers. Often in large organizations different people in different areas understand the same the same information in very different ways. By using these AdHoc grids, one User can generate a report that is more readily understandable by a different group.

Examples

• PAN Interface
• Custom Reports
• (v1) AdHoc Grid Library

Questions?

If your organization still has questions about possible ways to Integrate PCR-360 with 3rd Party Applications you are currently using or are interesting in adding, please submit a General Request from help.pcr.com. PCR is happy to answer any questions your organization has.