Yes this is getting pretty frustrating among metrics and graphs alike for a couple years now, not to be able to set to K or M etc...

Not yet without coding, it is in the pipes for S1 2024 according to the roadmap.

Hello!

Unfortunately, there is no such option at the moment. We have created a corresponding request for the development team to reconsider this logic.

As for now, we cannot provide you with specific recommendations on your question at this time, as such a scenario has not been studied and we have no examples of such a realization.

Can you please provide some direct example of what you are trying to achieve since unfortunately it's not obvious to us what is performed on the page at the moment, what is the expected result and what is the actual result? Maybe some steps to reproduce it in the local application (like the following:

1) Add column A

2) Add attribute B

3) Connect B to A in the following manner

4) Go to the page where the column and the attribute were added

5) Do "this"

6) Expected result is C

7) Actual result is D

) .

Thank you!

Oleg Drobina,

Basically all I want is to be able to set the value of an attribute in code without triggering the "You have unsaved changes that will be lost. Continue?" message when you leave the page. Is this possible?

Harvey Adcock,

I tried to reproduce the issue, but changing the value of the virtual attributes (like attributes created to control the visibility of the field) by itself does not cause this dialog to appear. 

Please ensure that no other changes need to be saved on the page. Or provide us with additional information describing the exact steps to reproduce the issue.

Best regards,

Natalia

Natalia Kalynovska,

Sorry, I was probably not detailed enough in my abbreviated version - the changes are actually to an attribute that is based over a real column on the entity, so not a virtual attribute. Is there any way to modify such a field in code without triggering the dialog?

Hello Harvey,

To change the field without triggering the dialog, you should save it at once.

It could be implemented by adding the following code to the HandleViewModelAttributeChangeRequest:

…

if (request.attributeName === “[Name of the attribute]”) {

const saveResult = await this.handlerChain.handlerChain$.process({

           type: "crt.SaveRecordRequest",

           preventCardClose: true,

           $context: request.$context

    });

}

…

Please pay attention that too many saving requests may decrease performance.

Another way is to save the necessary changed values to a virtual attribute first, and then extract all of them (set attributes values) and initiate SaveRecordRequest while closing the page (in crt. ClosePageRequest). This approach has some disadvantages:

1. you need to manually adjust the visibility  of “SaveButton” and “CloseButton“ by adding the corresponding merge operations to “viewConfigDiff” of ListPage and FormPage modules (see example - https://community.creatio.com/questions/how-remove-closesave-button-custom-section);
2. data would be saved only on a close/back button click.

And again – you should provide some conditions in order not to store too many changes.

Additionally, starting from the 8.1.1 Creatio version, the dialog may be prevented by adding to handlers the overridden “crt.CanDiscardUnsavedDataRequest” handler:

{request: "crt.CanDiscardUnsavedDataRequest", handler: async (request, next) => {return true;}},

(see https://community.creatio.com/questions/possible-suppress-message-upon-canceling-freedom-ui-mini-page).

However, it still requires manually adjusting the button's visibility and providing proper data saving.

Best regards, 

Natalia

Thanks Natalia, it would be really useful to have the functionality for making silent changes from code that existed in Classic UI added back into Freedom UI - see this post for what was possible in Classic: https://community.creatio.com/questions/change-value-field-without-firing-changed-events

The utility can be in setting fields from code when a create record page loads based on more complicated conditions than you can define in business rules/by other means, but not causing the user additional clicks to cancel or think that they might lose work.

Possibly some usage of this guide might be able to fulfil the ability to discard such data, though it would probably be quite tedious to implement in this scenario: https://customerfx.com/article/suppressing-the-unsaved-data-prompt-when-canceling-a-creatio-freedom-ui-modal-dialog/

The error was coming from a script in which variables were not well declared

Hello,

Yes, indeed, in this case, it is necessary to redesign processes to be interpreted, not compiled.

https://academy.creatio.com/docs/8.x/no-code-customization/bpm_tools/pr…

hello!
I have the same errors during compilation, but in OpportunitySchema.Opportunity.cs file, recompilaiton didnt help

Dmitrii Balashov,

Please specify if you already tried to follow the instructions provided above to fix this issue:

"it is necessary to redesign processes to be interpreted, not compiled."

https://academy.creatio.com/docs/8.x/no-code-customization/bpm-tools/pr…

I've only just recently started working with Creatio, but as I understand it this relates to writing Script task correctly

But after deleting all my custom script tasks the problem is still present on after recompiling

I contacted support and it looks like this is an issue with Opportunity package in version 8.1.3, which should be resolved in 8.1.4

Dear Dmitrii Balashov,

These compilation errors are fixed for 8.1.4, but you can go to the workaround solution:

    1) Unlock the Opportunity package for the hotfix.
    2) Open the embedded process in the Opportunity object schema.
    3) Change three lines (8, 10, 11) in the OpportunitySaving method to use the full definition of System.Linq.Enumerable save process and compile the system.
    4) Lock the Opportunity package.





 

