This document briefly describes the enhancements provided with version 8.2.x of the MDTransform product.
|
From Build Date |
Description
|
|---|---|
| April 16, 2019 | If a User Role is defined to be authorized to code 28 (Request to Add, Modify or Delete Objects in MDCMS) and the assignment of a user to that role cause the Licensed MDCMS developer count to be exceeded, a warning message will be displayed to help avert work stoppages due to this situation.
If a User Role is defined to be authorized to code 29 (Request to Add, Modify or Delete Objects in MDOpen) and the assignment of a user to that role cause the Licensed MDOpen developer count to be exceeded, a warning message will be displayed to help avert work stoppages due to this situation. |
| The command API MDUPDUSR can now be used to add or update users with all user parameters as well as add or remove role membership for the user for up to 20 roles at once (or all roles).
MDUPDUSR can also be used to remove users from MDSEC. |
|
| April 30, 2020 | MDSEC Authority code 37 to determine at the application level which users are authorized to edit their own Object Requests |
| MDSEC Authority code 38 to determine at the application level which users are authorized to delete their own Object Requests | |
| MDSEC Authortiy code 16 to determine which users are authorized to export report, spooled or file output via email | |
| MDSEC Authortiy code 17 to determine which users are authorized to export report, spooled or file output to IFS | |
| August 9, 2020 | Flag added to MDSEC user profiles to allow checking of authority for the job’s current user, when the original job user isn’t authorized to an MDSEC function. This provides a mechanism to allow MDSEC to permit authorization to a function after a role-swap. |