What is a one sentence summary of your feature request?
The Save and Cancel buttons on the Change Request page are hidden behind Salesforce’s bottom navigation bar when users access the page from Sales Console or Service Console, causing unsaved changes and compliance issues.
Please describe your idea in detail. What is your problem, why do you feel this idea is the best solution, etc.
hen users open and manage Change Requests from Salesforce Sales Console or Service Console, the Save and Cancel action buttons are rendered below the visible area of the page. This happens because Salesforce adds a fixed bottom navigation bar in console-based apps that overlaps the action container where the Save and Cancel buttons are placed. As a result, users complete their selections (adding Customizations or Proposed Customizations), click Confirm Selection, and then navigate away without realizing the Save button exists but is out of view. This causes all selected customizations to be lost silently. The issue is inconsistent — some users can partially see the top of the Save button while others cannot see it at all — making it unpredictable and difficult to detect. The current workaround requires users to open Change Requests exclusively from the Netwrix Lightning app, but in practice most users work from their standard Salesforce console apps.
How do you currently solve the challenges you have by not having this feature?
We use the Netwrix Lightning app as a workaround, but this requires users to switch apps every time they need to manage a Change Request. In practice, many users are unaware of this requirement and continue working from their usual console app, resulting in lost customization selections and Change Requests being approved with blank changes, which then appear as non-compliant.