On the Settings menu, click Configuration. The Configuration page is displayed.
This page contains: ShowHide
The Configuration page enables you to configure system wide settings in IRC, such as environmental settings, system settings, notification template settings and archival settings. This page also enables you to modify the global configuration settings for approval process templates and user creation requests, and remove the Infor adapter.
Configuration settings are grouped under their respective tabs and panels.
To take action on this page, users must be assigned the following roles or custom roles containing the required permissions:
Role |
Actions |
Administrator, System Manager, System Manager (SaaS) |
View and configure settings. |
This tab enables you to configure the following settings. It is necessary to begin a new IRC session after modifying and saving the settings in this section:
In the From Address field, provide an address that will identify the sender of email notifications (a mailbox setup for IRC or an individual’s account).
In the Incoming Account field, provide the email address for the account that will receive and process emails from IRC users. For example, if a user unsubscribes to an event, or if a reviewer discusses an exception with another reviewer, the emails interchanged between reviewers are processed through this account.
Click Save.
Users receiving emails from IRC will be able to send their responses through an email to the IRC system.
This panel enables you to provide the details of the email account used to receive these incoming emails.
Provide the following details:
In the Email Protocol field, select the protocol of the email account. The default is MicroSoft Exchange Server.
In the Security field, select whether the server hosting the email account is secured or not secured. If the receiving account is a gmail account, you must select the secured option.
From the Exchange Server Version drop-down list, select the required version for the exchange server. Exchange server versions 2003, 2007 and 2010 are supported.
Specify the details of the server hosting the email account. For example, if the email account used is a gmail account, it needs to be POP3 enabled. In this case you need to specify pop.gmail.com.
In the User Name and Password fields, provide the credentials for the email account.
For Microsoft Exchange Server protocol: The format should be: domainname\username
For POP3 protocol - Mention only the user name
In the Port Number field, provide the port number of the server hosting the email account. If the account used is a gmail account, the port number must be 995.
Click Save.
Use this panel for the following:
To make it mandatory to assign compensating controls to exclusions when mitigating violations from the Violation Browser by selecting the check box Make Compensating Controls mandatory for mitigation. By default, this is mandatory. Clear the check box if assigning compensating controls to exclusions should not be mandatory.
To enable users to view only the compensating controls that are attached to the violated rule while mitigating violations, select the check box Filter Compensating Control by Rule.
The settings on this tab apply to Authorizations Insights for SAP, Oracle, PeopleSoft and SAP EP and enable you to configure the following:
Specify whether IRC should automatically be assigned to mapped users.
Specify the roles that should be automatically assigned.
Manually map users if required.
Automatic Role Assignment
During a full extraction, IRC users are mapped to extracted users if the option Map Connection Users is selected while creating a connection. Configure the settings below if mapped users should automatically be assigned roles.
Automatic Continuous Monitoring role assignment: Select Yes to automatically assign roles. If you select Yes, the Select roles for automatic assignment field is enabled .If you select No, roles must be manually assigned to mapped users.
Select roles for automatic assignment: To assign roles to mapped users, select the required roles from the list on this page.
Upload list of Users: See the section on manual mapping below.
After configuring the above settings, click Save.
Manual mapping
IRC enables you to upload a CSV file containing a list of ERP users and the name that these users should be given in this application. For example, assume that user John exists in different connections under different names but needs to be given the same IRC name. This could be done by uploading a CSV file containing John's name from the different connections and the name that he should be mapped to in IRC. When the CSV file is uploaded, data from the file is loaded into a database table. Every time a new file is uploaded, the new information is appended to the existing information.
When users are extracted, IRC checks that the users from the CSV file are present in the connection. Users not found in the connection will be skipped. Mapping is performed on the basis of a unique identifier, which in this case is the ERP user name. The mapped users are then given the new name and are displayed in IRC with this new name.
It is possible to subscribe to an email notification containing a report listing how many users were manually mapped and how many were skipped or ignored during mapping.
The format of the CSV file is as specified below. The file should be a common file for all connections:
User Name |
Mapped Name |
J Jones |
JJ3232 |
S Adams |
SA5789 |
Note: Multiple users from a single connection should not be mapped to a single IRC user for the same connection.
In the field Upload list of Users, click Browse to locate the file and click the Upload icon to upload it. Ensure that the CSV file is uploaded before performing the extraction as manual mapping does not impact previously extracted users.
During extraction, manual mapping will take priority over automatic mapping. The mapped names are reflected when browsing for a user from any page in IRC. The mapped user names are displayed as violations or exceptions on the Violations browser and the Exceptions browser respectively.
Use this setting to restrict users (including users with the Administrator role) from modifying tasks created by other users . By default, Administrators can view and modify all tasks.
Select the check box Restrict administrator task view to logged in user's view so that users can view all tasks but may modify only those tasks that they own.
These settings are applicable for Process Insights. These settings enable you to limit the number of exceptions displayed in reports, based on rule priorities. The exceptions limit can either be set collectively for all priorities or for individual priorities.
Eliminate Duplicates - By default, duplicate exception entries are removed before exceptions are written to the database. To retain the duplicate exception entries, select the option No.
BCP chunk size for exception writer in MB:- From the drop-down list, specify the number of exceptions in one chunk to be written to the database. The default data size is 500 MB.
MAX exceptions for all types of priorities - From the drop-down list, select the maximum number of exceptions to be displayed in reports all for priorities collectively. By default, 10000 exceptions are displayed.
MAX exceptions with priority as low /medium/high/informational : Provide the required value in these fields to modify the exceptions limit by priority.
Self assign exceptions while closing : Select this check box to automatically assign an exception to a user trying to close the exception. This option does not apply to assigned exceptions. This check box is not selected,by default.
Analysis Settings- Authorizations Insight
These settings allow you to specify the number of violations that should be displayed for an Authorizations Insight analysis. These settings are to be configured for the required ERP as follows:
These settings allow you to limit the number of role and user violations generated in an Authorizations Insight for Lawson analysis as well as the number of rules that are analyzed at a time. For users with large data volumes, this could significantly reduce the time required for an analysis.
Role violation cap: From the drop-down list, select the maximum number of role violations that should be generated during an analysis. The rule engine stops evaluating the rules once this limit is reached. Values are set in multiples of 1000. For example, if 100000 is the value set, this means up to a 100,000,000 role violations will be generated.
The default value is 0. This means all violations will be generated during an analysis.
User violation cap: From the drop-down list, select the maximum number of user violations that should be generated during an analysis. The rule engine stops evaluating the rules once this limit is reached. Values are set in multiples of 1000. For example, if 100000 is the value set, this means up to a 100,000,000 user violations will be generated.
The default value is 0. This means all violations will be generated during an analysis.
Rule chunk size: From the drop-down list, select the number of rules to be used in analysis. For example, if you select 30 rules while scheduling an analysis and the rule chunk size specified here is 10, data is analyzed three times using 10 rules at a time. The default value is 20.
After configuring the above settings, click Save.
Note: If the violation cap is hit, a notification is displayed on the respective reports. The Violations browser does not display any such notification.
These settings allow you to limit the number of role and user violations generated in an Authorizations Insight for ION Applications analysis as well as the number of rules that are analyzed at a time. For users with large data volumes, this could significantly reduce the time required for an analysis.
Role violation cap: From the drop-down list, select the maximum number of role violations that should be generated during an analysis. The rule engine stops evaluating the rules once this limit is reached. Values are set in multiples of 1000. For example, if 100000 is the value set, this means up to a 100,000,000 role violations will be generated.
The default value is 100000. This means all violations will be generated during an analysis.
User violation cap: From the drop-down list, select the maximum number of user violations that should be generated during an analysis. The rule engine stops evaluating the rules once this limit is reached. Values are set in multiples of 1000. For example, if 100000 is the value set, this means up to a 100,000,000 user violations will be generated.
The default value is 100000. This means all violations will be generated during an analysis.
Rule chunk size: From the drop-down list, select the number of rules to be used in analysis. For example, if you select 30 rules while scheduling an analysis and the rule chunk size specified here is 10, data is analyzed three times using 10 rules at a time. The default value is 20.
After configuring the above settings, click Save.
Note: If the violation cap is hit, a notification is displayed on the respective reports. The Violations browser does not display any such notification.
These settings allow you to limit the number of role and user violations generated in an Authorizations Insight for SAP analysis as well as the number of rules that are analyzed at a time. For users with large data volumes, this could significantly reduce the time required for an analysis.
Role violation cap: From the drop-down list, select the maximum number of role violations that should be generated during an analysis. The rule engine stops evaluating the rules once this limit is reached. Values are set in multiples of 1000. For example, if 100000 is the value set, this means up to a 100,000,000 role violations will be generated.
The default value is 0. This means all violations will be generated during an analysis.
User violation cap: From the drop-down list, select the maximum number of user violations that should be generated during an analysis. The rule engine stops evaluating the rules once this limit is reached. Values are set in multiples of 1000. For example, if 100000 is the value set, this means up to a 100,000,000 user violations will be generated.
The default value is 0. This means all violations will be generated during an analysis.
Rule chunk size: From the drop-down list, select the number of rules to be used in analysis. For example, if you select 30 rules while scheduling an analysis and the rule chunk size specified here is 10, data is analyzed three times using 10 rules at a time. The default value is 20.
After configuring the above settings, click Save.
Note: If the violation cap is hit, a notification is displayed on the respective reports. The Violations browser does not display any such notification.
Analysis Settings - PeopleSoft HR
These settings allow you to limit the number of permission list, role and user violations generated in an Authorizations Insight for PeopleSoft HRMS analysis as well as the number of rules that are analyzed at a time.
PermissionList violation cap: From the drop-down list, select the maximum number of permission list violations that should be generated during an analysis. The rule engine stops evaluating the rules once this limit is reached. Values are set in multiples of 1000. For example, if 100000 is the value set, this means up to a 100,000,000 permission list violations will be generated.
The default value is 0. This means all violations will be generated during an analysis.
Role violation cap: From the drop-down list, select the maximum number of role violations that should be generated during an analysis. The rule engine stops evaluating the rules once this limit is reached. Values are set in multiples of 1000. For example, if 100000 is the value set, this means up to a 100,000,000 role violations will be generated.
The default value is 0. This means all violations will be generated during an analysis.
User violation cap: From the drop-down list, select the maximum number of user violations that should be generated during an analysis. The rule engine stops evaluating the rules once this limit is reached. Values are set in multiples of 1000. For example, if 100000 is the value set, this means up to a 100,000,000 user violations will be generated.
The default value is 0. This means all violations will be generated during an analysis.
Rule chunk size: From the drop-down list, select the number of rules to be used in analysis. For example, if you select 30 rules while scheduling an analysis and the rule chunk size specified here is 10, data is analyzed three times using 10 rules at a time. The default value is 20.
After configuring the above settings, click Save.
Note: If the violation cap is hit, a notification is displayed on the respective reports. The Violations browser does not display any such notification.
Analysis Settings - PeopleSoft FI
These settings allow you to limit the number of permission list, role and user violations generated in an Authorizations Insight for PeopleSoft FISCM analysis as well as the number of rules that are analyzed at a time.
PermissionList violation cap: From the drop-down list, select the maximum number of permission list violations that should be generated during an analysis. The rule engine stops evaluating the rules once this limit is reached. Values are set in multiples of 1000. For example, if 100000 is the value set, this means up to a 100,000,000 permission list violations will be generated.
The default value is 0. This means all violations will be generated during an analysis.
Role violation cap: From the drop-down list, select the maximum number of role violations that should be generated during an analysis. The rule engine stops evaluating the rules once this limit is reached. Values are set in multiples of 1000. For example, if 100000 is the value set, this means up to a 100,000,000 role violations will be generated.
The default value is 0. This means all violations will be generated during an analysis.
User violation cap: From the drop-down list, select the maximum number of user violations that should be generated during an analysis. The rule engine stops evaluating the rules once this limit is reached. Values are set in multiples of 1000. For example, if 100000 is the value set, this means up to a 100,000,000 user violations will be generated.
The default value is 0. This means all violations will be generated during an analysis.
Rule chunk size: From the drop-down list, select the number of rules to be used in analysis. For example, if you select 30 rules while scheduling an analysis and the rule chunk size specified here is 10, data is analyzed three times using 10 rules at a time. The default value is 20.
After configuring the above settings, click Save.
Note: If the violation cap is hit, a notification is displayed on the respective reports. The Violations browser does not display any such notification.
These settings allow you to limit the number of responsibility and user violations generated in an Authorizations Insight for Oracle analysis as well as the number of rules that are analyzed at a time. For users with large data volumes, this could significantly reduce the time required for an analysis.
Responsibility violation cap: From the drop-down list, select the maximum number of responsibility violations that should be generated during an analysis. The rule engine stops evaluating the rules once this limit is reached. Values are set in multiples of 1000. For example, if 100000 is the value set, this means up to a 100,000,000 responsibility violations will be generated.
The default value is 0. This means all violations will be generated during an analysis.
User violation cap: From the drop-down list, select the maximum number of user violations that should be generated during an analysis. The rule engine stops evaluating the rules once this limit is reached. Values are set in multiples of 1000. For example, if 100000 is the value set, this means up to a 100,000,000 user violations will be generated.
The default value is 0. This means all violations will be generated during an analysis.
Rule chunk size: From the drop-down list, select the number of rules to be used in analysis. For example, if you select 30 rules while scheduling an analysis and the rule chunk size specified here is 10, data is analyzed three times using 10 rules at a time. The default value is 20.
After configuring the above settings, click Save.
Note: If the violation cap is hit, a notification is displayed on the respective reports. The Violations browser does not display any such notification.
These settings allow you to limit the number of role, user and group violations generated in an Authorizations Insight for SAP EP analysis as well as the number of rules that are analyzed at a time.
Role violation cap: From the drop-down list, select the maximum number of role violations that should be generated during an analysis. The rule engine stops evaluating the rules once this limit is reached. The default value is 0, or no violation cap.
Values are set in multiples of 1000. For example, if 500 is the value set, this means up to a 500000 role violations will be generated.
User
violation cap: From the drop-down list, select
the maximum number of user violations that should
be generated during an analysis. The rule engine stops
evaluating the rules once this limit is reached. The
default value is 0, or no violation cap.
Values are set in multiples of 1000. For example, if
500 is the value set, this means up to a 500000 user
violations will be generated.
Group violation cap: From the drop-down list, select the maximum number of user group violations that should be generated during an analysis. The rule engine stops evaluating once this limit is reached. The default value is 0, or no violation cap.
Rule chunk size: From the drop-down list, select the number of rules to be used in analysis. For example, if you select 30 rules while scheduling an analysis and the rule chunk size specified here is 10, data is analyzed three times using 10 rules at a time. The default value is 20.
After configuring the above settings, click Save.
Note: If the violation cap is hit, a notification is displayed on the respective reports. The Violations browser does not display any such notification.
These settings enable you to configure What-if analyses and requests by ERP:
This setting is applicable for all What-if analyses.
From the Number of days to retain (What-ifs only) drop-down list, select the number of days for which the What-if analyses must be retained in IRC. What-ifs with the status reviewed and forced completed are purged from the application server after the expiry of this setting. The completed What-ifs (with or without violations) are not be purged.
Select the check box Allow comments during Request mitigation to allow Approver comments while mitigating requests.
Select the check box Expand What-If Violation chart by default for the expanded view of the Violation Chart panel on the Violation Details page.
What-if and Request Settings - Lawson
These settings apply only to Authorizations Insight for Lawson.
You can configure the following settings on this panel:
Display Existing Violations (for What-ifs): Select Yes if already existing violations for a specific What-if analysis are to be displayed on the Violations Details page.
Display Existing Violations (for Requests): Select Yes if already existing violations for a specific request are to be displayed on the Violations Details page.
After configuring the above settings, click Save.
What-if and Request Settings - ION
These settings apply only to Authorizations Insight for ION Applications.
You can configure the following settings on this panel:
Display Existing Violations (for What-ifs): Select Yes if already existing violations for a specific What-if analysis are to be displayed on the Violations Details page.
Display Existing Violations (for Requests): Select Yes if already existing violations for a specific request are to be displayed on the Violations Details page.
Violations cap: Select a value to limit the number of violations to displayed.
Rule chunk size: From the drop-down list, select the number of rules to be used in the What-If analysis. For example, if you select 30 rules while scheduling an analysis and the rule chunk size specified here is 10, data is analyzed three times using 10 rules at a time. The default value is 20.
After configuring the above settings, click Save.
What-if and Request Settings - SAP
These settings apply only to Authorizations Insight for SAP. Use this feature to configure What-if analyses and requests for SAP.
You can configure the following settings on this panel:
Analyze locked users (for What-if): Select Yes if users locked in SAP are to be included as part of What-if analyses. The display of users in the Select Users drop-down list, while creating a Role Assignment Management What-if, depends on the option selected in this field.
Analyze locked users (for Request): Select Yes if users locked in SAP are to be included in request analyses. The display of users in the Select Users drop-down list, while creating a Role Assignment Management Request, depends on the option selected in this field.
Display Existing Violations (for What-ifs): Select Yes if already existing violations for a specific What-if analysis are to be displayed on the Violations Details page.
Display Existing Violations (for Requests): Select Yes if already existing violations for a specific request are to be displayed on the Violations Details page.
Role violation cap: From the drop-down list, select the role violation limit for What-if and request analyses. Role violations will be generated till this limit is reached.
User violation cap: From the drop-down list, select the user violation limit for What-if and request analyses. User violations will be generated till this limit is reached.
After configuring the above settings, click Save.
What-if and Request Settings - SAP EP
These settings apply only to the Authorizations Insight for PeopleSoft HRMS. Use this feature to configure what-if analyses and requests for PeopleSoft HRMS.
You can configure the following settings on this panel:
Display Existing Violations (for What-ifs): Select Yes if already existing violations for the specific what-if analysis are to be displayed on the Violations Details page.
Display Existing Violations (for Requests): Select Yes if already existing violations for the specific request are to be displayed on the Violations Details page.
Violation cap: From the drop-down list, select the violation limit for a What-if and request analysis. No further violations will be generated after this limit has been reached.
Rule chunk size: From the drop-down list, select the number of rules to be used in analysis. For example, if you select 30 rules while scheduling an analysis and the rule chunk size specified here is 10, data is analyzed three times using 10 rules at a time. The default value is 100.
After configuring the above settings, click Save.
What-if and Request Settings - Oracle
These settings apply only to the Authorizations Insight for Oracle. Use this feature to configure What-if and request analyses settings for Oracle.
You can configure the following settings on this panel:
Display Existing Violations (for What-ifs): Select Yes if already existing violations for the specific What-if analysis are to be displayed on the Violations Details page.
Display Existing Violations (for Requests): Select Yes if already existing violations for the specific request are to be displayed on the Violations Details page.
Violation cap: From the drop-down list, select the violation limit for What-if and request analyses. Violations will be generated after this limit is reached. By default, No Cap is selected, which means there is no limit on the violations generated.
Rule chunk size: From the drop-down list, select the number of rules to be used in analysis. For example, if you select 30 rules while scheduling an analysis and the rule chunk size specified here is 10, data is analyzed three times using 10 rules at a time. The default value is 100.
After configuring the above settings, click Save.
What-if and Request Settings - PeopleSoft FISCM
These settings apply only to the Authorizations Insight for PeopleSoft FISCM. Use this feature to configure What-if and requests analyses for PeopleSoft FISCM.
You can configure the following settings on this panel:
Display Existing Violations (for What-ifs): Select Yes if already existing violations for the specific what-if analysis are to be displayed on the Violations Details page.
Display Existing Violations (for Requests): Select Yes if already existing violations for the specific request are to be displayed on the Violations Details page.
Violation cap: From the drop-down list, select the violation limit for a What-if and request analysis. No further violations will be generated after this limit has been reached. By default, No Cap is selected which means there is no limit on the violations generated.
Rule chunk size: From the drop-down list, select the number of rules to be used in analysis. For example, if you select 30 rules while scheduling an analysis and the rule chunk size specified here is 10, data is analyzed three times using 10 rules at a time. The default value is 100.
After configuring the above settings click Save.
What-if and Request Settings - PeopleSoft HRMS
These settings apply only to the Authorizations Insight for PeopleSoft HRMS. Use this feature to configure What-if analyses and requests for PeopleSoft HRMS.
You can configure the following settings on this panel:
Display Existing Violations (for What-ifs): Select Yes if already existing violations for the specific what-if analysis are to be displayed on the Violations Details page.
Display Existing Violations (for Requests): Select Yes if already existing violations for the specific request are to be displayed on the Violations Details page.
Violation cap: From the drop-down list, select the violation limit for a What-if and request analysis. No further violations will be generated after this limit has been reached. By default, No Cap is selected which means there is no limit on the violations generated.
Rule chunk size: From the drop-down list, select the number of rules to be used in analysis. For example, if you select 30 rules while scheduling an analysis and the rule chunk size specified here is 10, data is analyzed three times using 10 rules at a time. The default value is 100.
After configuring the above settings, click Save.
