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 

Hi,



I am seeing lots of advancements in Creatio nocode but also in the evolution of clio & clio explorer with visual studio code . There are still cases where either some small things need to be developped and Creatio is still a sensitive tool that needs to be debugged also by no code creators.



Anybody else would love to have more up-to-date official e-learning videos, guided learning, corporate training on how to best develop on Creatio using best practices, how to make the best use of clio & clio explorer ?



Kind regards,



Damien

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.