Archiving options:
Check if the security permissions in Development Environment should be migrated to UAT or Production environment.
- Keep permissions – if the check box is ticked the source environment permissions will be exported. Objects archived with that option can affect the existing permissions on target environment depending on the unarchiving option.
- Unticked – no permissions are exported. If the object already exists in the target environment will maintain the permissions of the target environment. If the object doesn’t exist will inherit the permissions from its new parent folder.
Unarchiving options:
REPLACE: Old – replaces existing objects with last modified date older than the migrated ones. Usually this one is used.
REPLACE: All – replaces existing objects with the same name, overwriting only those that do not have the read-only attribute set
REPLACE: Force – replaces existing objects with the same name, overwriting even those that have the read-only attribute set
REPLACE: None – doesn’t replace the objects if an object with existing name exists on the target environment
ACL: Create – existing groups/roles in the target environment will be used. The groups/roles used by the migrated object that don’t exist in the target environment will be CREATED.
ACL: Preserve – existing groups/roles in the target environment will be used. The groups/roles used by the migrated object that don’t exist in the target environment will be DISCARDED.
ACL: Inherit – assigns permissions of the parent folder on the target environment
