The necessary filtering can be implemented in section page source code. In order to do that you will have to write the handler for crt.LoadDataRequest request that appears when the lookup is opened.

Here is the example of the implementation:
 

/**SCHEMA_MODEL_CONFIG_DIFF*/,
	handlers: /**SCHEMA_HANDLERS*/[
		{
			request: "crt.LoadDataRequest",
			handler: async (request, next) => { 
				if(request.dataSourceName !== "PDS_UsrDoctor_sm2qg7w_List_DS") {
					return await next?.handle(request);
				}
				console.log('Lookup Load Data...');
				const cardModel = await sdk.Model.create("UsrHospitalVisitCardV3");
 
				// now load the records and provide the filters             
				const cards = await cardModel.load({
					attributes: ["UsrDoctor"]
				});
				console.log(cards);
 
				if (cards) {
					const filter = new sdk.FilterGroup();
					filter.logicalOperation = sdk.LogicalOperatorType.Or;
					cards.forEach(async (card) => {
						if(card.UsrDoctor && card.UsrDoctor.value){
							await filter.addSchemaColumnFilterWithParameter(sdk.ComparisonType.Equal, "Id", card.UsrDoctor.value);
						}
					});
 
					// note, these lines are only needed due to an issue with filters in Creatio-DevKit SDK
					// expected to be fixed in Creatio 8.1
					const newFilter = Object.assign({}, filter);
					newFilter.items = filter.items;
 
					request.parameters.push({
						type: "filter",
						value: newFilter
					});
				}
 
				return await next?.handle(request);
			}
		}
	]/**SCHEMA_HANDLERS*/

 
In the example above "PDS_UsrDoctor_sm2qg7w_List_DS" is the name of the lookup that has to be filtered and "UsrHospitalVisitCardV3" is the object that contains that lookup and which records we should check.

You can also find some additional details and useful information in the articles:
https://customerfx.com/article/dynamically-filtering-a-lookup-on-a-creatio-freedom-ui-page/
https://customerfx.com/article/querying-data-using-filter-conditions-via-the-model-class-equivalent-to-enityschemaquery-in-a-creatio-freedom-ui-page/

Yes, you need to activate the new beta feature in 8.2.1 : https://academy.creatio.com/docs/8.x/resources/release-notes/8-2-1-ener…

++++

Hello,
 

You can implement the following code to reload the data source when you get to the Freedom UI page on the crt.HandleViewModelInitRequest.
 

Sample implementation for “Opportunities_FormPage”

