Время создания
Filters
Idea
Discussion

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

0 comments
Show all comments

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 

 

0 comments
Show all comments

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

4 comments

Hello,



Perhaps these links will be useful to you:

https://www.youtube.com/watch?v=Qy7BsGrxbB0

https://github.com/Advance-Technologies-Foundation/clio



Best regards,

Malika

Hi Malika,

Thank you for the links, it's a start. But a more structured & up-to-date advanced training/documentation/recommendation are needed.



The video is a good example, but it relates to Creatio from 3 years ago. Since then Creatio has evolved a lot (with different backend behavior), Clio also and Clio explorer also.



Official structured training/tutorial tracks from Creatio would be more than welcome and necessary, rather than having to dig through academy / community / github in an unstructured way.



Cheers,

Damien



P.S. : Advance-Technologies-Foundation: is it Creatio or 3rd party ?

Damien Collot,

 

Excellent idea indeed!

 

I have just discussed internally with my colleagues that while a lot of information is available on the academy, the community, and the GitHub readme/documentation of clio, we miss a training that clearly points out how this all works together and was meant to be used.

Ultimately, the software vendor should provide best practices and guidelines!

 

Cheers,

Robert

Damien Collot,

Thank you for providing this great suggestion. We have already forwarded this idea to the responsible team for Clio, for consideration and creation of additional newer Clio training videos and tutorials.

 

Show all comments

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

0 comments
Show all comments
Idea
Discussion

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.

0 comments
Show all comments