Hello,
 

Thank you for your question. To provide a more detailed analysis, could you please clarify the following:
 

1. 1. We need screenshots of the specific functionality you require.
2. 2. Please specify whether this functionality is needed in the Freedom UI or the Classic UI.
    

Your cooperation will help us assist you more effectively.
 

Thank you!

Hi, Victoria!

Please turn to us via Creatio Support so we can examine the system behavior in further detail.

Dear Kevin,

We appreciate your patience as we consulted with our R&D team regarding the concerns you raised.

Regarding the connected record in the feed panel, we are pleased to inform you that the behavior you mentioned will be addressed in the upcoming 8.0.3 version. 

If you have any further questions, please let us know, we would be happy to help.

Thank you for choosing Creatio!

Alina Yakovlieva,

Is there any update on this feature? I can't find any documentation mentioning how to enable the record name in Freedom UI feed.

Kevin Brady,

Hi!

Unfortunately, currently, there is no ETA for the implementation of this functionality.

You request has increased the priority of the task.

Your can monitor our Release notes using the following link: https://academy.creatio.com/docs/8.x/resources/category/releases

Thank you for your patience!

Have a great day!

Alina Yakovlieva,

So the previous commitment got delayed and now it's not even on the plan? Just saying the section in feed is not helpful to users.

Hi Kevin,

I've written up the steps for adding an IFRAME in Freedom UI here:

https://customerfx.com/article/embedding-an-iframe-on-a-creatio-freedom…

Ryan

Hello!

In version 8.1.0 tags will be implemented in Freedom UI, the approximate ETA for it is the end of September.

Hi Jerome,

They are working for me. One thing I did initially was add it to the control in the viewConfigDiff. You're actually supposed to add the validator to the attribute in the viewModelConfig - not to the control in the diff. Once I moved it there it worked. Your column is likely in the viewModelConfig already (if it's been added to the page). Look for it there and just add the validator to that existing attribute in the model.

Ryan

Thanks Ryan,

I managed to step into my validator, but there's no way to retrieve some values (since request is not defined).

Best regards,

Jerome BERGES,

Hmm. Not sure about that. I've only used validators where I need the control's value only (which is provided in the params passed in). I had assumed you could pass in other values in the validator params, but that doesn't seem to be the case (or at least I can't figure out how that works). Hopefully we'll see more documentation soon.

Ryan

Joaquin Eztala,

Currently, the R&D team is working on such task, they plan to create a solution in the next releases. You can try to workaround in this way:
On the field's change add a custom handler, set a flag in it, look at this global flag (atribute's value) in the validator.

Most likely to validate "if end date it's not before the begin date" you can use in handler await request.$context.DateTimeAttribute_nnnn

