Configuring System Settings
You configure system settings to control system-level behavior such as email notifications. Use the Settings card in the Tools cluster to access system settings. You must be a Service Administrator to configure system settings.
Notification Settings
Notification settings enable you to configure the way the system sends email notifications.
- From Tools, select Settings.
- Perform an action:
- In Send Notifications, click the check box to enable or disable sending email notifications for the entire system.
- In Email Subject Prefix, enter a prefix for the subject line of system-generated emails to identify the environment from where the email was sent.
- In Substitute Recipient, select a single default user to which emails should be sent instead of the primary recipient (such as request assignees, request collaborators, and request approvers). This can be useful when testing notifications in a test system. Only users with a defined email address are displayed.
- In Attach Subscription Request File, click the check box to enable or disable automatically including the request file that was used to generate the request items in a subscription request as an attachment to the notification emails that get sent to subscription assignees and collaborators.
- Click Save.
Request Settings
Request Rejection Settings
You can prevent users from rejecting requests by request type. For example, you may not want users to have the ability to reject consolidation requests.
- In Prevent Rejection for Request Types, click Selected.
- In Select Request Types, use the drop down box to select
one or more request types that you want to prevent rejection for:
- Interactive
- Subscription
- Consolidation
- Import
- Load
For the request types that you selected, users will no longer have the Reject action available to them.
Request Deletion Settings
Use the Prevent Deletion for Submitted Requests checkbox to prevent users from deleting requests that have already been submitted. When this option is enabled, if a user attempts to delete a request in the Submit stage that has already been submitted (for example, a pushed back or recalled request), they are prompted to close the request instead. Closed requests cannot be resubmitted.
Request Purge Settings
Request purge settings enable you to set the number of months after which request actions for completed requests are automatically purged from the system. This can reduce the size of your migration snapshot files.
- You can set the number of months after which request actions are purged from 6 to 18 months.
- After a request is purged, you can still view the request items (for example, in the Request Inspector or the Request Worklist), but you can no longer expand each request item to see the request actions for that item, and you can't download the request item details.
- The transactions for purged requests are still available in transaction history. See Auditing Transaction History.
- The purging of completed request actions takes place on a weekly basis, and after request actions are purged they cannot be recovered.
Calendar Settings
Calendar settings enable you to specify the end of the fiscal year for your organization. This setting is used by time labels to produce rolling time labeled viewpoints based on a Fiscal calendar rather than the Gregorian calendar. See Creating, Editing, and Deleting Time Labels.
Use the drop down menu to select the last month in your fiscal year.