Hello, 

You can see how to do this for a Freedom UI page here 

https://customerfx.com/article/receiving-server-side-messages-in-a-crea…

That article shows how to receive the message, the article links to another article that shows how to send the message from the process. As for refreshing the page once you get the message, see https://customerfx.com/article/refreshing-reloading-page-or-list-data-o…

Also, just to point out, this sort of thing won't be necessary in 8.0.7, which is due out soon. There will be a built in way where you can set an option in the object for it to auto refresh called "Enable live data update". Checking this will handle the sending of the message and refreshing any UI bound to the object automatically when the object is modified in processes etc.

Ryan

Hello,

Could you please clarify what you mean by "Model class"? Also, could you kindly provide us with an example of how you read a record?

Thank you.

For Orkhan: The model class is the new method for working with data objects in Freedom UI pages, available in the DevKit SDK, replacing EntitySchemaQuery, InsertQuery, UpdateQuery, and DeleteQuery. An example of reading a record using the Model class is here https://customerfx.com/article/retrieving-a-record-via-the-model-class-…

However there are issues currently when reading a collection of records since the filters are not properly set. I have an open case with support on this topic (case #SR-01182879). When filters are used with the model load it sets the filters incorrectly and causes a server error. I have an article ready to publish on this topic as soon as the issue is resolved but I’ve not heard anything from support yet. 

The code to load a collection of records using the model class would look something like this (however, as I mentioned, the filter gets applied incorrectly and the query fails with a server error 500 due to the invalid filter)

const accountModel = await sdk.Model.create("Account");
 
const filters = new sdk.FilterGroup();
await filters.addSchemaColumnFilterWithParameter(sdk.ComparisonType.Equal, "Type.Name", "Partner");
 
const partners = await accountModel.load({
    attributes: ["Id", "Name", "Type"],
    parameters: [{
        type: sdk.ModelParameterType.Filter,
        value: filters
    }]
});

Ryan

Also, I do have a workaround for the issue with querying a collection of records using the Model class. The issue that occurs is with how the filters are serialized to JSON for the request. However, if you shallow copy the filters first, then replace the filter.items, it will work. Here is a sample with this workaround (this does work successfully):

const accountModel = await sdk.Model.create("Account");
 
// create the filters
const filters = new sdk.FilterGroup();
await filters.addSchemaColumnFilterWithParameter(sdk.ComparisonType.Equal, "Type.Name", "Partner");
 
// shallow copy the filters to a new object and replace the items
const newFilters = Object.assign({}, filters);
newFilters.items = filters.items;
 
const accounts = await accountModel.load({
    attributes: ["Id", "Name", "Type"],
    parameters: [{
        type: sdk.ModelParameterType.Filter,
        value: newFilters
    }]
});

Hopefully I'll hear back on why this only works with this workaround and this will no longer be necessary.

Ryan

I am not official support, however I did bookmark this post Filtering a lookup in Freedom UI - Help needed | Community Creatio

Hello Federico, 

Please let us know if you have tried to implement the functionality as described in our Academy?
If there were any errors or difficulties, please let us know which exactly?
https://academy.creatio.com/docs/developer/interface_elements/record_pa…

Best regards,
Anastasiia

Anastasiia Zhuravel,

Yes this seams to work only for the classic UI no for the Freedom. I need a solution for the new UI

Same, Client wanted something similar for an integration with an external application. Was looking forward to more advanced capabilities in Freedom UI

Hello,

It seems that IFRAMECONTROL view type is not supported in Freedom UI and also we don't have any example of this implementation internaly. I've asked our core R&D team to add this possibility in the out-of-the-box configuration and provide some examples in the Academy. Thank you for this idea and helping in making the app better!

Oleg Drobina,

Looks is something very needed for the clients :)

Federico Buffa 😀, Damien Collot, 

It's possible to do that with the help of this article:

https://academy.creatio.com/docs/developer/front_end_development_freedo…

In the 2.b "Declare the component class", you should insert your iframe HTML markup.

Also, keep in mind that not all sites can be inserted as iframes due to different security settings.

We have plans to implement a no-code component, but not in the nearest 8.1 release. Thank you for your feedback about this.

Hello, 

Please check the discussion regarding your question here.

Bogdan,

Hello Bogdan, 

Thank you for your response.

But I wanted to reload the detail in Freedom UI, the detail is in the form page and on click of '+' we add the new details which is in other form

Once I save the details the page automatically moves the parent form page. But the detail is not refreshed, Only the record gets added to the detail.

I wanted to refresh entire detail after click of Save while saving a new record in child form.

const handlerChain = sdk.HandlerChainService.instance;
                             await handlerChain.process({
                            type: "crt.LoadDataRequest",
                            $context: request.$context,
                            config: {
                                loadType: "reload"
                            },
                            dataSourceName: "datasourcename"
                        });

This works in the current form page. But i wanted to refresh the detail in parent form page once I click on save button in child form page.

GargeyiGnanasekhar,

Unfortunately, we don't have ready examples of the implementation of your business task.

We've registered it in our R&D team backlog for consideration and implementation in future application releases.

Thank you for helping us to improve our product. 

Hi,

Please use a business process in this case to read all remaining records from the detail and update their values that will be triggered upon record deletion from the object of this detail. It's much easier than trying to create a UI logic using DeleteRecordReqeust.

Oleg Drobina,

