Package suddenly changed to "Locked": Deployment risks?
Hello Community,
I’m working on a Creatio Cloud instance (version 8.1.3.3193) and have encountered a challenge with a user-made package.
The Situation:
- I have a user-made package that contains replacing objects for Account and Contact (from the Customer360 app).
- The package was created directly in this environment (not installed via .zip or SVN).
- This package was previously open, but has suddenly changed to a locked status. Despite the lock icon, I am still able to modify and save schemas inside it.
My Questions:
- Will this "locked" status cause errors when transferring the package to Production via .zip export or the Assembly process? or it cannot be trasferred?
- What is the best way to remove this lock?
- If unlocking isn't possible, should I create a new package that depends on this locked one and try to replace the objects again? I'm concerned that a "replacement of a replacement" might cause issues with the core Customer360 functionality.
Thank you for your guidance!
Like
Hello.
If the package icon is greyed out - 
, this means that the package is locked.
This can occur if the package was installed on your site or if the package Maintainer differs from the value specified in the Publisher system setting.
At the same time, this does not mean that the package cannot be installed on another site. If the states of the environments are aligned, you can export the package and install it on another site. Please note that in this case the package will also be installed as locked.
There are two options to unlock the package, temporary and permanent.
To remove the lock, you can either use the Unlock for hotfix action to unlock the package temporarily
https://academy.creatio.com/docs/8.x/dev/development-on-creatio-platform/development-tools/delivery/hotfix-mode , or create a ticket for the support team to unlock the package permanently.
If your package has a lock icon next to it but the package icon itself is yellow 
, this means that the package is unlocked for changes but locked in SVN.
You can find more information regarding this behavior in the following article.
https://academy.creatio.com/docs/8.x/dev/development-on-creatio-platform/development-tools/creatio-ide/operations-with-packages#title-15340-9
Best regards,
Antonii.