* APPS-1004/APPS-1005: Retention steps are not updated when moving from another category with a different retention schedule
* APPS-1004/APPS-1005: [AGS] Retention steps are not updated when moving from another category with a different retention schedule
- Added test for APPS-1004 and changed fix to solve another isuue
RM-7106
* APPS-1004/APPS-1005: [AGS] Retention steps are not updated when moving from another category with a different retention schedule
- Added common method to be used by both categoryType and folderType
* APPS-1004/APPS-1005: [AGS] Retention steps are not updated when moving from another category with a different retention schedule
- Added change to reinitialize folders recursively, for the case
where there are multiple subcategories
* APPS-1004/APPS-1005: [AGS] Retention steps are not updated when moving from another category with a different retention schedule
- Added changes suggested at review
* ACS-1781 Config set up and validation
* ACS-1781 Unit tests for config validation
* ACS-1865 Code tidy up
* ACS-1865 Updates from PR review
* ACS-1865 Updates from review
* APPS-1073_Automated Rest API tests for checking Export for Records having size greater than 4MB
* Updated the test files as per Review Comments
* Updated the test files as per Review Comments
Co-authored-by: Shubham Jain <Shubham.Jain@hyland.com>
Co-authored-by: shubhamjain10 <shubham.jain@globallogic.com>
* changes related to retain frozen Records
* RM-6941 add Log entries [ags][skip repo]
* RM-6941 Remove final from the variable declaration
Co-authored-by: bdwiwedi <brij.dwiwedi@globallogic.com>
* Added validation to the ScriptActionExecuter class to enforce the existing constraints on parameter script-ref (Repo has the constraint to only allow scripts in Data Dictionary / Scripts and AGS has the constraint to only allow scripts in Data Dictionary / Records Management / Records Management Scripts") by validating if the given scriptRef is in the allowed valued of the constraint set on that param
* Added a new unit test for AGS to make sure that rmscript action still works as expected when the script is in the correct folder and fails when not
* Added new case in ActionServiceImpl2Test#testExecuteScript to assert that the transaction fails when we execute the action with an invalid script
* Moved test testActionResult from ActionServiceImplTest to class ActionServiceImpl2Test - Before it ran with a script not in Data Dictionary so with the added validation it started to fail. I moved the unit test do avoid duplicating the code to create the script in the correct location.
* Upgrading org.json:json from version 20090211 to 20201115 introduced the issue as getString method in the newer version does not allow for values other than strings
* Replaced getString for the get method
* Original PR in governance-services: https://github.com/Alfresco/governance-services/pull/1448
