Clio release 6.0.2.32 provides features to facilitate application management.

Get list of installed applications

clio get-app-list -e ENV_NAME # or clio apps -e ENV_NAME

We used ATF.Repository and Remote Data provider in Clio for easy way for data integration between Creatio and 3rd party systems.

Download application from environment

clio download-app APP_NAME|APP_CODE -e ENVIRONMENT_NAME --FilePath FILE_PATH.ZIP

Deploy application from one environment to another without ALM portal connectivity

clio deploy-app APP_NAME|APP_CODE -e SOURCE_ENV -d DESTINATION_ENV

P/S: from version 2.0.53 clio explorer support UI command for set default environment

0 comments
Show all comments

Clio explorer version 2.0.52+ provides editing feature for package file content 

*update clio api required

clio install-gate -e ENVIRONMENT_NAME

Also in this release clio 6.0.2.25+  and clio explorer 2.0.52+ provide functionality of compiling a package

clio compile-package MyPackage -e MyEnvironment

Also, you can create clio workspace in a folder with empty git repository

git clone https://git.com/repo
clio createw

 

1 comments

Good job! Love this feature

Show all comments

New clio release 6.0.2.16 provide new feature for exploring file content on remote server.

clio files --package CrtBase
 
descriptor.json
src\css\driver.min.css
src\js\bootstrap.js
src\js\driver.min.js
 
clio files --package CrtBase --file descriptor.json
 
{
        "bootstraps": [
                "src/js/bootstrap.js"
        ]
}

P.S: Exploring features coming soon to clio explorer with edit mode

2 comments

This is fantastic. I assume this will eventually be available to view package file contents in Clio explorer as well?

Ryan

Ryan Farley,

Yes, we plan to do it in the near future and are already working on it.

Show all comments
Question

Hello Team,

I wanted to change the name of an existing package. What is considered the most efficient way to perform this action?

Like 0

Like

1 comments

That's never supposed to happen. You need to have a firm idea of a package's purpose when you create it.

I guess you can work around it and use some SQL script. But I would just keep the original name if I were you. Especially if you use SVN Version control on the package

Show all comments