Migrate
Updating to the Second-Generation Managed Package
Last updated
Was this helpful?
Updating to the Second-Generation Managed Package
Last updated
Was this helpful?
The primary blocker when switching between generations of the Managed Package is managing the access that users have to GRAX features and components. The first-generation package includes legacy permission sets that can be used to control user access, but the second-generation relies on permission sets created by the GRAX application during Auto Config. When removing the first-generation package, users assigned the legacy permission sets need to be updated to the equivalent set to avoid interruptions.
For more details on GRAX's permissions model, see our Permissions documentation.
For migration purposes, the non-defunct legacy permission sets map as follows:
GRAX Configuration Admin
GRAX Console Admin Permission
GRAX Advanced User
GRAX Console Power Permission
GRAX User
GRAX Console Standard Permission
All other legacy permission sets have no equivalent and are defunct. They can be dropped from users without consequence.
The following steps and script can be used to automatically perform the mapping shown above for all users in your org.