IMPORTANT!! Separate Packages for Different Clients in single instance
Hi,
I'm working on Creatio Cloud Instance (Freedom UI) where I need to create separate packages for multiple clients in this single instance.
Challenges:
- changes made in one entity i.e. Contact for client 'a' should not reflect on UI or anywhere when employee of Client 'b' log into system.
- Load the modification based on client.
Platform: Creatio:Energy (freedom UI)
Like
I would be interested to know if it is possible to install a package, uninstall it, and upload a second package. The application was creating packages of different demos, to be installed as and when needed.
If I remember correctly the tables for custom sections of uninstalled packages are not deleted when the package is uninstalled (presumably unless coded).
Hello,
We would like to note that the described development approach — using a shared environment for multiple clients and packages — is not optimal and may lead to additional difficulties such as configuration conflicts, unexpected errors, or even non-functional logic.
The recommended and most stable development practice is to maintain a dedicated development environment for each client.
In scenarios where multiple developers are involved, it is highly recommended to use version control tools such as GitHub, GitLab, or SVN. This approach ensures better collaboration, traceability, and stability during package development and delivery.
As for the functionality you described — unfortunately, it is not available in the out-of-the-box version of Creatio. However, we’ve registered a request for our development team to consider adding it in future releases.
Best regards,
Antonii.
Gareth Osler,
It is possible to uninstall a package from the system.
However, this process should be approached with caution. Before proceeding, it is essential to ensure that all references to the package have been completely removed, that the package is not being used as a dependency in any other package, and that its removal will not negatively affect the configuration or overall system stability.
We strongly recommend performing such actions in a test or non-production environment first, to avoid any unintended consequences.
Additionally, please note that if the package creates any custom database tables, they will not be removed automatically during the package uninstallation. In such cases, manual cleanup will be required — either by writing SQL scripts or implementing custom logic — to fully remove those tables from the database.
Best regards,
Antonii.