define("Opportunities_FormPage", /**SCHEMA_DEPS*/["@creatio-devkit/common"]/**SCHEMA_DEPS*/, function/**SCHEMA_ARGS*/(sdk)/**SCHEMA_ARGS*/ {
...
        handlers: /**SCHEMA_HANDLERS*/[
              {
        // Load data grids
      request: 'crt.HandleViewModelInitRequest',
      handler: async (request, next) => {
          console.log("You returned to FreedomUI page");
            const result = await next?.handle(request);
            const handlerChain = sdk.HandlerChainService.instance;
            await handlerChain.process({
                type: 'crt.LoadDataRequest',
                $context: request.$context,
                config: {
                    loadType: "reload"
                },
                dataSourceName: "ContactRolesListDS"
            });
            return result;
      }
  }

Serhii Parfentiev,

Hello Serhii,

Have you actually tried it ? HandleViewModelInitRequest is not even triggered when you close the classic ui page (nothing in the console log)

Sasor

++++

++++

++++

++++

+++++++

Hi Community,

Is there any idea about this topic?

Sasor

Hello,

When clicking on the "Complete" button from the next steps, the system will show you the Freedom UI mini page, as this is a Next Steps core logic.

The only way to avoid opening this mini page is to develop your only Next Steps tiles and assign different logic for the complete button.

Dymytriy Vykhodets,

can you please help me where this core logic is written. so that i can try to create new logic.

Dymytriy Vykhodets,

the idea is to open the main page in place of mini page when we click on complete button

Alok Kumar,

Yes, we want to opent the main page directly

Hello, is there an additional information on this particular need? Is there a documentation to be followed for "developing custom Next Steps tiles and assign different logic for the complete button"? In some cases, complete button is expected to be enough to complete the action at that time. Is there any additional resource on this topic?

Hi Shemroy!

This error can occur when the contacts you are trying to merge are linked to a system user.

When trying to merge them, the system attempts to link one contact to another user, but a contact cannot be linked to more than one user. This results in an error, since the system does not allow this situation.

Such user-linked contacts should not be merged. If necessary, you can deactivate one of the users and rename the contact to avoid confusion.

Since deleting a user is not supported by the system by design, deleting a contact linked to such a user is also not possible.
 

If you have any further questions, please let us know, we would be happy to help.
Thank you for choosing Creatio!

Hello Vladimir,

I've the same question and I followed these steps for Contact section:

1. Create a replacement for the Freedom client schema. Please create a new client module, and for the URL in the browser, change schemaType=9 
for example like that: .../0/ClientApp/#/ClientUnitSchemaDesigner/new?packageId=db5d44a0-881e-ba1b-3396-a2dfae3fecee&packageName=test_contacts&schemaType=9
2. Set Parent object -  Contacts form page (Contacts_FormPage)

3. Change del module script 

viewConfigDiff: /**SCHEMA_VIEW_CONFIG_DIFF*/[
			{
				"operation": "insert",
				"name": "Checkbox_Custom",
				"values": {
					"layoutConfig": {
						"column": 1,
						"row": 2,
						"colSpan": 1,
						"rowSpan": 1
					},
					"type": "crt.Checkbox",
					"label": "$Resources.Strings.PDS_RecordInactive_Custom",
					"labelPosition": "auto",
					"control": "$PDS_RecordInactive_Custom"
				},
				"parentName": "SideAreaProfileContainer",
				"propertyName": "items",
				"index": 1
			}
		]/**SCHEMA_VIEW_CONFIG_DIFF*/,
		viewModelConfigDiff: /**SCHEMA_VIEW_MODEL_CONFIG_DIFF*/[
			{
				"operation": "merge",
				"path": [
					"attributes"
				],
				"values": {
					"PDS_RecordInactive_Custom": {
						"modelConfig": {
							"path": "PDS.RecordInactive"
						}
					}
				}
			}
		]

Hello,
 

The solution provided by Stefano is a good one. 

An alternative solution was discussed in this post: https://community.creatio.com/questions/recordinactive-checkbox-missing-freedom, and you can use the approach from there.
 

However, we still recommend adding the required column directly via page metadata, as described above.
 

We already have a backlog task to address this issue in future versions of the application.
 

Thank you for reaching out!

Stefano Bassoli,

Hello Stefano,

I just followed your advice and it worked well, thanks!

However, is it possible to select the field in the conditions part of the business rules? It doesn't show up there either.

Thanks,

Robert

Hi,
 

Unfortunately, there is no direct way to perform such printing.

However, you can configure this logic using a workaround.
 

For example, if you want to export all records from the "Invoice" section into a single report, you can follow these steps:

1.Create an "Invoice report" object (optionally, you can create a section for it).

2. In the "Invoice" object, add a lookup column that references "Invoice report" (e.g., UsrInvoiceReport).

3. Create a single record in the "Invoice report" section.

4. Update all Invoice records, setting the UsrInvoiceReport column (from step 2) to the record created in step 3.

5. Create a report based on the "Invoice report" object and add a table section for the "Invoice" object, linking them as follows:
 

Invoice report.Id = Invoice.UsrInvoiceReportId
 

This way, you will generate a report that includes all records from the Invoice table, as they all reference the same record.
 

You can also use this same section for other objects like Document, Order, etc. by repeating steps 2-5.
 

Hope this helps! Take care! 😊

Hello,

Unfortunately, it is not possible to hide "+ Add a new step" button within the "Next step" using OOTB functionality. This can only be achieved with development tools, but we currently do not have examples of such an implementation.

Additionally, we have created a task for the responsible R&D team to consider adding this functionality in future releases.

Hello Harvey,

The task is still in progress and the only workaround that currently exists is using the text column instead of a number. In case this number should be processed it can be done using type casting in formulas (or script tasks) of business processes.

I've also added your voice to prioritize the problem for our R&D team. Hope this will be implemented soon.

We are also experiencing this issue when searching by dates. For example, 4/5/1967 will generate a hit, but not 04/05/1967.  Interested in being added to any prioritization tickets on this.

Anna Pannier,

Please create a separate question in the community with a description of how exactly the search is performed and which datatype your current column that stores the date has.

Hello,
 

You don't need to use programming for this task.
You need to create an object replacement (in your example, an Account object replacement), in which you can set the default value for the corresponding columns, save the changes, and publish the object.





 After that, when you open the pages of creating records, you will see the fields immediately filled with the default values.



These links can also be useful for you to find more options for achieving your goal:

https://academy.creatio.com/docs/8.x/dev/development-on-creatio-platform/development-tools/creatio-ide/configuration-elements/object

https://community.creatio.com/questions/it-possible-set-default-value-f…

Thank you.

Hello Serhii,

Thank you for the reply.

1) We can not utilize the generic default value, becasue depending on the conditions the Type, might have differnetvalues.

2) Our frontend logic is associated with OpenSelectionWindowRequest. In the documentation of OpenSelectionWindowRequest there is no documentation for default values.

Is there any workaround to achieve this?
Sasor

If you need to use a value based on one of the fields of an object, it is fashionable to use business rules at the object level, which, depending on the value in one field, will set the value for another field using the “Set values” option.




 

Hello community,

any new development in the new versions of the codebase that allows us to set default values on OpenSelectionWindowRequest?

Sasor