Question

working Package got greyed out in onsite integration

Hi,

After importing the package into the onside environment , our working package got greyed out.

any help on this, 

Thanks

Like 0

Like

1 comments

JUAN PABLO OSUNA DE LEON,

Hello,

 

In most cases the package is being transferred from dev site where it was developed to prod site where no development should be done, therefore once the package is installed to the target site (prod site in this example) it's locked, as no further development should be done directly on the prod site, and if you need to apply changes to the package, you should do so on dev site and transfer changes with the package once again. One more thing to mention, if you are about to install the package once again to the target site where such a package already exists, it should be locked on the target site for customizations to be applied properly.

According to the logic mentioned above, after installing the package transferred from dev site is locked on your on-site instance.  



The package can be unlocked with the help of the corresponding script, but unfortunately, due to security reasons, we cannot share it. If your onsite instance can be accessed from external IPs and you can contact us at support@creatio.com and grant us external access, we can unlock the package for you. 

Alternatively, you can consider deploying the onsite instance from a backup of the dev site, this way the package will be unlocked (of course if it's unlocked on dev site).

Or share with us copy of your current Database, so we'll unlock it on the copy and provide you with it.



Best regards,

Yuliya Gritsenko

Show all comments