Hello Oleg, 

I have almost implemented functionality in the client schema under deleteRecordRequest handler. Right now the functionality is working irrespective of the confirmation option choosen, It works even when we click No from the confirmation box. 

I wanted to make the functionality to work only if I click "Yes" from the confirmation box. 

Is it possible to read the option chosen by user while deleting a record(either Yes or No) in the handler?

Thanks

GargeyiGnanasekhar,

What I've observed from the behavior is that the DeleteRecordRequest is called twice: once you click delete button and once you select one of the yes\no options. Then I was trying to find a difference in either requests contexts or in the requests, but there is none or it's not obvious. And finally if we take a look at the initiator of the GetCanDelete method (that is called once you hit the "Yes" option) it's also not obvious who calls it:

I really tried to find a place in the code that could be overriden, but it seems that it's impossible to do in the current version (tested in 8.0.6). That's why I've asked to use a business process instead.

If you want to initiate the delete from your own code, you can use the Model class for that. See https://customerfx.com/article/deleting-a-record-from-client-side-code-…

If you're handling the crt.DeleteRecordsRequest you could simply not call the "next" handler in the chain. Basically, only call this if the answer is yes: await next?.handle(request); 

Ryan

Hello, 

See this article https://customerfx.com/article/prevent-navigating-back-to-a-parent-page…

There's an isSilent param in the page config you can change to prevent it from closing.

Ryan

Hello,

This article will show you how to navigate to a new page on a Freedom UI page: 

https://customerfx.com/article/navigating-to-a-page-via-code-in-a-creat…

If you want to open an edit page for a record, or an add page, this article outlines how to do that: 

https://customerfx.com/article/opening-an-edit-page-to-add-or-edit-a-re…

Ryan

Also, as far as having the button trigger both - there are two routes you can take. 

Route 1 - If you'd always go to this other page after saving, you could just do that when the save request is triggered. This article shows how to listen for when the page is saved, then you could navigate to the other page from there: https://customerfx.com/article/adding-code-to-the-save-event-of-a-creat…

Route 2 - If you're only wanting to save, then go to this other page, when your own button is clicked, and not for all saves, then you can wire up your own handler for your button. This article shows how to to that: https://customerfx.com/article/adding-a-button-to-execute-custom-code-o… In the handler, you'd save the page, then navigate to the other page. If you go this route (creating a custom request for your button). It would look like this:

{
	request: "cfx.clickMeButtonClicked",
	handler: async (request, next) => {
		// make sure you've added the "@creatio-devkit/common" as mentioned in the articles			
		const handlerChain = sdk.HandlerChainService.instance;
 
		// first save the record
		await handlerChain.process({
			type: "crt.SaveRecordRequest",
			$context: request.$context
		});
 
		// now navigate to the other page, this navigates to the orders section
		await handlerChain.process({
			type: "crt.OpenPageRequest",
			schemaName: "OrderSectionV2",
			$context: request.$context
		});
 
		return await next?.handle(request);
	}
}

Ryan

Ryan Farley,

Please note that it's best to pass context to each handlerChain.process call. So, in your example, the second call should be:

		// now navigate to the other page, this navigates to the orders section
		await handlerChain.process({
			type: "crt.OpenPageRequest",
			schemaName: "OrderSectionV2",
			$context: request.$context
		});

Oleksandr Khardikov,

Thanks for that. I've updated the code in my reply for completeness and also the articles on my website.

Ryan

I don't believe you can set a default for tomorrow's date in the object property defaults (unless you add it in the entity code). 

It's done pretty easily on the page if you want to add the code there, it would look like this (for a Freedom UI page):

handlers: /**SCHEMA_HANDLERS*/[
	{
		request: "crt.HandleViewModelInitRequest",
		handler: async (request, next) => {
			const result = await next?.handle(request);
 
			const cardState = await request.$context.CardState;
			if (cardState == "add" || cardState == "copy") {
				request.$context.TheDateFieldAttribute = Terrasoft.utils.date.addDays(new Date(), 1);
			}
 
			return result;
		}
	}
]/**SCHEMA_HANDLERS*/,

Ryan

Ryan Farley,

Thank you, it worked 

Hello,

You can change that by adding a handler like this - note this will change the value from "New record" when adding a new record for the page:

handlers: /**SCHEMA_HANDLERS*/[
	{
		request: "crt.HandleViewModelInitRequest",
		handler: async (request, next) => {
			const result = await next?.handle(request);
 
			const cardState = await request.$context.CardState;
			if (cardState == "add" || cardState == "copy") {
				request.$context.HeaderCaption = "Add a new something";
			}
 
			return result;
		}
	}
]/**SCHEMA_HANDLERS*/,

As far as binding it to some page value, you could use the same but first get a value from the page. Something like this:

handlers: /**SCHEMA_HANDLERS*/[
	{
		request: "crt.HandleViewModelInitRequest",
		handler: async (request, next) => {
			const result = await next?.handle(request);
 
			const cardState = await request.$context.CardState;
			if (cardState == "add" || cardState == "copy") {
				request.$context.HeaderCaption = "Add a new something";
			}
			else {
				// get a value from the page
				const someValue = request.$context.someAttributeOnThePage;
				request.$context.HeaderCaption = someValue;
			}
 
			return result;
		}
	}
]/**SCHEMA_HANDLERS*/,

Ryan