...
| Excerpt |
|---|
PCR-360 is capable of generating large amounts of data. Proper data retention policies and clean up processes will help to keep PCR-360 running as optimal as possible. Retention values apply to the length of time data is preserved before being permanently deleted from the application, whereas Aging is how long Services (or other entities, potentially) retain their current data associations before being "cleaned" for reuse. As a last distinction, Retention and Aging are both separate from Archiving, which defines how long data remains in the "primary" tables. Data Retention values define how long, in days, the records are kept. Zero indicates records are cleaned up immediately. A negative number is not allowed, but if left blank the event will not clean up any records. Data Retention Events will only clean up the oldest months worth of data per run until the data retention days threshold. This ensures the system is not bogged down when there is a backlog of records. To utilize this event effectively it is recommended to run weekly. Once caught up, it can be changed to monthly, although any performance gains would likely be negligible. Please contact the helpdesk with questions, or for assistance setting up retention policies. API Request Logs Authentication Log The Authentication Log cleanup event recurs weekly, is set to pending by default, and has a default retention value of 365 days. The retention value is set on the Manage Tenants form.   Bulk Update History The Bulk Update History cleanup event recurs weekly, is set to pending by default, and has a default retention value of 365 days. The retention value is set on the Manage Tenants form. Imports The Delete old Import Files and Imported Records event recurs every day to cleanup records. The retention value for the records is set on the Manage Import File Format form. If the retention value is set too soon it could limit PCR's ability to troubleshoot issues relating to that import format. Messages The Messages cleanup event recurs weekly, is set to pending by default, and has a default retention value of 365 days. The retention value for this event is set on the Manage Tenant form. System Messages (BIll generation, Bulk updates, etc.) and Messages of Inactive Users are effected by this event. The PCR-360 messaging system allows Users to send and receive messages from other PCR-360 users, those messages are not deleted by this cleanup event. |
Adding Email Accounts
...
Users can also add email accounts to the tenant. These accounts serve as the "From" and "To" addresses for the automated email capabilities built into the application. Click on the 'Email Accounts' tab and click the 'Add' button (see image above).
...
In the form (see image above), Admin users are prompted to define a number of required fields for the new email account. This email account specification defines how PCR-360 will send and receive emails. PCR-360 sends email notifications and alerts, and can also "read" incoming emails to a specified email account. For example, if the subject of an incoming email references a specific Service Desk number, the application will add the email to the SD item's Email Thread; if no SD number is specified, the application will create a new Service Desk Inquiry.
...
Select the appropriate Account Type.
MAKE SURE TO USE THE EMAIL ADDRESS YOU WANT PCR-360 TO USE
On the OAuth2 Configuration tab enter Application ID and Secret KEY copied down from the Registering an Application steps above.
Also enter in the following values:
Authentication Authority URL: https://login.microsoftonline.com/common for this example
Authorization Endpoint: /oauth2/v2.0/authorize
Token Request Endpoint: /oauth2/v2.0/token
Scopes (groups, or permissions): openid profile offline_access user.read mail.read mail.send
Save the Email Address
Click the "Click to Authenticate" button
Follow the prompts to authorize PCR-360 with your Email.
Once completed the portal will redirect back to the application with a success message.
The button on the OAuth2 Configuration tab should now say "Click to RE Authenticate"
The application is now configured to send (and/or receive) emails using the email address that was authenticated
...