The following are some common access related use cases that we have encountered in the past -
1. By default, filter and show only certain section records to certain Org/Func roles.
2. Filter detail records by a specific column and show only a subset of records to a certain Org/Func role.
As of now, applying default filters for section lists and details can only be done by writing code. There are cases where analysts are not comfortable with writing code and enabling these to be done via no-code configuration capabilities will be a value addition to them. This will also improve app maintainability and ease of modification when compared to writing code.
We will register both propositions for the R&D team so they will consider possibility of adding or simplifying this functionality in future.
However, can you please specify why is it not convenient for you to set up access rights with record permission enabled for some section for each role needed?
In this way all users will be able to see only those records for which they have access rights granted.
It possibly can be a no-code solution for the first point stated in your idea.
Hi Roman. Thank you for the response. The use case would be something like this -
A section contains a list of records with one column being country. These records are inserted programmatically and not manually. We have distinct organizational roles for each country. We need to display only those country records to users of those organizational roles.
If the above scenario can be handled via record permissions, Pls let me know. From what I read, record permissions are based on the record author. Follow up question -
Can I insert records programmatically (ESQ) as a user from a specific Org role? If Yes, then I could use record permissions to handle my use case.
Creatio has a 'Last write wins' policy with respect to handling concurrent updates to the same record. Use case below -
User 'A' and 'B' have the same contact's page open at the same time and intend to modify the same field. 'A' changes a field and saves it. However 'B' does not know that the field value has changed behind the scenes and in turn modifies the value. B's change overwrites A's and neither user knows that this has happened.
Multiple users having access to 1 record is common place where people work in teams and an entire Org role has access to modify a set of records. There are also cases where Creatio will need to co-exist with other enterprise systems which modify the same record thus creating a shared source of truth.
Request the following ideas to be considered to be added to the platform -
At a first level, users need to be alerted of any changes to a record they are currently viewing. That way, they can refresh to get the latest values and take corrective action.
At the next level, when the user saves their changes, S/he can be presented with their version of changes vs the version of changes done by another user - thereby enabling manual resolution of conflicts.
Thank you for providing us with ideas that can improve the customer experience of using the Creatio platform. For the 1st idea, we have registered a separate request to our R&D team. If this idea will be in high demand it can be implemented in future versions of the application after additional analysis. Also, you can contact our manager to discuss the faster implementation of the required functionality.
Accordingly to 2nd idea: if I understood your request correctly, this kind of functionality is already provided with out-of-the-box version of the application. For this purpose you can use "Change log" section. The change log contains information about adding, modifying, and deleting records (entries) in the database tables for Creatio objects. This includes sections, details, lookups, as well as other objects.
More information about "Change log" you can find in the next atricle:
Hi Roman. Thank you for the response. Yes, I am aware of the change log and it certainly helps in retrospective action. But, It doesn't help in conflict resolution at the moment of the conflict.
It will help if a user is presented with the conflicting changes at the moment s/he saves - so that they can decide which values are the correct ones and then save.
As Creatio has formerly given up with the idea to develop the conception of the landing pages within the CRM (that was planned in release 7.17), I propose that the API for the landing pages would be able to receive attachments either in Base64 converted attachments either in Binary.
Suggestion: Add two properties on the No of employees Lookup;
Employee range low point (int) Employee range high point (int)
This lookup would for example in row '2-4' hold 2 and 4 respectively.
This way I can easier match the correct property value to an integer.
Let's say I have a API that gives me information that this Account has 475 employees. I need to match this information to another integer to fid the correct lookup.
It would look like this:
Employee range low point =< 475 && Employee range high point => 475
I could change this on my and my cusomers environments but I believe it's a good idea to have it be the same everywhere!
I have a lookup with a list of countries along with the phone code for each country. I need to be able to display list of countries and select the country in one place and also be able to select a phone code from a list of phone codes in another place.
This is currently not possible as one object can only have 1 display value. I can either show a list of countries or phone codes.
Being able to show different display values from the same underlying lookup seems like a good feature to have. Reduces complexity of look up creation and maintanence.
Yes, this is a good idea to have multiple display values for the object and it was already registered for our R&D team. I will also let them know about your community post so to prioritize the problem for them. Thank you for helping us to make our application better!
