Clio version 6.1.0.14 has been released. What`s new:

Added support for custom naming your composable application in Hubs. Now, you can specify aliases that Clio will use to find application releases in the file system. Example:

Environment:
  url: https://preprod.creatio.com
  authappurl: https://preprod.creatio.com/0/ServiceModel/AuthService.svc/Login
 
apps:
  - name: CrtCustomer360
    version: "1.5.2"
    apphub: MyAppHub
    aliases: ["Customer360"]
 
 
app_hubs:
  - name: MyAppHub
    path: "//MyAppHub/Apps"

Fix behavior for environment settings when -e is provided.

clio apply-manifest my-prod-manifest.yaml -e prod 

P.S: Next releases will add a feature for storing information about the list of packages from environment to manifest and ability transfer configuration between two Creatio instances

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 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.

Clio release version 6.0.2.51 provides new features for setting versions to Composable applications in CI\CD pipelines. 

Feature compatible with clio workspace code structure:

clio set-app-version [WORKSPACE_FOLDER_NAME] -v 1.0.1

Also, this command can be used for the single package with application description in cases when not used clio workspace structure

clio set-app-version -f [PACKAGE_FOLDER_PATH] -v 1.0.2

P.S: This feature and publish-app command fully cover all cases for versioning artifacts of composable applications. 

Clio release version 6.0.2.49 and Clio explorer version 2.0.59 provide functionality to get info about the Creatio system. It contains the product name, core version, type of database, runtime platform, and customer ID. It can be helpful for identifying installation or updating packages 

Also, it is available in command line mode

clio get-info -e ENVIRONMENT_NAME

Required update Clio API on the environment to version 2.0.0.28

The new release of clio v.6.0.2.43 and clio explorer version 2.0.58 provides a new exciting feature to deploy the latest version of Creatio available in the storage.

You need to create local or network storage  with following structure:

And add path to storage in clio config file:

It can be local or network path.

You can open the settings file via clio explorer ui or the command

clio cfg open

P.S: Deploy latest releases from storage also available via console command, detailed information about other option available at the following link

clio deploy-creatio --product studio --db pg --platform net6

Clio version 6.0.2.41 and Clio Explorer version 2.0.56 provide functionality for easy organizing and distribution of your composable applications. Now, you can download applications to the local file system from your registered environments.

This command creates a workspace for selected applications, which can later be deployed to any of your Creatio environments.

Clio Explorer provides convenient control for all workspaces stored in one directory.

Therefore, you can:

- link the local file system to git or another version control system

- map workspace to Creatio development instance

- deploy on-demand new versions to QA or Production environments

- easily combine all your applications on new environments in the cloud or local