Best regards,

Andrii

Andrii Kurta,

Thank you!

Hi Harvey,

I've done this in several areas in our system using modal forms (actually called a Mini Page in the page types dialog you select from when creating a new page). Here's an example of a dialog allowing the case status to be set from a list (we don't use editable lists yet since there's no way to add validators yet to lists):

This is just a modal/mini form created using the form designer. The nice part about this is that it can be bound directly to the object (I have many that aren't bound as well, depending on the scenario).

You can open this specific page for a particular record using this method (also possible with an action in no code designer as well) https://customerfx.com/article/opening-a-record-for-edit-in-a-specific-…

Ryan

Ryan Farley,

Thanks for the reply Ryan, that seems like exactly what we're after! I had wondered about using a Mini Page for it but wasn't sure how that would be hooked in to work. How are you triggering the mini page to be displayed, I take it it's from code? Is it using something like the following when clicking a button or whatever the trigger is:

const handlerChain = sdk.HandlerChainService.instance;
 
await handlerChain.process({
	type: "crt.CreateRecordRequest",
	entityName: "CustomEntity",
	entityPageName: "CustomEntityMiniPage",
	$context: request.$context,
	defaultValues: [{
		attributeName: "Col1",
		value: "Val1"
	}]
});

Or are you able to get a Mini Page to appear without some entity it's based over? For our requirements, the data field to be modified would actually be on the entity of the Form Page the user was currently on, so it didn't seem like the crt.CreateRecordRequest would make sense, but the crt.OpenPageRequest always seems to open the Mini Page as though it were a full-sized page, and the crt.UpdateRecordRequest I hadn't tried yet as I didn't already have a Mini Page for the entity and thought it likely wouldn't work as the mini pages are generally used for adding data, not editing?

Thanks again.

There's so many uses of modal (mini) pages beyond just what mini pages were used for typically in classic ui. 

IMO It's one of the best additions to Freedom UI, the ability to create dialogs for specific purposes, bound to a record or not, that really enhances the user experience. This is a prompt for selecting parameters for a report.

Ryan

Harvey Adcock,

You would use an "crt.OpenPageRequest". I edited my original post to include a link to an article showing how to open it to edit a record. 

Ryan

Harvey Adcock,

In older versions the "crt.OpenPageRequest" did open the page in full screen, even if a modal page. But I think that was fixed in 8.0.10 and has been working for me (it does open as a modal)

Ryan

Perfect, thanks Ryan, really helpful!

Ryan Farley,

One more question, is there a way to pass information from the current page to the page being opened via the OpenPageRequest? Trying defaultValues, similar to what you would use when creating a new record from a page launched by code, doesn't seem to have any effect, and I can't see any other candidates for it.

Harvey Adcock,

I’m not 100% sure but I think you can only pass values for a new record (crt.CreateRecordRequest) only. 

Alternatively, you could write some values to a global or use the StorageUtilities module and then read from the form once opened. See StorageUtilities here: https://customerfx.com/article/persisting-data-between-pages-in-creatio…

Ryan

Harvey Adcock,

You can try something like this to pass defaultValues

request.$context.executeRequest({
	type: "crt.OpenPageRequest",
	$context: request.$context,
	schemaName: "UsrYourCustom_FormPage",
	modelInitConfigs: [
		{
			action: sdk.ModelInPageAction.Edit,
			recordId: yourRecordId
		},
		{
			defaultValues: [
				{
					attributeName: "someName",
					value: "someValue"
				}
			]
		}
	]
});

Alex Zaslavsky,

Does this passing of values work for passing a value into a Page Parameter? Or is there some way to do so? The value I want to pass to a new page (either through OpenPageRequest or CreateRecordRequest) is not on the entity, it's just a parameter on a page, but we need to set this value when opening the page.

Hi Francois,

Thank you for bringing this matter to our attention.

The developer has resolved this issue and published the new version of the application on the Creatio Marketplace.

Please install the latest version via the following link: Advanced list setup for Creatio

Hello...While fixing the previous bug...I believe another one came up.

When accessing a CASE (or any object), if you click on the ACCOUNT of the CASE and come back...for some reason the system doesn't know where it was and keeps displaying the Loading Icon with a brighter screen.

He're a short video to help you understand the problem :



vtq-media.com/Video-Library/BUG-display-when-returning-from-a-detail-page.mp4

Can you fix that ?

SEE CASE below opened to Support@creatio.com 

Case #SR-01273076: VTQ-CANADA - Bug display when returning from a detail page

Oleg Drobina  (Creatio Support)

2/29/2024 at 1:31 PM

Hello Francois,



Thank you for the video and the explanation!



After studying the behavior, we could reproduce it out-of-the-box after installing this Marketplace addon https://marketplace.creatio.com/app/advanced-list-setup-creatio. This addon directly provokes the behavior you've described.

 

Any updates on that issue ?

Hi Hassan!

We recommend checking the configuration of the start signal. If the page appears when you manually start the process, then it is likely that the start signal for record creating wasn't configured correctly.

Please check if the process starts, you can check it in the System designer -> Process log. If the process didn't start, check the start signal configuration and make sure that the record created match the conditions.

You can get more information about start signal for creating a record on Academy: https://academy.creatio.com/docs/8.x/no-code-customization/bpm_tools/pr…

If you have checked the settings and still need help, please contact our support team for further analysis.

Best regards,

Alina

Alina Yakovlieva,

Hi Anna,

The process does start and it is in process. When I go to Logs, I can see the process at the Mini page stage. From there I can inspect the mini page and complete the process by clicking on the button.

Hassan Tariq,

In this case, please check the setting of the "Who performs the task?", maybe the page shows to another user. 

Also, you can check more information about the Pre-configured page set up on Academy: https://academy.creatio.com/docs/8.x/no-code-customization/bpm_tools/pr…

On the signal, make sure that "Run following elements in the background" is not checked.

Ryan

Bump

Hello!

Please note that this can be realized through 2 options:

- via business processes

- via development 



Unfortunately, we cannot provide you with specific recommendations on your question at this time, as such a scenario has not been studied and we have no examples of such a realization.

Bump

Hello,

I suggest you check if the filtering conditions are being met.

1. Try building the same filter in the Orders object and check if such records exist, and if there are more than 2 records. (We noticed that you have Finish Date < Start Date; we are not familiar with the logic of your object, but we recommend verifying the correctness of this filter.) Reference: How to work with data

2. Enable process tracing to check the values returned by the process elements: Reference: Trace process

Regarding the second issue, you need to add more filters so that the records found in the Read Data element meet the required condition.

If you encounter further difficulties in configuring the process, please contact our support team at support@creatio.com.



Best regards,

Pavlo!

Hello,



Unfortunately, at the moment it is impossible to customize colors in charts. However, a task has already been registered in our R&D team to add the option to customize colors in charts, in future releases. In case you would like to check  what stage this task is at, I am sending you the task number: PR-6359.