Problem Statement: Whenever a new module gets created via a packaged solution, the user has to explicitly set up the module security permissions for the incoming modules in target environment. {For EWF Report, Table and Variant page adds a new module}
This could be tedious if we need to set it up for even a handful users (say 20-30) and this becomes more tedious if the same needs to be done for multiple modules.
Solution:
As a solution we are exposing user groups from the source system which the consultant can set up permission for and add to the incoming package so that the target system would have all those permissions set for the user groups and any underlying user would automatically get the required permissions.
Must Have Sucess Criteria
-Adding user groups to packages so that the underlying module and resource security permissions can be set using the package in the target system.
-Export all content of the user group on Package download.
-Fail the import, if the underlying modules of the user group does not exist in the target system.
-Allow inclusion of user groups in packages without much validation.
-Do not include "Assigned Users" details in the JSON export.
-On Upsert of the user groups, maintain the assigned users in the target system. This would completely be ignored in the export and import of the user groups.
Should Have Sucess Criteria
-Filtering of user groups in a way that only relevant user groups get populated for selection under any package.
-Improved JSON export of user group modules based upon what the package needs.