We have this business requirement where we need to add duplicated communication options. For example, we can have two records for the same phone number.
When we try to add the same number, we receive the following error:
The idea here is to use the same type. For example, we need to create multiple duplicated instances for "Mobile Phone", because later on we will be using these records for our business logic. The number might be the same, but we have other attributes that have unique keys. We want to change this rule so it can be applied to those attributes.
We are localizing in Italian our application. We are using the OOTB Email Page for sending email and replying to email.
In the reply email window we are not able to localize the highlighted label (see attached file) while we do not have problem in localizing send email window.
May we ask some suggesting for addressing our aim?
To set localized values for the From, To, and other fields, you need to go to the settings of this field on the editing page and set the localized values as shown in the attached screenshot.
Hi Sergii, thank you very much for your response. We have already localized as per your indication and we suceeded in localized the (New Email window). We are not able ti localize the response window (reply/forward email window) even if the Creatio code page seems to be the same (Email page).
As for now, there is no such functionality. We have already registered the idea for our R&D team to implement this functionality in further releases. We will assign your case to this project to increase its priority.
I'm interested in utilizing the Script element within Creatio. Where can I find reference materials or code samples for C#?
Additionally, is there a platform available to compile C# code snippets before directly uploading them to the Creatio Platform (in the Script Task Element)?
All available examples of using the code in the script task element can be found here. As for checking the C# code - there is no such platform for business processes script tasks. You can create a code in Visual Studio and check if it works. Then, using the provided article, implement the same functionality in the business process script task.
Is it also possible to create your Standard source code and call those from a script task? Similar to Process to calculate actual working time in projects on schedule?
as in OOP you can create an instance of a class and use its methods in the logic of a business process. Use Terrasoft.Configuration in the business process (add it to the process usings in the process settings) and create an instance of your class as SomeClass nameOfTheInstance = new SomeClass().
You can enable development in the file system as described here and there won't be a need to manually import packages in the Visual Studio. You will be able to review the code and apply changes to it.
I designed a process like following Images in dev site. In Send Email element, I checked "Ignore errors on sending". But Creatio threw error end terminate this process. What is wrong with this?
Please delete all those mailboxes from the program and synchronize them again on behalf of the supervisor user to address this issue. To avoid such a situation in the future, we recommend synchronizing the mailbox once and allowing shared access to it for other system users, as described in the academic article here.
As the title says, we sometimes need to disable buttons while still showing them - something which was easy to do in Classic UI. Is there any way of doing so in Freedom UI? I can't see any examples in OOTB Freedom UI areas, anywhere that does have disabled buttons OOTB are in Classic UI sections (e.g. the "Finish session" button on the System User page on the Access Rules tab when no record is selected).
Does it not work to bind an attribute to the enabled property of a button and set as true/false? I've not tried that, but I assume it would work? Have you already tried that?
As a note, the only way I could find to put some kind of hint/tooltip on the button when it's disabled is by using the "title" property, which gives you a standard browser tooltip display when hovering the mouse over the button. And binding that to an attribute that you change to be blank when the button is enabled.