Where DateTimeAttribute_nnnn:

	"attributes": {				
	"DateTimeAttribute_nnnn": {
		"modelConfig": {
...
"validators": {
			"StartDateIsNotNotLessThanProjectStartDate": {
				"type": "dw.StartDateIsNotNotLessThanProjectStartDate",
				"params": {
					"message": "#ResourceString(StartDateIsNotNotLessThanProjectStartDateMessage)#",
				}
			},
           "StartDateIsNotNotMoreThanProjectDueDate" ...
		}

Anhelina,

A quick question if I may, how do you create a global flag in a client module and how do you look at it in a validator function.  Thanks,

edit: I used session storage in the end.

Gareth Osler,

By the phrase "global flag" I meant the attribute value.
This method hasn't been tested, and I can't give you a guarantee of stable work. 

We're still waiting for the out-of-the-box realization and will post the article with updates on the Academy.

Hello,

Unfortunately, it is currently not available to enable Multiple selections of lookup values in Freedom UI.

 

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.

Hello,

You can try another approach: the column that is responsible for the section list page that will be opened when going to the section is SectionSchemaUId (in the SysModule table). This column represents data from the UId column of the SysSchema table. What can be done to force custom page to be opened when opening the section is modifying the current SectionSchemaUId column value for the proper SysModule table record to the desired value. So you need to find the SysModule record responsible for your current section (for example using the query like:

select * from "SysModule" where "SectionSchemaUId" in (select "UId" from "SysSchema" where "Name" = 'UsrTest_ListPage')

), use an Id of the record found and then use it in the query like:

update "SysModule" set "SectionSchemaUId" = 'desired UId of the UsrPage_ebkv9e8 schema' where "Id" = 'Id found previously'

and relogin to the app after that. I recently tested it and the Services_ListPage was opened for my custom Freedom UI section:

Oleg Drobina, thank you so much! I tried this approach before and it doesn't work probably because I had a mistake with the IDs. Now it is working. Appreciate your help. Regards

Creatio 8.0.10 https://academy.creatio.com/docs/release/release-notes/8010-atlas-relea…

There is an issue in current versions of Creatio with the filter classes, such as FilterGroup etc, being applied to model load/queries. I've been reporting this issue since 8.0.6 (#SR-01182879) but it's still not yet fixed in 8.0.9, very frustrating (I've been told it will be fixed in 8.1 #SR-01198668 🤞🏻). However you can still use them with a small workaround. The example below will get all Accounts that have Type = Customer:

// make sure to add "@creatio-devkit/common" as sdk
 
const accountModel = await sdk.Model.create("Account");
 
const customerFilter = new sdk.FilterGroup();
await customerFilter.addSchemaColumnFilterWithParameter(sdk.ComparisonType.Equal, "Type.Name", "Customer");
 
// This is the workaround you have to do for the filters to work.
// Shallow copy to a new object and then reassign the items collection.
const newCustomerFilter = Object.assign({}, customerFilter);
newCustomerFilter.items = customerFilter.items;
 
// now use new shallow copied filters in the query
const customers = await accountModel.load({
    attributes: ["Id", "Name", "Type"],
    parameters: [{
        type: sdk.ModelParameterType.Filter,
        value: newCustomerFilter
    }]
});
 
// the customers variable is now an array of accounts with Id, Name, and Type columns
console.log(customers);

The whole issue with the FilterGroup is that the items collection doesn't get unrolled from a collection to an array - the copy forces the object to flatten out how it's expected by the underlying DataService call.

Ryan

Ryan = Creatio's code gap workaround master

Ryan Farley,

This is my code : 

handler: async (request, next) => {

        // Get the selected date values

        var dateFrom = new Date(await request.$context.DateTimeAttribute_6jtq65k);

        var dateTo = new Date(await request.$context.DateTimeAttribute_vg9eydm);

        var datesBetween = [];

          var currentDate = new Date(dateFrom);

          while (currentDate <= dateTo) {

        datesBetween.push(new Date(currentDate));

        currentDate.setDate(currentDate.getDate() + 1);

          }

  // Convert dates to integers without the time component

          var datesAsIntegers = datesBetween.map(date => {

        return parseInt(date.toISOString().slice(0, 10).replace(/-/g, ""), 10);

          });

        const accountModel = await sdk.Model.create("UsrEntity_a6e9b72");      

        // Load the accounts based on the filter.

        const accounts = await accountModel.load({

            attributes: ["DateTimeAttribute_x2whel6"],

        });

        console.log(accounts); 

            for (const value of accounts) 

            {

                for (const value1 of datesAsIntegers)

                {

                   const integerValue = parseInt(value1);

                value.NumberAttribute_ejh4wbq === integerValue;

                }

                console.log("1");

            }

return next?.handle(request);

        }

Here we are trying to get value of "NumberAttribute_ejh4wbq" but we are only getting "Id" .

Can you help us with this?

Verify that the column name is correct. In the accountModel.load your passing the attributes array with "DateTimeAttribute_x2whel6", this needs to be the column name in the object/table (which will likely start with a Usr)

Ryan