Same here in our cloud dev environment with this new 8.1.2 functionality

You are right, we do not have the problem on our production environment, only on the dev env.

Hello,

Please note that this issue is connected to the 8.1.2 release and in order to fix it you need to create a case directly for our Support team (support@creatio.com) so we could work with the site in question.

Not possible. However, coming Q2 2024 are new business rules that you can show/hide things based on a user role. So you could at least have different elements show/hide on the same page for various roles. https://academy.creatio.com/docs/release/creatio-roadmap?search=role&ch…

Ryan

Hi Ryan,



Thanks, will see if that could work as possibilities might by bigger with these new business rules.



We have 2 different pages today in classic UI with quite different approach, was hoping not having to a nocode implementation with Freedom UI.



Cheers,



Damien

It is possible to have many different pages for the same object. You could do something like, from the base page, check the user role and then redirect to some version of the page for that role. However, that could get messy and would likely be easier to just have tabs for each role that show/hide as needed.

It's also possible to create pages based on database views, so in theory you could have entire sections of the same data tailored to different roles as well, but that sounds like an unnecessary amount of work, especially since you'd have to update the views every time a new field was added to the object.

If it's based on a field such as a "Type" it can all happen in the same way that it did for classic pages - that is implemented in Freedom UI.

Ryan

Hello, 

Unfortunately, Creatio no longer supports contact synchronization with Exchange and Google. This lets you improve the security and relevance of your customer base.



Regards, 

Orkhan

Orkhan,

Thanks for the response, but I think users have the necessary competency to decide which data is relevant in their CRM system.

Also, how is this enhancing security?

Many other CRM systems provide the feature to sync contacts and leads often request it!

BR

Robert Pordes,

Greetings,

Thank you for your clarifying questions. We removed this feature for several reasons:

1. This functionality had unresolved logical issues.
2. This functionality was hardly, note, hardly, used by our users.
3. Security-wise, an Abstract Sales Representative could synchronize the entire contact database to themselves and depart from the company, thereafter potentially utilizing or passing on the contacts to the company's competitors.

Hello,

 

Please make sure that the URL of Identity service has the following appearance in the field: https://yoursite-is.creatio.com without a slash at the end.

Hello!

This means that there can be logic at the event layer level that changes the value of this field when saving a record. It can be on action: OnUpdating, OnSaving. Details here:

https://academy.creatio.com/docs/8.x/dev/development-on-creatio-platfor…

Or changing a given field leads to another action that changes its value again.

To track exactly where this field changes, you can write additional logging when the record is saving, in various methods, such as OnUpdating and OnSaving, on the EntityEventListener. This logging will help you find exactly where the field value changes.

Hello!

You can use the filtersConfig parameter to filter records, as mentioned in the article.

Or you can use the option selectionState to predefine selected rows, which will be pre-selected when the lookup page is opened.

Example of selected records:

{
	type: "crt.OpenLookupPageRequest",
	...
	selectionState: {
		type: 'specific',
		selected: [
			'00000000-0000-0000-0000-000000000000',
			'11111111-1111-1111-1111-111111111111',
		]
	}
}

An example of pre-filtering records:

{
	type: "crt.OpenLookupPageRequest",
	...
	filtersConfig: {
		filterAttributes: [
			{
				name: 'MyFilter',
				loadOnChange: false
			}
		],
		attributesConfig: {
			MyFilter: {
				value: {
					"items": {
						"29e16d42-36f1-4e04-9029-4321cbb2494d": {
							"filterType": 1,
							"comparisonType": 11,
							"isEnabled": true,
							"trimDateTimeParameterToDate": false,
							"leftExpression": {
								"expressionType": 0,
								"columnPath": "Name"
							},
							"isAggregative": false,
							"dataValueType": 1,
							"rightExpression": {
								"expressionType": 2,
								"parameter": {
									"dataValueType": 1,
									"value": "Super"
								}
							}
						}
					},
					"logicalOperation": 0,
					"isEnabled": true,
					"filterType": 6,
					"rootSchemaName": "Contact"
				}
			}
		}
	}
}

It is still the same since the Lookups area is still classic UI.

Also, BTW I have the instructions with Postgresql instructions here, if interested/needed: https://customerfx.com/article/creating-an-edit-page-for-a-lookup-in-cr…

Hello Harvey,

It's not possible for now, but 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!



Unfortunately, there is no such possibility now. We have registered a request for the development team to consider adding this option in future updates. 



Best regards, 

Anton

Hello!

Unfortunately, there are no approximate timelines for implementing the functionality. 
However, you might be interested to know that we have the functionality to change DCM conditions on the pages.

We would also appreciate it if you could provide more details about the business task you plan to implement.

First read the record using whatever Identifier you have on it from the source data. If the record exists the Id value will be a Guid and if it doesn't exist the Id of the record will be Guid.Empty.

So the condition for the update will look like: 

[Id from the Read] != Guid.Empty (this means the Read found the record)

The "else" will proceed to the Add, just make sure you populate some identifying value from the API call that you'll use when you read if the record exists next time.

Ryan