LOUIS-ALAIN FILIATRAULT CGI CRM Solution Architect

If you select a product bundle that includes X products, the association between each product and the bundle is stored in the "Parent Bundle" field that only contains the GUID of the bundle.

There is a "Parent Bundle Product" field which is a lookup but it is empty.

It would need to function properly and store the parent bundle in order to be able to configure views, advanced finds and other reporting by bundle or report product sales by bundle or outside a bundle via this lookup field.

Have option in "Up Next" widget control in form designer to hide "Mark complete" button.

In some cases, "Mark complete" closes the sequence activity the wrong way.

For example, an email would be closed with a "Completed" status reason rather than "Sent".

Alternately, the "Mark complete" function could be enhanced to handle each activity type correctly.

• If phone call, ask for status reason
• If email, prompt to confirm and send
• If task, just close as "Completed"
• etc

Currently the option to Merge leads is only available if duplicate detection is triggers and the "View Duplicates" button is displayed.

The Merge button is only offered within the "View Duplicates" dialog.

A "Merge" button should be available when 2 or more leads are selected the same way it is offered when 2 or more accounts are selected.

Improve Phone Call activity closure

• In "New look" interface, make dialog box big enough that we don't need to scroll to see Status Reason under Status
• Validate between Status Reason and Call Direction - you shouldn't be able to say a call is Completed/Made for an incoming call or that a call is Completed/Received for an outgoing call
• Offer OOB "Left Voicemail" status reason to replace "Left Voicemail" boolean

The "Master ID" lookup column is locked from modification.

• It is not possible to make it searchable to views (e.g. making a "Merged Accounts" view)
• It is not possible to add it to a view
• It is not possible to add it to a form. There is a "Merged" Yes/No column that you can add to views and forms but it begs the question "Ok it's merged, but to what record??"
• It is not possible to add a Related associated view based on the "lead_master_lead" relationship

For the sake of traceability, we need the user to be able to easily see where lead xyz went to if it got merged out and if a lead contains merged leads.

Values set in Choice-type column have a Description field.

This field does not seems to be used but could be used in model-driven apps and canvas apps to provide a tooltip explaining what a given choice represents.

This would be useful for fields where a tooltip could guide to new employees to use the appropriate value for a given record.

For example, when select something like a case type or a lead type, if the user is not sure what value to set, they can try a value and hover over the field to see the tooltip to help confirm that they have selected the appropriate type for the record.