Idea
Discussion

 

Clio will be updated to. NET8 starting from 8.0.1.1. The Creatio platform will be updated to .NET 8 starting from 8.2.1, which will be released in December of this year.

 

In the 8.0.1.1 version, a flag --ts was added to show timestamps in the log messages:

clio ping env --ts

 

Thanks Federico Buffa for submitting a pull request on the Clio GitHub repository!

0 comments
Show all comments

Hi team,

We want to add a button in communication panel through which cases section should open in the side pane ( opens on clicking of buttons in communication panel) through with cases can be created quickly without closing the current section page opened in the tab.

 

We have created button in communication panel but we are finding references to open the page in side pane.

if anyone of you can help on this ,I will really appreciate it.

 

Thanks in Advance

Like 0

Like

7 comments
Best reply

Kashish Shakeel,

For Classic, it's doable, but definitely not as easy (there is not a no code approach for classic shell, only for Freedom shell). If you're using classic shell, best approach is to look at the code for the other panels and duplicate for your needs.

Ryan 

Hello Kashish,

Thank you for your question. First of all, are you using the Shell of Freedom UI in the section from which you are opening the side panel? Secondly, while I believe that creating a case from the side panel is possible, I'm not sure if your logic can be fully implemented. Also, would it be easier to create the case using a modal page in your section?

I'll be happy to assist you and will be waiting for your response.

The Academy refers to those as sidebars and they can be created with no code (more or less) in Creatio 8.1.3 and higher. See https://academy.creatio.com/docs/8.x/no-code-customization/customization-tools/ui-and-business-logic-customization/set-up-a-sidebar

Ryan

Yevhenii Grytsiuk,

 

Thankyou you your reply currently we are using the classic UI,we are not using Shell of Freedom UI in the section.

 

The requirement is to create  a quick access option for creating cases without needing to jump on another page and also in a way that  the information from the current open page can be visible properly as it is going to help in case creation.
 

The best that we thought of was using side panel for case creation while the user can see all information in the current open page.Is there any way you can help me achieve that?

 

 

Yevhenii Grytsiuk,

 

Ryan Farley,

 

Thank you for your reply, we are looking for some information on the same topic in the classic UI.

 

Is there any reference for classic UI? f yes can you please share that information with me?

Kashish Shakeel,

Answering question for Ryan - I am almost certain that, unfortunately not. That's why I was asking if you are using shell or freedom ui. However it is still possible to create a modal/minipage regardless.

Kashish Shakeel,

For Classic, it's doable, but definitely not as easy (there is not a no code approach for classic shell, only for Freedom shell). If you're using classic shell, best approach is to look at the code for the other panels and duplicate for your needs.

Ryan 

Ryan Farley,

 

Hi,

thankyou for your reply we will try to implement customized code.

 

Show all comments

Material Symbols & Icons - Google Fonts

 

Hi!

 

We are excited to announce a new feature in Clio release 6.1.0.37: the Set application icon command! This new command allows you to easily set or update the application icon for your Creatio projects directly from the command line, ensuring your application meets the Creatio Marketplace requirement.

 

Example of using:

 

clio set-app-icon -<APP_NAME> -<ICON_PATH> -<PACKAGE_FOLDER_PATH>

 

Replace <APP_NAME> with the name or code of your application, <ICON_PATH> with the actual path to your SVG icon file, and <PACKAGE_FOLDER_PATH> with the path to the folder containing your application packages.

 

P.S: Set application icon command is compatible with all Creatio versions 8.0+

 

Happy coding!

0 comments
Show all comments

I am currently developing an application where I need to add a "Sync Data" button to both the Accounts and Contacts sections. This button will trigger a Business Process that needs to work dynamically based on the context from which it is called.
 

The key requirement is to use a single, common Business Process for both Accounts and Contacts. In this process, I need to determine whether the button was clicked from the context of Accounts or Contacts, so the appropriate actions can be taken accordingly.
 

I understand that creating separate Business Processes for Accounts and Contacts could achieve this, but my goal is to have a unified process or function that can be reused across multiple entities.
 

I would greatly appreciate any guidance or suggestions on how to implement this in Creatio.

Thank you in advance for your assistance!

Like 0

Like

1 comments
Best reply

Create a boolean parameter "IsContact"(it's just an example, you could create any parameter ) and pass true if the button is clicked on contact page and false if it's clicked in any other place 

Create a boolean parameter "IsContact"(it's just an example, you could create any parameter ) and pass true if the button is clicked on contact page and false if it's clicked in any other place 

Show all comments

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.

0 comments
Show all comments

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.

2 comments

Hi, it downloads and installs both from and to source environment or one of those two should be a target ?

Do you have a video to show how it works ?

Thanks :)

This is excellent. As Damien mentioned, a video of this and other clio functionality, or even some additional details of the commands, would be fantastic.

Clio has grown to have so much functionality and commands that it's sometimes hard to fully understand what many actually do. A more complete description of what they do specifically, such as this command does X, Y, then Z etc, would be very helpful (not referring to "clone-env" specifically, but just in general). I avoid using some of the commands since I don't fully understand the specifics of what they are actually doing. 

I know this is open source, so I don't want to lump in any additional work, but even just a more complete or detailed description of the commands on github would be helpful. I'd be happy to contribute, even with creating documentation and videos, but that's difficult when many commands aren't completely clear and understanding the specifics require digging through the source and often cliogate as well, which adds a lot of time and sometimes guessing. 

Show all comments

Git] GitFlow, usar ou não usar? – Código Maromba

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

 

0 comments
Show all comments

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

3 comments

Great Idea!

Can it also find differences in Features?

Vladimir Sokolov,

Features are already part of the diff

Show all comments

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

0 comments
Show all comments

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> 

 

0 comments
Show all comments