Hello,

Could you please describe your business goal in more details, with screenshots if possible?

Hello Andres!

Unfortunately, there are no specific event handlers for the fields.

But you can create your own handler for the blur event using the "handlers" schema section of the Freedom UI page or a remote module.

This request should be bound to the “blurred” property of the input field in the “viewConfigDiff”:

Also, the list of the generic query handlers is available here: https://academy.creatio.com/docs/8.x/dev/development-on-creatio-platform/front-end-development/freedom-ui/client-schema-freedomui/references/handlers

Example of the invoking the query handler - https://academy.creatio.com/docs/8.x/dev/development-on-creatio-platform/platform-customization/freedom-ui/page-customization-basics/examples/change-where-the-query-handler-is-invoked

Best regards,

Natalia

Thanks! Actually the "blurred" property is what I was looking for.

Is there any documentation in which I can see all the properties that can be bound for a field, in the same way we can bind blurred?



Thanks!

 

Hello Nur!

There is a possibility to customize the search by any column of the Product object with a text value.

You can implement that in the following way:

1. Open Configurations.
2. Create a replacing view model for “ProductSelectionSchema”(Product selection schema page).
3. Add the “getQuickSearchFilterConfig” method, which sets the filter columns, and specify the names of all the text columns you want to search by.
4. Change the value of “SearchStringPlaceHolder” in the localizable strings to the corresponding one (optional). This value would be displayed in the search box as a placeholder.
5. Save the changes and reload the product selection page (press “F5”).

Best regards,

Natalia

Hello Ahmad,

Could you please elaborate on your business task?

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.

Hello,

We have already addressed a similar issue, and you can find the solution at the following link: https://community.creatio.com/questions/client-esq-and-validation-mecha…

+1 for this functionality, to be able to set it up for all or some groupe of users

Definitely agree this needs to be possible if it isn't already!

Hello,

Unfortunately, there is no possibility to disable the "All Apps" workplace at the moment. However, we have already registered a problem regarding this and forwarded it to our R&D team for review so it could be fixed in one of the future versions of the application.

Mira Dmitruk,

This is also a potential security issue. Users are able to see sections that are not supposed to be visible to them. This means that with every section we need to ensure that record permissions are available and implemented. Also, I notice the lack of AuthGuard. If a user appends a section page name to the URL, they are redirected to that section as well.



Can we have a workaround (even custom code) to remove/ hide All Apps and other irrelevant workplaces based on user role?

Mira Dmitruk,

Any news on this?

It is very important and 

Like Shivani was asking, is it possible to limit acces to users, even if it is via custom code?

This is really important

Rgds,

Luis

Luis Tinoco Azevedo,

For version 8.1.2 there is operation permission to hide All apps workplace

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/

Hello,

At the moment, there is no possibiliy to set up a mini-page just for viewing records in the system. Currently you can create a mini-page for creating a new record and set up a mini-page for editing an exisiting record with the help of a business process.

We also do not plan to support mini pages for 7x (Classic UI) with the Shell enabled, as this functionality is already implemented and is available in Freedom UI (starting from version 8.0.8).

We recommend you to configure the needed section in Freedom UI and to set up the required mini page for creating a record there.

You can learn more about it in this Academy article.