New and/or Adjusted Functionality
Added "creation" logs to Access Point's log when Access Points are created (TICKET 1980)
At various places in the Application where an Access Point could be created the Creation event was not logged in the Access Point log history. The creation for the Access Point has been added in the following places:
- Open-ERP import
- Authorization Sync Access Point
- Business Function Import
- Baan Menu Import (Authorizations)
- Baan Session Import (Authorizations)
- Access Point Import (Baan, Custom, Child Baan, Child Custom)
- Copy Repository to Repository
Automated Role expiration upon DEM Import (TICKET 1987)
In the situation a DEM Role is expired (in the DEM file using tgbrg810.expi) the DEM Import will try to expire the DEM Role. The normal Expiration Validation is applied. If the validation allows the expiration, the Dem Role is set to Expired.
Report "Business Control Testing Schedule Report" (TICKET 2004)
The report now shows the grid with pages instead of endless scrolling
Automated SoD Conflicts Export (TICKET 2006)
A parameter is added to enable to export all conflicts instead of "per company".
DEM Access Scan (TICKET 2017)
Adjusted DEM Scan statistics for more clarity. The statistics will now specify
- DEM Authorizations from this DEM Access Scan
- Total Number of DEM based Authorizations
- Total Number of Authorizations
DEM Import (TICKET 2021)
Added a new Statistic, "Unique # of Active Employees with Roles". Main purpose is to help validate the completeness of the DEM Import.
Administration Client - Conflict Grid (TICKET 2023)
Corrected the fact that there were duplicated columns related to the Authorization Employee Group.
Environment Settings – Notifications Folder (TICKET 2024)
The parameter “Automated SoD Conflicts Export (per Company): Also attach report (when size permits it)” displays as a sub section of “SoD Conflicts Scan Auto Email File Attachment” while it is not. Lay-out has been adjusted to reflect that this is a separate parameter.
Web Portal Report: PAR as Owner - report id-44 (TICKET 2026)
The calculations which control the in which color the PAR Cycle is showing, has been adjusted.
The calculation done for the green/yellow and red is as follow:
- % Complete Number lines reviewed / Total Number of line to be reviewed
- % Days lapsed Number of days passed / Total Number of days allowed
Green :
[% Complete >= 1] or
[% Complete / % Days Lapsed >= 1]
Yellow :
[% Complete / % Days Lapsed >= 0.75 and < 1.0]
Red
[Close Date is in the past AND % Complete <1] or
[% Days Lapsed >=1 AND % Complete <1] or
[% Complete / % Days Lapsed < 0.75]
DEM Import with AMS Report (Ticket 2035)
In the situation the User is not yet present in the EZ-Compliance database, the user is to be present in both the DEM file and the AMS report to be created.
PAR Web Portal Reports (TICKET 2036)
The function select all / deselect all, does not take into account any filtering which applied. This could lead to the situation that certain records which are filtered out, are still selected, which is undesirable. Since these are 2 separate functions which can not work together, the button “Select All / Deselect all” are inactivated in the situation a filter is applied.
Bug Fixes
Employee Import (TICKET 1973)
does not create log when an SMTP error occurs on sending the notification
Repository Statistics - # of distinct APs in conflicts (TICKET 1978)
The number of distinct Access Points in Conflicts will now only take the active conflicts into account and no longer also the History Conflicts.
Repository Statistics – Print (TICKET 1984)
Resolved an unhandled exception error in the situation the user would first print the repository statistics and then cancel the command.
Client – Adding Testing Schedules (TICKET 1990)
Resolved a layout issue when adding testing cycles and selecting a Business Control, the list of Controls to select from was not displayed properly.
Web Portal Report Control Testing Schedule (TICKET 1991)
Resolved an issue that not all Scheduled Cycles are include din the report “Control Testing Schedule”.
Web Portal report “Business Process Details” (TICKET 1992)
Resolved an issue which caused Report "Business Process Details (id=18) to come up empty
Enable/Disable PAR (TICKET 1993)
In the situation that a PAR is saved with the Enabled Check mark set, when the same record is opened again and the check mark Enabled is unchecked, but the record is not saved yet. Currently it is allowed to save the record with the check mark Enabled as Unchecked and the PAR Cycle is put in Progress after it is opened. A protection is added that the record can not be saved with the Enabled Checked Mark unchecked if the PAR cycle is in Progress.
Business Controls by Risk Matrix (TICKET 1997)
Resolved an issue that the relationship between a Risk and Control was not properly reflected on the intersection in the Matrix.
The option Authorization vs Access Review in the contextual menu is not only available for completed PAR Cycles.
Prefilled User on Login (TICKET 2000)
If "Use Network Id for login" is in use, EZ-Compliance Admin Center's login form does not save the "last user" correctly (was saving the user account instead of network id)
Web Portal - My Business Control Testing Cycle - View Work Items (TICKET 2011)
Resolved an issues where the viewing of the Work Items of a Cycle would result in an error message for archived cycles.
From the Conflict Reports contextual menu select the option View Role 1 Information. The pop up window was missing the Role Description. His has been corrected.
Create New Business Function (TICKET 2013)
Upon creating and saving a new Business Function in the Client Application, the attribute Application was not saved. This is corrected.
Access Point - Import from Baan Report (TICKET 2020)
In the situation an Access Point is created from the Import from Baan Report, the Last Updated Date not properly filled. This is now corrected.
Web Portal - Company Owners - id 156- (TICKET 2034)
One of the column heading was displaying the wrong label as column heading.
Open-Application import log details
The number of import files in log of the open Application Import could be incorrect, since it would count all files instead of only the .eza files. Now the log reflects only the count of the .eza files.