See attached document for full details.
New and/or Adjusted
Functionality
- DEM Import
In the situation that a Process
Activity points to another Process, the Activity-to-Role Access Mode is
assigned to the (sub) Process-to-Role, instead of the Activity’s Access Mode.
- View Parent / Child Diagram
The dialogues View Parent / Child
Diagrams now will show the DEM Diagram/Sub-Processes nested structure.
- Rename “Import/Scan History Log” to “View
Event History Logs”
Since the History Log includes more Events than only Imports/Scan’s the
Name of this Dialogue is renamed to Event Log History
- Global User Replace: Added log results in
Event History Logs
Added the Event Log for the Global
User Replace to the Event Log History, including the details of the User
Replace performed
- DPI (Depth per Inch) Aware
The application is been adjusted
to be fully DPI (Dots per inch) Aware
- Allow Expiration of Completed PAR Owners
Employees who were PAR Cycle
Owners could not be expired, independently of the PAR’ status. The Expiration
functionality has been adjusted so that Owners of Completed PAR Cycles
can now be expired.
- Employee Batch Expiration functionality
In the Employee Dialogue, an option is added to Expire and/or Replace
Employee in Batch. This option can also be automated as part of the
Imports/Scan Automation.
The Batch Expiration is accessible through this dialogue and has the
following main features:
One or more input files can be selected. In case
multiple files are selected, the input files need to have the same format.
The
files need to be of type CSV, and the delimiter can be indicated. Especially
when Employee Names are also to be included, it is highly recommended to NOT
use a comma as a delimiter, since a comma sometimes is used in names.
The only mandatory column of the import file is the
“Account Name” of Employee to be expired.
The normal conditions will apply to determine if
an Employee can be expired. For example, if an Employee is still an Owner of an
Object (eg Control, Role, Employee Supervisor, SoD Owner, Reviewer of an Active
PAR Cycle, Owner of an PAR and/or Cycle, etc) or the Employee has still Authorizations
and/or Conflict, the Employee cannot be Expired.
In the situation the Employee can
NOT be expired and the option “Force Replace of Employees that cannot be
expired” is checked, the process will try to Replace the “To Be Expired
Employee” with the Employee indicated and mapped in the additional columns in
the import file. The Replace, will use the same functionality that is available
in the Global Replace Function.
In the situation the that Replace
By Employee is not in the Employee table, this Employee will be created including
the (optional) attributes mapped in this process.
The configuration can be stored
and re-used. This stored configuration is also used in the automation. Use the
“Automated Import/Scan Configuration” window to create and maintain them.
- Purging History Conflicts by Date
When Purging History SoD
Conflicts, the user can now specify a date and only conflicts identified prior
to (or on) this date will be deleted.
Bug Fixes
- Unable to download File from control history
(TICKET 1417)
Fixed an issue where downloading file attached to a Business Control Testing,
from the Web-Portal History grid could generate an error.
- Handling of special characters in documents
(files) upload and download (TICKET 1441)
In some situation if the document attached to a Business Control testing
Cycle has special characters in its name, it could result in errors. The
handling of special characters has been improved.
- Violation Level filter not taken into account
in Role based preventive scan (TICKET 1457)
Resolved the fact that the Violation
Level filter was not taken into account within the Role-based Preventive Scan.
- Unhandled exception error - history conflicts
(TICKET 1464)
On lower-tiered hardware, loading
the History SoD Conflicts grid could result in a timeout. Improvement have been
done to help this situation.
- Resolution Rule – Copy Repository-to-Repository
Resolved
issue that prevented the Resolution Rule collision options to appear when using
the copy repository-to-repository utility.