I need to allow only some authorized users to add new email accounts.
I didn't find any feature or operation permission that could allow mailbox creation only to certain users or groups. I only found something regarding managing shared mailboxes.
I tried giving object permissions only to system administrators but my test user is still able to add a mailbox: the UI reports a javascript error and the mailbox creation doesn't complete (see image below), but it's not what I expected.
Is there something I'm missing or that object permission doesn't work as expected?
This is the correct behaviour. There will be no notification about missing access rights, only the loading screen, but the user will not be able to add the mailbox. There is already a request created for our R&D team to add a meaningful notification for users, it will be implemented in future releases. I have assigned your request to the project in order to increase its priority. As for now, the solution described by Anastasiia is the only option.
You can create a data binding for the SysLocalizableValue object and add all the records regarding the image to this data and it will be transferred when the package is moved between the environments.
I want to change the text that appears in this pop-up, "Detail Product Terms is not filled". This pop-up appears when i click save and one of the product terms is not filled.
I have also seen in the SysTranslation table and i havent found it.
Unfortunately, It is not possible to change the text in the error message. The problem here is that the schema that defines it is very hardcoded in the application core. It is not possible to replace and modify it.
Assuming the field is a text field, you can try the following custom approach in client page schema.
1. Make the field not required in the section wizard.
2. In the client page schema, add the following code in the methods:
methods:{// Redefining the base method initiating custom validators.
setValidationConfig: function(){this.callParent(arguments);this.addColumnValidator("UsrProductTerms", this.ProductTermsValidator);},
ProductTermsValidator: function(){
var invalidMessage ="";
var ProductTerms =this.get("UsrProductTerms");if(ProductTerms.length!=0){
invalidMessage ="";}else{
invalidMessage ="Product Term is required in order to proceed";//Put your custom message}return{
invalidMessage : invalidMessage
};},
},
Now you can see your custom validation message. Similar approach can also be used for fields of type Lookup, Date, Integer etc.
You need to create a custom item view module based on the Contact object and add it to the Leads section. Please use this article as a reference where the same task is described using a custom "Books" section added as timeline item to the "Accounts" section.
I have a printable which is no longer needed. What option do I have to prevent displaying this printable in the object list of Print button? How can this printable be disabled?
I have made some fields read-only when I am creating the fields on the edit page. When I use the Open Edit Page element and try to add some values to other fields, the read-only fields also change as editable fields. I wanted to keep my read-only fields always not editable. How to resolve this issue.
Normally, Section wizard reflects the content from all the schemas up to the package indicated in the "Current package" setting.
However, UI reflects the content and logic from all the schemas of all the packages.
"Custom" package is dependent on all packages of the application (and should be the last one in the hierarchy), all columns are the same and are visible both on UI and in Section wizard once it's set as the current package.
I would suggest you check the "Current package" setting and parameters of column "Currency" on the pages in each package in the hierarchy.
I’ve this requirement where a specific user must run a specific Process. In this process, there should be a set of tasks that must gather all the attachments of the current record and generate a ZIP file with these attachments. Furthermore, this process should also download the ZIP file to the user’s computer.
Hi there! We recently uploaded an application to the marketplace
that allows you to download all the files of a section, example of an
account, in a ZIP file. Possibly it is useful for your use case or
to check how it was done.
Check it here https://marketplace.creatio.com/app/download-zip-button-creatio
Thank you for the response. We manage to find a solution for our requirement. However, If we get another use case like this one, we will have your application in mind.
on an opportunity or lead, when selecting the "client" as an account, "primary phone" is not translated in French on the client card - still shows "Primary phone", although lookup is already set as "Téléphone principal", and shows as such on main account page.
The value for this column is received from the "Phone" column of the "Account" object, so you need to go to the object itself and check which value is stored for French localization there and also save and publish the object after the changes.
The value for this column is received from the "Phone" column of the "Account" object, so you need to go to the object itself and check which value is stored for French localization there and also save and publish the object after the changes.
Or: That it does not fill "Full Job Title" when certain specific field in "Job Title" is selected (Example, if chosen "Other" then we do not want "Other" in "Full Job Title")
I've this situation where I've developed a new page for the Creatio Mobile Application. This new page has a detail and a set of columns, as you can see on the following image.
My goal is to apply a "Required Field" business rule to this detail (marked as red) based on the values of a specific column inside this page.
In the actual version of the system business rules from the desktop, the platform is not transferred to the page in the mobile application. At the moment, business rules can be set with the help of development only.
We have the enhancement request registered by our R&D. It means the functionality will be implemented in future releases, although there is no ETA yet.
