New Clio release version extends clone-env operation for simple copy your packages from one environment to another. It can be used when you want to try your code on the new version of Creatio platform or check compatibility with another products.


To clone all packages from maintainer(s), run the following command.


clio clone-env --maintainer ATF --source SOURCE_ENV --target TARGET_ENV


If you want to try a new release of Creatio, use the exclude-maintainer argument to exclude all OOTB Creatio packages.


clio clone-env --exclude-maintainer Creatio,Terrasoft --source SOURCE_ENV --target TARGET_ENV


P.S In the future, we plan to release ability transfer features and settings between environments and transfer data sets.

Show all comments

New Clio release version allows clone packages from one Creatio environment to another. 


clio clone-env --source Dev --target QA --working-directory [OPTIONAL PATH TO STORE]


The command creates a manifest from the source and target, calculates the difference between them, downloads the changed package from the source environment to the working directory (optional parameter), and installs it in the source environment.


Hi, it downloads and installs both from and to source environment or one of those two should be a target ?

Do you have a video to show how it works ?

Thanks :)

This is excellent. As Damien mentioned, a video of this and other clio functionality, or even some additional details of the commands, would be fantastic.

Clio has grown to have so much functionality and commands that it's sometimes hard to fully understand what many actually do. A more complete description of what they do specifically, such as this command does X, Y, then Z etc, would be very helpful (not referring to "clone-env" specifically, but just in general). I avoid using some of the commands since I don't fully understand the specifics of what they are actually doing. 

I know this is open source, so I don't want to lump in any additional work, but even just a more complete or detailed description of the commands on github would be helpful. I'd be happy to contribute, even with creating documentation and videos, but that's difficult when many commands aren't completely clear and understanding the specifics require digging through the source and often cliogate as well, which adds a lot of time and sometimes guessing. 

Show all comments

Git] GitFlow, usar ou não usar? – Código Maromba

Clio release version provides the ability to customization your app-hubs with a branch-oriented strategy. Now you can define the following structure


To define a branch use the following arguments


clio publish-app --app-name Application_1 --branch master --app-version 1.0.4 --app-hub ./builds --repo-path .


Also, support branching was added to the apply-manifest command and you can specify the branch name in the yaml file\



NOTICE: If you use a naming convention requires a zip file name to be different than app code, then use aliases in manifest file


Show all comments

Clio version provides new functions to find differences in system settings, features, and packages across two Creatio instances


clio show-diff --source ENV1 --target ENV2


to save the result to a file specify the file option as follows


clio show-diff --source ENV1 --target ENV2 --file "C:\manifests\diff-env1-env2.yaml"


P/S: This command finds all data from source source which not presented or has different values on the target environment


Great Idea!

Can it also find differences in Features?

Vladimir Sokolov,

Features are already part of the diff

Show all comments

Clio release version allows you to save package states from your Creatio environment to the manifest file. You can use the following command to save settings to a file. 

clio save-manifest "C:\GitOps\production-manifest.yaml" -e production


Clio stores packages' Names and hash, which are based on ModifiedOn, Checksum, and Names of relative Schemas. For example

Also in the manifest file, Clio store feature states and addresses 

And web services addresses

If the manifest file does not exist, this command will create it. if the file already exists, Clio rewrites it. This behavior was created to organize the flow to store and monitor changes using Git.



Show all comments

Clio version was released. Now, you can add packages to the workspace with auto generate composable application descriptors.


// Init clio workspace
clio createw
// Add package to workspace
clio add-package MyApp -a True


If you have one application in the workspace, new packages will automatically be included in it.


// Init clio workspace
clio createw
// Add package and app metadata to the workspace
clio add-package MyApp -a True
// Add a package to the workspace and include it in MyApp
clio add-package MyPackage


This command can be used to add several applications to one workspace.


// Init clio workspace
clio createw
// Add first app to workspace
clio add-package MyApp1 -a True
// Add the second app to the workspace
clio add-package MyApp2 -a True


P.S: Error of work with temp directories in multiple Clio instances at one time was fixed

Show all comments

Clio release provides a command to create a state manifest for the Creatio instance and store the configuration of web services and feature states.


clio save-state "D:\manifest\myinstance-creatio-manifest.yaml" -e MyInstance


Storing this file in Git can be used to control instance changes. In future releases, the manifest file will store sys-settings values, applications, and packages, and it will also clone environment settings to clean Creatio instances.


P.S: Also the ability to work with HotFix mode was added to Clio commands. To enable/disable it use the following command


# To enable hot-fix mode for a package  
clio pkg-hotfix <PACKAGE_NAME> true -e <ENVIRONMENT_NAME> 
# To disable hot-fix mode for a package 
clio pkg-hotfix <PACKAGE_NAME> false -e <ENVIRONMENT_NAME> 


Show all comments

Hello Creatio Community,

I'm asking if there is a way to connect a Hosted Cloud Environment to Clio Explorer, and develop components from visual code and deploy them to the Cloud Environment?


Like 0


Show all comments