Release Notes EZ-Compliance 2020a-HF2 (build 1.20.10.3262)

Release Notes EZ-Compliance 2020a-HF2 (build 1.20.10.3262)


New and/or Adjusted Functionality

·         Added Employee Supervisor option in the Global User Replace functionality (TICKET 1508)

In the Global Replace functionality the option to Globally Replace the Supervisor is added. Note that the Batch Expiration of Employees also makes use of this Global Replace Functionality, therefor the Batch Replace will now also include the Supervisor replacement.


Bug Fixes

·         Unhandled exception error when viewing history conflicts (TICKET 1464)

Resolved an unhandled exception error when viewing history conflicts in the EZ-Compliance Client application

·         Sub-Process Role/Diagram relationships gets overridden with Parent's Role/Diagram relationships (TICKET 1488)

If a Process has a link to Role and also calls a Sub-Process which also has a link to the same Role, the Sub-Process' link to the Role gets overridden with its parent's process / role attributes such as “Use Activity Authorization" and an "Access Mode" properties. Although this is an uncommon configuration set up, the software has been modified to accommodate this.

·         Adding Resolution Rule is not possible (TICKET 1497)

When adding a resolution rule, the query builder gives an error, preventing the user from adding a resolution rule. This issue has been addressed.

·         Remove timeout on PAR Archive grid loading (TICKET 1498)

The PAR Archive Grid could time-out in situations where there is a large data volume to load. The time-out has been removed to prevent this time out from happening.
·         Added stability in the way that Standard Dynaflow Authorizations are presented in real-time (TICKET 1513)
When Client Admin Center users are created / disabled / removed, the representing Authorization(s) in the Authorizations table are now updated upon existing the Client Admin Center Users grid.
·         DEM Access Scan
In the DEM Access Scan, the resulting access mode is determined based on a cascade of decisions. The ultimate fallback should be the Access Mode of the Access Point. When running the Access Scan in mode “Specific” the fallback was not applied correctly. This has been adjusted.

·         EZ-Compliance Web-Portal

Additional protection was included against shared database connections for customers with large amount of simultaneous opened connections to prevent the web-portal user to receive an error.



    • Related Articles

    • Release Notes EZ-Compliance 2021a-SP2 (build 1.21.12.3937)

      SEE ALSO ATTCHED DOCUMENT New and/or Adjusted Functionality  •             External Access Change Request Id's are to be unique (TICKET 1739) Added protection when creating an ACR based on an external message. In the situation the external request ID ...
    • Release Notes EZ-Compliance 2022a-SP1 (build 1.22.11.4332)

      New and/or Adjusted Functionality Access Scan – EAMS (TICKET 1885) In the Access Scan a new option is added in the section Child Option/Filters. In the sub section “Include Child Access Points in Scan” the option “Both (satellite Sessions ...
    • Release Notes EZ-Compliance 2022a (build 1.22.10.4144)

      New and/or Adjusted Functionality Merge of the EZ-Compliance and EZ-Dashboard client (TICKET 1836)  EZ-Compliance and EZ-Dashboard are merged into one Client Application. The EZ-Dashboard functionality can now be found under the Master Data menu: ...
    • Release Notes EZ-Compliance 2021b (build 1.21.20.3987)

      New and/or Adjusted Functionality openERP Import - multiple descriptions same Diagram/Process Object (TICKET 1806) When importing authorizations any Master Data object which is included in the import file, but not present in the Master Data, is ...
    • Release Notes EZ-Compliance 2020a-HF1 (build 1.20.10.3192)

      See also attached document  New and/or Adjusted Functionality  ·         Added Access Level to "Employee Business Function Access" report (TICKET 1485) The Access Level was added to the Employee Business Function Report. In the situation there were 2 ...