Hiding Buttons on View Redlines Page
The View Redlines user interface in Conga Contracts for Salesforce has several actions available by default. Any of these buttons, except for Compare, can be hidden from the View Redlines page using URL parameters. The following is a full list of actions you can hide:
| Parameter | Type | Description |
|---|---|---|
| altId | String | Record ID — used when no Standard Controller record is available (generic page load) |
| disableOpenInWord | String (true/false) | Hides the "Open in Word" button |
| disableTrueUp | String (true/false) | Hides the "True Up" button |
| disableTrueUpAll |
String (true/false) | Hides the "True Up All" button |
| disableNegotiate | String (true/false) | Hides the "Negotiate" button |
| disableSavePdf | String (true/false) | Hides the "Save as PDF" button |
| disableSendWithCongaSign | String (true/false) | Hides the "Send with Conga Sign" button |
| enableRecursiveMergeSync | String (true/false) | Enables recursive merge sync behaviour |
| locale | String | Overrides the locale for the page (e.g.
en_US) example : locale=TEXT($User.LocaleSidKey) |
Create Custom View Redlines Button
Changing the parameter value to False will allow that button to show in the View Redlines interface. Alternatively, you can remove the parameter entirely. Omitting a parameter from the URL syntax provides that same functionality as using =false.
Use Case for Sales Users
BlueCube, Inc. wants Legal Users to have full access to the View Redlines interface but Sales Users to only be able to Compare versions. To accomplish this, BlueCube will create two custom View Redlines buttons:
In this example, the Sales User button will be:
{!URLFOR($Action.Contract.APXT_Redlining__View_Redlines, null, [altId=APXT_Redlining__Contract_Agreement__c.Id, disableOpenInWord=true, disableNegotiate=true, disableTrueUp=true, disableSavePDF=true, disableSendwithCongaSign=true], false)}
The Legal User button will be:
{!URLFOR($Action.Contract.APXT_Redlining__View_Redlines, null, [altId=APXT_Redlining__Contract_Agreement__c.Id], false)}
Once the buttons are created BlueCube will use Salesforce functionality, preferably Dynamic Actions on a Lightning Page, to show/hide the proper buttons to Users.