We have a creatio instance with around 100 users, who in order to authenticate use the Creatio authentication. This users are set in specific organizational and functional roles, with access rights applied to them.
We will do a sync with Active Directory through LDAP for the same 100 users, so that the users use LDAP authentication to log in to Creatio and not Creatio authentication?
1-Will these cause any duplicates with the existing Contacts ?
2- Should we deactivate the licenses of the existing users before doing the sync with AD ?
During synchronization with LDAP is checked table SysAdminUnit (table section Users), so when you synchronize the new user will be created.
You can re-bind the contact with an SQL query and then delete the new contact.
The connection to the table of contacts in SysAdminUnit is made by the ContactId column.
Also, by checking the SysAdminUnit table, if the system already has a user bound to a contact, we cannot create another user bound to an occupied contact.
If users were previously synchronized over LDAP and they have an LDAP element, the system should not generate new contacts/users.
I can change access rights to object in process. But before providing access rights to Document I would like to check whether desired group already has access to record. Is it possible to do it by process?
I created an attribute to be able to disable it when there is an unsaved field, the problem is that I can't change it, and the page in the two images above are the same page, it is a detail page.
Could you please share with us more details on the page/detail where you are using this, and the current code implementation that you have for your button?
Is there a way to freeze a record - lock all fields and connected details - based on a condition? For example, if an Order status is set to Completed, all the fields and details connected to order record should be locked. In order to make any change to the record, the status has to be changed from Completed to In Progress and then the record is unlocked.
If you wish to change access rights on a particular stage of the Order, you can simply add a "Change access rights" to its stage:
With it, you can state which roles/users should have their rights set to "read-only".
Alternatively, you could create a trigger process that is triggered once the stage of your Order section is changed and then do the same rights delegation as mentioned above with the "Change access rights" element in your business process (I created an example that is based on the stages of the leads section):
However, the most reliable way to do this is to use a process and change the access rights of the record(s) - otherwise, they could still be changed in other places, such as the mobile client.
There are webservices that are called from client side when some fields are changed. Even with the permission restriction, these change events will still be triggered when the value is changed although it can not be saved by clicking the save button.
Looks like Ryan's solution is more compatible with the customizations we have in place now. That would help us lock the field giving no provision for the user to change the field value.
I have an editable list, and I want that one of its columns "Product" be displayed as a link. So that when its clicked it redirects automatically to the Product section.
How can this functionality be achieved ?
Does this involve overriding the addColumnLink: function ?
Microsoft stopped using the "Basic authentication" type for mailbox authorization. Therefore, to solve the issue, It recommends switching to the OAuth authorization type to restore mail synchronization in the application. Microsoft provides the following set up instructions - https://learn.microsoft.com/en-us/exchange/clients-and-mobile-in-exchan…
For the application version 8.0.2 and above the steps are the following:1. Setup the application in Azure.
2. Make changes to the mail provider on the Creatio side (change from basic to OAuth and fill in data form Azure side).
3. All user mailboxes will require user action to grant permission to continue synchronization.
Older versions:1. Setup the application in Azure.
2. Setup the mail provider on the Creatio side (It’s better to create a Copy of the existing mail provider and use it but it’s also possible to change the old one)3 .a If it is OK to delete the mailbox and add it with the new mail server – it’s the easiest way and will cause no additional issues. That’s all.
3 .b In case you cannot / don’t want to delete a mailbox and want to adjust it to use the new mail provider then your IT team should do steps 1and2and then contact Creatio support asking to:- Update the MailServerId column of the MailboxSyncSettings table with the value of the new/adjusted mail server that can work with Oauth.
- Run the script: update "MailboxSyncSettings"- set "ErrorCodeId"='5f906e1c-9521-45df-8e43-82b5109e0e4d'- where "Id"='the_Changed_Mailbox'4. All user mailboxes will require user action to grant permission to continue synchronization.
As Bhoobalan mentioned, Microsoft has disabled basic authentication for Office 365 accounts, which means you can no longer use a username & password to log in from other applications (such as Creatio). Instead, you need to create an OAuth app in the Office 365 Azure portal, then use that in Creatio.
We followed all the steps as per your link, and then tried to update the new password in Creatio ( where it shows warning message like specify the new password). It gives the same error message.
But when I deleted my email account and re-added , it works fine.
Do we need to delete all the email accounts ( We have 5 email accounts for renewal, case process) and re-add them ? or do we have any other way to provide permission and make it sync without deleting them ?
Yes, The steps are the same for versions below 8 as mentioned.
It's not mandatory to delete the mailbox and re-add them but if it is fine to remove and re-add the mailbox, it's the easiest method to do.
All 5 accounts must be of Office 365 and currently you have updated the OAuth in Creatio following Ryan's article. So you can remove the other mailbox and re-add them and synchronize it.
