-
Ability to enable advance find for entities based on the security role
Suggested by BILU BABU – Completed – 11 Comments
Currently there is no way to control the security for advance find entities and all users having any read level access can see the enties in advance find. From a solutioning point of view, read level access would be required to be provided for certain roles, but those roles should not be able to search the entity in the advance find.
Field level security is an option but difficult to maintain if there are lot of fields and roles.
It is a suggestion that this kind of security settings will enhance the current security architecture of dynamics CRM and from a security role perspective, we should be able to define which entities can be enabled for advance find for a particular security role. -
Possibility to set the default font for email per user
Suggested by Helena Blücher – Completed – 13 Comments
It would be great to be able to set default fonts and font sizes for composed emails in Dynamics for each user. Eg on their personal settings. It would also be great to be able to set the default font and font size for composed emails on the system settings. -
Add a button to insert KB articles in email replies
Suggested by Michael Stavrou – Completed – 1 Comments
Right now I need to locate the article independently and then click on email it from the case. However this loses track of the original email. I'd like to have a button where I can insert a KB article on an email reply. We have buttons for email templates and signatures which are both old school, why not have one for the new KBs? This saves agents time and it also allows them to add multiple KB articles to the same email response if needed.
-
Enable user to customize 'Conversation' entity
Suggested by Dafid Margetha – Completed – 2 Comments
Enable user to customize 'Conversation' entity. There are a lot of business industry in real world, for example: automotive, banking, insurance, healthcare, etc. The problem is, on current environment, Conversation entity cannot be customized. And Agent need to check related information from selected Account or Contact. For example on Automotive industry: When agent select Account or Contact, and Agent need to know their related Vehicle so agent can actively give information to the customer. For Insurance industry: When agent select Account or Contact, Agent can see their Insurance Policy. With this idea, agent can focus on the same screen without need to open new tab. You can imagine if one agent handle 5 customer at one time, s/he need to open up to 10 screen to handle the chat to get the related records. Also agent can start and finish all task on one screen only. -
Mail Editor- best in-class required/Outlook like
Suggested by Marc Bertauts – Completed – 2 Comments
***9.1- CK Editor VERSION missing features to optimize user experience*** Context reminder: lot of communications done with customers/external partners/internal partners is done via Mail to keep trace of service request for traceability/auditability/compliance…therefore Mail communication in a case context is FOUNDATIONAL. MSFT TARGET should be the MSOffice Word/Outlook rich text editor features >>Main features missing for 9.1: -Ability to copy/paste an Excel table directly (simple Ctl+C/Ctl+V) and keep formatting -Ability to copy a Word or other MSOffice source (Outlook) formatted text (containing -images, table, bullets, links…) directly (simple Ctl+C/Ctl+V) and keep formatting -Ability to copy an image directly and enable resizing -Also Enable internal images/stop current encoding and take image as an image file -Enable hyperlink to open browser session, public or internal HP sites -Ability to choose/configure mail default font at system/user level -Implement language spelling check -Enable HP Fonts -Enable resizing of tables and images by dragging on the borders/corners instead of having to go through menus -Ability to drag & drop/copy-paste files to attach within email sending -Implement language Spelling check
-
Email to Case Process Needs to Run when the Queue is BCC'd
Suggested by Jim Corriveau – Completed – 5 Comments
Currently, when a Queue email address is BCC'd Server Side Sync creates the message in CRM but the Email To Case Process fails to run. The Email To Case Process must run on emails where the Queue email address is in the BCC. This can be done by correcting the Email To Case Process or having SSS put the Queue email address in the TO or CC fields when the email is created in CRM. It does not matter how it is fixed as long as BCC'd email address are treated the same as a TO or CC email address. Thanks, Jim
-
Ability to change the chat widget's background
Suggested by Nuno Galvão – Completed – 1 Comments
We would like to be able to change the colors of different elements from the chat widget, most importantly the background. -
Customize proactive chat popup text
Suggested by Anthony Fuentes – Completed – 11 Comments
When the proactive chat shows, the top half of the popup says "Welcome to Live chat support!". I would like to be able to customize that text. -
Ability to link conversations to leads
Suggested by Oscar Monrio de la Herran – Completed – 4 Comments
Currently it is only possible to link conversations to contact, account and case records. As part of our business process, we need to link conversations also to leads in order been able to migrate from our actual solution. Thanks -
Configuration setting to set default language for Knowledge Article
Suggested by Rafael Urbano – Completed – 4 Comments
Surprisingly enough the default organisation/environment language is not used when configuring new Knowledge Articles. Instead "English - United States" is selected by default. The product team should strongly consider changing that behaviour so it matches the default language set at the organisation level or provide a configuration setting to allow customers defining their preferred default language for Knowledge Articles. Changing that attribute each time someone is creating a new KB record is annoying and time consuming. Typically KB administrators forget about it so they need to manually translate each KB record to their preferred/required language after the fact which is even less enjoyable.