Some objects created by production users (campaigns, for example) are created on the current package.
If they go to out custom package, won't they be lost when a new package version is imported from development ?
What package id & prefix should be used in production environment? "Custom" and "Usr"? Or our custom package id and prefix?
Like
Dear Ricardo,
If one object is located in package A and second in package B, updating package A will not interrupt data from package B.
If you are developing on dev instance and installing the package from dev to prod this package will be locked and no changes will be saved to it.
If you are trying to change unlocked package to locked it will most likely lead to installation issues or functionality issues.
Since it is not expected for new features to be developed on production application you can use Custom package for minor changes.
The prefix should be the same as on dev and it should not interfere with existing customisations (if there are objects on schemas with "Usr" prefix it is not recommended to change prefix).
Best regards,
Angela
Angela Reyes,
Thanks for your reply.
That's exactly how we are working . We are using the same prefix as our custom package that was imported from Dev.
When a production user tries to save a new process,
...he/she gets the message:
... and if he/she is allowed to save it, my concern is also if this new process will be preserved when a new version of the package is imported from Dev.
Ricardo Bigio,
Check the value of Current Package system setting and make sure this package is not locked.
Best regards,
Angela
Angela Reyes,
That is exactly what the problem is. The package IS locked in production, as it was imported from dev. What is the solution for that ? Should we have another custom package in the prod environment specifically for that, where users can save their campaing processes ?
Ricardo Bigio,
You can use Custom package. Each system has a "Custom" package which is unlocked and specified as the default custom package. It is called Custom.
Best regards,
Angela
Angela Reyes,
Thanks. That is the solution we have adopted. The only difference is that we have created another custom package, instead of using the "Custom" package.