Currently the default list view shows "Recently Viewed" records. Most users expect to see all records they can access and are confused by the default view during their first use of the platform. A similar problem exists with classic. The…
Show more

We do not have any option to include the configuration done in Omni-channel to migrate/deploy to production; not in Change Sets not in Eclipse. This is time consuming since we have to do it manually in production.

The recently announced Winter 08 feature - Inline Editing - is a fantastic advancement for the Salesforce.com user interface. However, it appears that this functionality will only be available for the record detail section when Winter 08 goes live.…
Show more

1. Record locked for approval or locked with trigger lock() method do not have pad lock icon as in classic. This even worse when user allow to click Edit button and only get error when hit Save button. 2. User should not allowed to hit Edit button…
Show more

It could be easier to the user if node positions were stored while managing dataflows through the editor. So that, users could organize nodes in a proper way instead of having the default visualization when opening a created dataflow. This could be…
Show more

Currently the the Lightning Experience UI only allows to display 4 fields on a related list. You would need to click "View All" to see all fields. This is a regressed functionality, given the fact that the same layout in classic version is…
Show more

Currently, only Text Area field type (255 words and under) and inline editable; Long Text Area or Rich Text Area fields are not open to inline editing in the enhanced lists view, however they are inline editiable within the record. I suggest that …
Show more

Now that Mulesoft has been acquired by Salesfforce, would be great if Dataloader.io became the standard import tool for Salesforce and if the monthly 10k limit on dataloader.io was removed to make that the default free import tool for sfdc. Could…
Show more