New Clio release version 6.1.0.22 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.

New Clio release version 6.1.0.21 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.

Clio release version 6.1.0.20 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

Clio version 6.1.0.19 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

Clio version 6.1.0.13 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

Clio release 6.1.0.12 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> 

Clio release 6.1.0.8 extends the ability to configuare your Creatio environments in a GitOps manner. Now, you can configure the URL address of WebServices in the manifest file.

environment:
  url: https://production.creatio.com
 
webservices:
  - name: GoogleAnalytics
    url: "https://google.ca"
  - name: FaceBookAPI
    url: "https://facebook.com/api"
 
app:
# list of applications
 
app-hubs:
# list of application stores
 
settings:
# list of sys-settings and value
 
features:
# list of features

Also, we extend the Clio commands and add abilities to see all web services, and their addresses

clio get-webservice-url -e <environment-name>

Improvements: From release 6.1.0.8, you can set the working directory for Clio via the Environment variable CLIO_WORKING_DIRECTORY. 

<your workplace>/tasks/set-clio-working-directory "c:\Temp\ClioWorkDir"

It helps avoid problems with CI\CD pipelines when you can't access default temp directories.

COMING SOON: In the next release, a "save-configuration-to-manifest" command will be released

Clio version 6.1.0.4 allows managing system settings on the Creatio instances via a manifest file. Text, Boolean, Integer, Date Time, and Lookup value (by Guid or Display value) are supported

Add section setting to the manifest file.

environment:
  url: ************************
  authappurl: *****************
 
settings:
  - code: "SETTINGS CODE 1"
    value: false
  - code: "SETTINGS CODE 2"
    value: 10
  - code: "SETTINGS CODE 2"
    value: "My_Text"
 
features:
 # list of installed apps
 
apps:
  # list of installed apps
 
app_hubs:
 # connected app hubs

To apply manifest to your environment, use the following command.

clio apply-manifest C:\my-configuration.yam -l user-p pwd

Clio explorer version 2.0.61 provides two experimental features for discovering and comparing feature states between two environments.

and

P.S. Managing  WebServiveUrls via manifest and Comparing two configurations that are coming soon. Clio command set-settings also was improved, and  you can avoid setup Type of sys-settings in an update scenario and set the Lookup value via display value 

Clio version 6.1.0.3 allows managing features on the Creatio instances via a manifest file.

Add section features to the manifest file

environment:
  url: ************************
  authappurl: *****************
 
features:
  - code: "FEATURE CODE 1"
    value: false
    users_values:
      "User1": true
      "Role 1": true
      "User2": false
  - code: "FEATURE CODE 2"
    value: false
 
apps:
  # list of installed apps
 
app_hubs:
 # connected app hubs

Allowed to set a default value for all users or specify it for each user/role,

To apply manifest to your environment, use the following command.

clio apply-manifest C:\my-configuration.yam -l user-p pwd

P.S Managing SysSettings and WebServiveUrls via manifest coming soon

Hello everyone! We are glad to share with you that Clio released version 6.1.0.1, which started to control the change management process for Creatio users.

Now you can store the configuration for Creatio environment in the yaml file

environment:
  url: https://myapp.creatio.com
 
apps:
  - name: CrtCustomer360
    version: "1.0.1"
    apphub: MyAppHub
  - name: CrtCaseManagment
    version: "1.0.2"
    apphub: MyAppHub
  - name: MrktAppollo
    version: "1.0.2"
 
app_hubs:
  - name: MyAppHub
    path: "//file.shareserver/MyAppHub"

This configuration file describes the desired states for the Creatio environment. Clio will compare the current and desired states and apply necessary changes (install/update applications from local AppHub, remove applications). You can register your several AppHubs in one configuration file.

To apply changes to the environment, use the following command

clio apply-manifest C:\my-configuration.yam -l user-p pwd

This approach implements best practices for managing and change logging.

In next releases will be added support for configuration:

  - sestem settings

  - feature states

  - web service base urls

  - packages

P.S:  Clio provides commands for versioning and publishing your composable applications to AppHub.