web
You’re offline. This is a read only version of the page.
close

Enable auditing for Dataverse for Teams database


In an environment of type "Microsoft Teams", auditing should be enabled to enhance security without the need to upgrade to Dataverse database.

Read more...
0 Comments

Read more...
0 Comments

Category: Admin Center (304)

STATUS DETAILS
New

Remove deprecated "auditretentionperiod" attribute when using API call


When using the API call to "/api/data/v9.0/organizations", the value for "auditretentionperiod" does not reflect the audit retention period setting in admin center. However, the value is updated correctly for "auditretentionperiodv2", which can cause confusion to customers. The "auditretention...

Read more...
0 Comments

Read more...
0 Comments

Category: Dataverse (229)

STATUS DETAILS
New

Increase the action limit or optimize the journey so that users are less likely to hit the 500 actions limit


When users design a journey, if it is complex enough, there will be an error when publishing it: "Journey could not be published due to too many actions being present exceeding '500'". It's frustrating as a user to build a journey and have the system say it’s too complex.


It w...

Read more...
1 Comments

Read more...
1 Comments

Category: Journey Design (243)

STATUS DETAILS
Backlog

Allow agents to directly take over bot conversations


Currently, there is no way for agents to directly take over bot conversations. They have to configure a topic with Copilot so that it can help transfer case from bot to agents, but this is a workaround.


It would be great if this feature is implemented to help with customer's o...

Read more...
0 Comments

Read more...
0 Comments

Category: Live Chat (165)

STATUS DETAILS
New

Allow users to apply Field Level Security override to triggers in Real-time marketing


Currently, FLS override is possible for personalization, journey, and segment. However, this is not applicable for triggers yet.


It would be helpful for users if this can be applied to triggers as well.

Read more...
1 Comments

Read more...
1 Comments

Category: Event Triggers (30)

STATUS DETAILS
New

Rename specific labels in Queue dashboard of Omnichannel historical analytics to avoid misleading


Currently, in the Queue dashboard, it is showing data for "Incoming sessions". However, Queue dashboard includes both incoming and outgoing conversations, so the "Incoming sessions" label is misleading.


It would be helpful if the label is renamed so that users can understand m...

Read more...
0 Comments

Read more...
0 Comments

Category: Customer Service Insights – BI Analytics (51)

STATUS DETAILS
New