I’m currently working on a use case where we need to customize the email composer in Creatio. Specifically, we’d like to know the possibilities for:
Editing or Updating the Email Composer:
Is it possible to modify the default email composer UI or add custom functionalities?
Can we add custom fields, change the layout, or integrate additional tools within the composer?
Are there any APIs or configuration settings available to achieve this?
Adding a Scheduler on the Email Mini Page:
We have a requirement to create a scheduler feature directly on the email mini page.
The goal is to allow users to schedule emails to be sent at a specific date and time.
What’s the best approach to implement this? Would we need to create a custom section, or is there an existing feature we can extend?
Any guidance, documentation, or examples would be greatly appreciated. If anyone has worked on similar customizations, I’d love to hear your experiences.
1. Unfortunately, the Message Composer element is not customizable in the system at the moment. However, we have increased the priority of this task to add such a capability in a future product update.
2. We do not have ready-made examples of such an implementation, but you can achieve this using a business process instead of sending messages manually.
You can implement the sending functionality via a script task, where you pass the draft activity ID. A similar approach was discussed here:
I'm trying to use the "Apply Filter" function to filter a lookup value based on three parameters. The business rule works correctly when adding a new record and copy record; however, when editing an existing record, only one filter is being triggered (marked).
Has anyone encountered this issue, and is there a solution to ensure all filters are applied when editing a record?
We are trying to use Dynamic Case Management for displaying our stage process. However, since the business process involves a lot of stages (12 in total), the visual representation isn’t ideal.
We attempted to organize the stages into columns and separate them into two headers ("Which column determines which case to use with a record?"), but this has resulted in unintended behavior, such as requiring manual confirmation for stage type changes (Header changes) upon modifying the column value and some bugs.
Has anyone encountered a similar situation, or have any workarounds for this case?
We have tried to create several cases, it requires populating a start condition. The thing is that when the start condition changes based on the column value, it triggers unwanted behavior. The user need to manually confirm stage changes when the column value (start condition) is modified.
What we expect is for the behavior to be consistent with how Dynamic Case Management (DCM) works in the "Normal" setup, where the UI immediately displays the stage changes when the column value is changed, even before the "Save" button is clicked.
About several cases: At this moment we have only manual replacement and our developer's researching the possibility to automatically switching cases in future releases.
For the main question about the size and visibility of different cases, you can use the "Group with another stage" functionality.
I am trying to change the order of the address in full address field in Accounts section of Customer360 creatio. Instead of Zip + Country + State + City + Address I want it as Address + City + State + ZipCode + Country.
I have contacted our R&D team regarding this question. First of all, this logic is implemented on the backend side, which means that even if it is possible, it would likely be extremely challenging to achieve.
To conclude, I believe it is not feasible at the moment. However, I will register this as a potential improvement, and hopefully, this feature will be implemented in the future.
Thank you The issue is fixed now, As I added a CustomAddressEventListener to override the BaseAddressEventListener in the source code of my custom package.
I have created a replacing schema for "Base Page Template" and added a button , now I wanted that button to show up in every freedom ui page in every section .
This must be enough for formpages. But you will also need to add this Button to ListFreedomTemplate because it can override some changes from "Base Page Template". Also, I would recommend to run fully generate schema source and compile all actions.
I found out recently that there is a new parameter type than can be selected which is called "Create from element":
I already checked the official documentation and the new 8.2 release notes but I can't seem to find any information about this. Does anybody know what is the purpose of it?
This allows you to automatically create parameters in the process that match another process element. It’s especially useful for things like webservices or subprocesses. If you select that parameter type, it will allow you to choose the other element in the process and then it will create parameters that match that process element. If you selected a web service element, for example, it would create parameters for all of the response parameters exposed by the web service (so if the web service returned Property1, Property2 and a Collection of values, you'd end up with parameters for each of those, mapped to the web service already. Definitely a time saver. Ryan
That's really it - it's not even actually a parameter in itself - It's more of a parameter generator. The point is to have it generate the needed parameters to work with some other process element, saving you the need/time to create them all yourself.