Mobile Integration
Smart CPQ can be accessed from any mobile devices (phones or tablets) from the Salesforce mobile app.
PROS recommends first reviewing Salesforce’s approach to mobility as of the Summer Release 2020 here.
It is possible to define a specific quote model, layout and theme for mobile devices.
Mapping IN - Salesforce to CPQ
The Managed Package is able to detect the type of device being used. All you need to do is define additional quote models, layouts, and services.
In the default installation, the device type will either be "desktop" or "mobile" (tablets and phones alike).
A parameter in Custom Settings named Enable Moble-specific Experience allows you to have distinct experiences for phones and tablets.
In the case of a mobile device, the quote model and layout to be used are the regular ones appended with _TouchTablet (or _TouchPhone if the device is a phone and the custom setting has been enabled)
Touchtablet/TouchPhone usage :
| SALESFORCE CRM AND COMMUNITIES–ACCESS VIA BROWSER | SALESFORCE CRM AND COMMUNITIES – ACCESS VIA SF1 | |
|---|---|---|
| Desktop | Desktop UI | Desktop UI |
| Tablets (other than Ipad) | Access not possible | _TouchTablet |
| Ipad | Desktop UI | _TouchTablet |
| Phone | Access not possible | _TouchPhone |
Example: Your custom settings are targeting a quote model myCPQModel and a layout myCPQLayout.xml. When accessing Smart CPQ from a
tablet myCPQModel_TouchTablet and myCPQLayout_TouchTablet.xml will respectively be used.
In addition, the catalog and configuration services used will also be different. If your quote model targets a HTK_CAT service, then the service being targeted (from cameleon.services) when using a mobile device will be:
- service_TouchTablet.HTK_CAT.xmlLayoutURI for a tablet
- service_TouchPhone.HTK_CAT.xmlLayoutUR for a phone
If the specific service isn't found, then the default service (service.HTK_CAT) will be looked for.
- In classic it is the usual Overview/Content tabs
- In lightning you will see a Content buttonWarning: If you chose to define a different quote model when using a mobile device, please note that the following scenario should be anticipated:
User creates a quote with a phone device: myQuoteModel_TouchTablet model is used. User saves the quote and leaves.
User (same or another) reopens the quote from a computer: myQuoteModel is used to open the quote.
We are indeed capable to retrieve all previous values of the quote, assuming that both quote models use the same fields / columns and the same DB column mapping. If not, errors will occur.
Different quote models should limit to different users rights, layout, and/or different formulas.
Note: When using a specific theme for a mobile device, if the theme was created from a desktop theme, it is possible that the iframe displaying Smart CPQ will be poorly rendered because it will be way too large.In that case, to address the issue it is possible to define a static resource that will allow resizing the iframe. Please follow these instructions to do so.
By defining a static resource in the SFDC environment (name = CPQQuote_Content (this name has to be used to be taken into account)) containing a CSS file named CPQQuote_Content.css, the rule inside this CSS file will be applied.
Note: For more details on the mapping IN mechanism, please refer to the CPQ content parameterization (basic) chapter.
Mapping OUT
The mapping OUT mechanism in SalesForce1 works in the same way as in Force.com.
In classic it is the usual Overview/Content tabs. In lightning you will use a Close button.
Both actions will direct you back to the Quote object.