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

Hi, 

Anybody knows how to alter the view of the timeline component in Freedom UI  - Creatio 8.3.0 ?

Example : Show attachments by default (rather than having to click on the arrow each time)
Removing the email title: Redundant in ticketing cases ...
Increase amount of text previewed

Etc

Cheers !

Damien

Like 0

Like

0 comments
Show all comments
Discussion
Business Process
Read Data
modify data

Some filters in BP steps such as the Read, Modify and Delete Data steps do not currently allow parameterisation of the filters, which can be a real constraint on development, often requiring workarounds or using a Script Task instead. It would be very useful to add in this functionality, similar to how most other filters can take the value from a parameter.

One example is in the Date macro filters for Previous X days, Following X days, Year X, Every year within X next days and so on. These all require a hard-coded number to be entered with no option to select a parameter/previous step's output for these values:

Often this reference data is stored somewhere and may want to change without having clients doing development, but at the moment this is not possible. Please can this feature be added to bring these types of filter in line with other filters on the same steps which do allow for passing in a parameter?

0 comments
Show all comments

Hi! Today I released a framework for automated testing of the Creatio platform.

The idea behind it is a simple language that a developer and a business analyst can both read. Because when you test Creatio, a large share of the work is the same kind of checking over and over: is the field on the page, is it filled in, is it required or read-only, do the configured rules behave the way they were set up.
So instead of page objects and selectors, a test looks like the picture below: a check that a field exists on the page, and that it takes a value.
You are probably looking at that GUID and the field code and thinking someone had to dig those out by hand. They did not. The framework opens the page itself, walks through its tabs, and writes down every field, button and tab it finds, with its caption and its type. You point it at a page and it describes itself. What you then write and edit are the checks.
Tests live in files with an .act extension. The framework picks up every test in the folder and runs them one by one, so a suite grows by adding a file, not by wiring anything up.
The part I am most pleased with is that a broken test costs you three seconds, not three minutes. Before a browser opens, the whole file is checked: unknown command, a field that is not on that page, an operator that makes no sense for a text field. You get every mistake at once, with line numbers, and you do not even need a running Creatio to find them. That makes it usable as a pre-commit check.
Which gives two things at once. A business analyst can read a test and change what it asserts without touching C#. And the same tests drop into a CI/CD pipeline, because the runner is a command-line tool that returns exit codes and writes reports.
Today it covers every field type on a Freedom UI page, plus buttons, tabs and the stage progress bar. It has been run against a live Creatio 8.3 instance, not only against mocks.
Next on the list:
- Grid detail support, so detail lists become testable
- Creating records automatically from a condition
- Richer reporting
- Making CI/CD integration simpler still
Open source under the MIT licence, built on .NET 8 and Playwright. Link in the comments.
If you work with Creatio and there is something you would want to test that this cannot reach yet, tell me. That is the most useful thing I can hear right now.

github:
https://github.com/artemivzhenko/automatic-creatio-tests

#Creatio #TestAutomation #FreedomUI #OpenSource #dotnet #QA #Playwright

Like 3

Like

Share

0 comments
Show all comments

I am seeing this error pop up in several places in 10x instances.  These are both demo instances and customer instances.  I have seen them inside of home pages, when trying to render charts, and in things like lead pages.  

Anyone else come across this?  Is this small bug with patch coming?  At first I thought was maybe something in a chart configuration it didnt like, but now seeing it in lead pages tells me something more in back end.

Like 0

Like

1 comments

I've not noticed that, at least not yet - although not really paid attention to any dashboards/charts/etc. If you look at the network requests in dev tools, do you see any requests in red (likely a SelectQuery) that might shed some light on what is causing the error?

Show all comments
Sales_Creatio_enterprise_edition
8.0

We have three instances of Creatio, dev / pre / prod. The dev and pre environments are newly made from a copy of production. 

We had one Lead:Cases process in all environments that was active, but when we updated our production environment, it created a new version. In our production environment, we now have version 0 and 1, where 1 is the same as in dev and pre.

What we are wondering, is why there was made a new version in production. When we moved from dev to pre, there was only one in both environments. This forces us to change case on all existing leads, which makes the reset to the first stage. We do not want to do this, because this will give us double lead stages and mess up reporting. 

We also do not want to have all existing leads finish the old version of the case. 

Has this issue occured for anyone else, and is there some other options to align the two versions in production? 

 

 

Like 0

Like

0 comments
Show all comments