The mapping IN mechanism in SalesForce1 works in the same way as in Force.com. The way to trigger the mapping IN is different though: instead of switching from the ‘Overview’ tab to the ‘Content’ or to the ‘Proposal’ tab, you have to use chatter actions from the PROS quote entity in SalesForce1.

For example, QuoteModel_TouchTablet is alright, while QuoteModelTooLong_TouchTablet is not.

For instance, the mapping IN is run when using the “Quote Content” chatter action from the PROS Quote object:

It also intervenes when using the ‘Proposal’ chatter action, for example:

In SalesForce1, the Save and Close button (calling

the DelegateCloseSpreadsheetActionForceCom delegate class) should not be used in the UI design.

In Salesforce1, the synchronization process is under the responsibility of the Force.com environment. Thus, you have to use the Force.com Submit button instead.

The mapping OUT mechanism in SalesForce1 works in the same way as in Force.com. The way to trigger the mapping OUT is different though: instead of switching from the ‘Content’ or the ‘Proposal’ tab to the ‘Overview’ tab, you have to use buttons or links to go back to the PROS quote in SF1.

When the quote in CPQ is called from SalesForce1, the layout and the model files used have the names of the web interface files, suffixed with “_TouchTablet”.

In the Proposal or in the Quote content interfaces, when the user clicks on the

Force.com Submit button, he is redirected on the PROS Quote object in Force.com where the entity is updated with regards to the mapping OUT mechanism.

In SalesForce1, the Save and Close button (calling

the DelegateCloseSpreadsheetActionForceCom delegate class) should not be used in the UI design.

In Salesforce1, the synchronization process is under the responsibility of the Force.com environment. Thus, you have to use the Force.com Submit button instead.

For instance from the Quote Content interface:

It also intervenes from the Proposal interface, for example: