Clio version 8.0.1.4 allows redirecting logs of any command to a file. To do it, use the following form

clio <COMMAMD> <COMMAND PARAMETERS> --log d:\log\my-log-file.txt

It creates an easy way to organize data for auditing the actions and changes and their parameters

Clio version 8.0.1.3 provides the ability to show and store the last compilation log from Creatio environment

clio last-compiltaion-log -e <ENV>

To store it locally, use the --log option

clio last-compilation-log -e <ENV> --log c:\log.txt

To display RAW output from the server, use the following

clio last-compilation-log -e <ENV> --raw

WerdienJihed, thanks for your idea and contribution to the Clio project 👍

P.S: In the next releases, we will extend the list of commands that will support store log to file for improving UX work with ci/cd pipelines

It would be good to add some extra options and tools to Business Processes to better control their behaviour in certain circumstances, for example when they have ended up hanging. These would make using Business Processes a lot more robust to issues without every implementation having to build their own framework around them.

The controls I would like to see added are the following, but I'm sure other developers could provide more that would be useful:

1. Maximum runtime - process instances would get set to "Error" state after this period automatically
2. Retry method - allow BPs to be configured to be retryable after hanging and getting set to "Error" state automatically or failing with an error. It should also be possible to specify maximum retries, and of course by default BPs should not be set to be retryable to avoid any issues with non-idempotent BPs/BPs which it only makes sense to run synchronously when a user initiates the action, for example
3. The ability for an admin to restart a specific BP instance - for example if they have identified one which has hung. This should be added alongside the "Cancel execution" ability we have currently in the Process log
4. Failure alerting mechanism - some built in failure alerting mechanism, even just simply emailing a system setting-defined email list, so that resolving these issues can be more proactive rather than reactive to user feedback. Being configurable which BPs send alerts and which shouldn't would be useful, as well as alerting thresholds to prevent too much spam would be nice to have

I would welcome any additions people have to this list, and getting any of these would improve the resilience of using business processes greatly for customers.

Clio version 8.0.1.2 provides support for a long time compiling all configuration during CI/CD pipelines via command

clio compile-configuration --all -e MyEnv

For cases when you want to run additional compilation of your configuration after installing a package, you can use the following command

clio install MyPackage.zip --force-compilation -e MyEnv

P.S This approach can be useful for ensuring resilient CI\CD pipelines 

I was very happy to learn about all possibilities of integrations using Creatio webhooks

and very disappointed when start to implement some use cases at customers 

to learn that Creatio is not using the webhook standard event structure

https://developers.oncehub.com/reference/the-event-object

to process the webhooks 

This has the implication that some major platforms that use the webhooks standards will not integrate easily with Creatio, for example:

https://www.wix.com/

https://paperform.co/

It is possible to develop custom logic but in this case we would like more standardization and less customization

Anyone has similar issues? And do you think it is a good idea?

Luis