Considerations for Process Adaptations for Print Action
Configure business process adaptations in Visual Studio Code-based Modeler to generate
PDF reports in the Consumer Goods offline mobile app. In the
MyDisplay_DisplayDetailsProcess.processflow.xml contract, create an event handler to handle the
printPDF event. Next, trigger the PrintV2 action on the Display module of the app to generate the
PDF reports. Lastly, test the results on a mobile device.
Required Editions
Available in: Professional, Enterprise, and Unlimited Editions
that have Consumer Goods Cloud enabled
Some backend processes are triggered when a sales rep taps a button to generate PDF reports in
the Consumer Goods offline mobile app.
View
The new menu creates an event that ensures sales reps view the
button to generate the PDF report on the app UI. The display process handles the event and the
event’s visibility is bound to a business object method.
Controller
The controller handles the print action and calls the method
to print the PDF report.
Model
The model determines the business objects and the business methods
and invokes the framework method to print the PDF report.
Configure the Event Handler Create an event handler in the MyDisplay_DisplayDetailsProcess.processflow.xml contract to handle the print PDF event. An event handler is a callback routine that dictates the action that follows an event. For example, to see a PDF report, a sales rep taps the Print PDF button on the Consumer Goods offline app. Here, the button-tapping action is an event, and the generation of PDF report is an event handler.
Configure the PrintV2 Action Create an action named PrintV2 in the MyDisplay_DisplayDetailsProcess.processflow.xml contract to trigger PDF report generation in the Consumer Goods offline mobile app.
Did this article solve your issue?
Let us know so we can improve!
Loading
Salesforce Help | Article
Cookie Consent Manager
General Information
Required Cookies
Functional Cookies
Advertising Cookies
General Information
We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required Cookies
Always Active
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional Cookies
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising Cookies
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.