Hello,

The fix behind this UseOptimizedSchemaOperationRightLevelSelect key is present out-of-the-box in 8.0.0 version. So please upgrade the application to 8.0.0 for the fix to be applied automatically in your application.

Hello,

Yes, it is possible to fetch the conversation history related to a Case through the API. However, the conversation history is not stored directly within the Case module. Instead, this data is maintained in a separate Activity table.

Each entry in the Activity table - such as emails, calls, notes, or messages - is linked to a Case via a foreign key relationship. This means that each activity record includes a reference to the specific Case it belongs to.

To retrieve the conversation history for a particular Case, you will need to use the API to query the Activity table and filter the results based on the Case’s ID. This will return all the related communication entries tied to that Case.

Creatio supports the OData protocol, which enables structured querying through parameters. OData is a standardized, REST-based protocol that allows for the querying and manipulation of data using simple HTTP messages and URIs, enabling seamless integration between data sources and clients.

To filter records, you can use the $filter parameter along with the eq (equals) operator.  For example :

https://mycreatio.com/0/odata/Collection1?$filter=Field2 eq 'Field2Value'

This allows you to request a filtered collection of Activity records where the Case reference matches a specific value.

You can find more detailed guidance in the official Creatio OData API documentation.

Hello, 

To design the stages panel in Freedom UI please refer to following link: 

https://academy.creatio.com/docs/8.x/no-code-customization/category/case-designer-workflows

Thank you for reaching out!

This is possible, but only from the context of the page itself. I am not sure if it's possible from a sidebar to know anything about the current page loaded elsewhere, maybe with a request handler in a remote module where you can specify the scopes?

As for getting this info within the context of the page, to get the primary data source, you can use: 

const pds = await request.$context.getPrimaryModelName();

With the data source name, you can get the schema for the datasource which will give you the entity/object name, the Id column attribute, and also the primary display value attribute using the following (note, this gets the attribute names, not the values): 

const pds = await request.$context.getPrimaryModelName();
const schema = await request.$context.dataSchemas[pds];
 
const entityName = await schema.name;
const idColumn = await schema.primaryAttributeName;
const nameColumn = await schema.primaryDisplayAttributeName;

Now that you have the attribute names, you can get the values: 

const idValue = await request.$context[idColumn];
const nameValue = await request.$context[nameColumn];
// etc

This sort of thing works great if you have a custom base page type that could be used for many different pages/objects. 

Also, as a FYI, not sure how this is going to change after 8.2.3 since 8.2.3 has a beta feature (not enabled out of the box) that allows a page to have multiple connected data sources. That might break some of this.

Ryan

Hi!

This behavior may indicate that the access permissions for reading emails from the mailbox are not fully configured.

We recommend reviewing this article and adjusting the permissions to ensure that all users working with cases can read the emails.

Please note that after making changes to the mailbox settings, the new rules will apply only to emails received afterward.

Best regards,

Kate

Hello,

Please provide a screenshot of your business process, along with settings of the element that updates the name.

Dymytriy Vykhodets,

This is business process - 

It runs every time an email message is added. After waiting for five seconds, it reads the "From" and "Contact" fields from the activity section. Then, using a script task, it extracts the name from the "From" field and sets it as the full name of the contact.

Darshan Dev Prajapat,

Please also provide the screenshot of the settings of the element that updates the name.

Mira Dmitruk,

You mean this 


After getting resultname from here i am setting full name of contact in set full name.

Any update on this?

Hello,

The problem is that the "Message type" column is no longer used in the new synchronization mechanism. We don't have a column property on the Activity that indicates whether it is an incoming or outgoing email.

This column is not populated by default. The logic that would fill this field does not currently exist in the system.

However, there is a way to determine this through additional filtering. When an email is synchronized, a record is created in the EmailMessageData table, which specifies the mailbox that synchronized the email. Based on this mailbox, the role of the email can be determined.

For example, if you synchronize the mailbox example@mail.com, then if this mailbox is in the "From" field, the role of the email will also be "From". If it is in the "To/CC/BCC" fields, the role of the email will correspondingly be "To/CC/BCC". Thus, you need to build a filter based on the relationships in EmailMessageData, where Role = From. In this case, you will filter for emails that were sent.


Additionally, you can configure a business process that will read the Role column of the EmailMessageData table for incoming/outgoing emails and, based on the Role field, set the Message type for the Activity record.

Best regards,
Pavlo!

Hello, 

Its working. I tried business process approach and its working fine.

Thanks

Hello,
 

At the moment, the Message Composer element is not customizable in the system. We recognize that this limitation may affect your workflow and the flexibility you need to tailor the system to your specific business requirements.
 

That being said, we want to assure you that we are actively working toward enhancing this functionality. Based on the feedback we've received from you and other users, we've increased the priority of this task.

Your experience and satisfaction with the product are very important to us. We constantly strive to make Creatio more adaptable and user-friendly, and your feedback plays a key role in guiding these improvements

Thank you for your patience and understanding.