Step by Step to create an Adobe Print form in Cloud application Studio
My series of Cloud Application Studio Blogs
- How to detect EditMode in an Embedded Component
- Step by step to enable your custom BO with attachment upload functionality
- Step by step to create an Adobe Print form in Cloud application Studio
- How to render PDF which displays picture from the image attachment of your custom BO
- How to get current logged on business user’s employee information and assigned organization unit via ABSL
- How to implement dynamic access control based on custom BO using OWL
- How to make Code List Restriction work when control field and restricted field are not on the same BO
- How to implement custom number range using custom business object
- Two approaches to create Code List in Cloud Studio
- Create Dynamic Code List via Custom Business Object Association
- Step by step to develop Thing Type based navigation and BO Object based navigation
- Put Extension field into embedded component and make it visible in Standard UI
- One possible cause that embedded component fails to display in UI
- Step by step to create HTML Mashup and make it visible in UI
- Step by step to enable Text Collection for your custom BO
- Automatically send an Email notification to line manager via Workflow in Account application
- Step by step to create Object Value Selector in Cloud Application Studio
- Two approaches to fill an UI field with dedicated logic implemented in Cloud Application Studio
- How to execute BO action on multiple selected BO instances in AdvancedListPane
The Adobe Print form must be created based on a BO. In this blog I will use the BO explained in this blog: Step by step to enable your custom BO with attachment upload functionality.
1. Create a new Print Form via context menu. A new form group and form template header must be created by following the creation wizard.
Below is an example of Form Group code whose technical value will be used later.
Below is the screenshot of Form Template Header:
2. Double click .xdp file under Form Template Header to launch Adobe Form Designer. If you have not installed it yet, download from here:
Design your layout in Adobe Form Designer, bind the BO field to the form element in Object tab. In the runtime, the bound field will display the corresponding value of BO instance.
Once finished, check in change from context menu and activate the change.
3. Go to Thing inspector UI where you could like to add the preview button, create a new Data field in Controller tab:
Create a new Output named PreviewOutput, and create two Parameters named “GroupCode” and “ForceFrontendPreview”. The corresponding parameter could be found below.
Create a model Dialog using the reusable UI whose path highlighted below. Bind the Root node of current model to NodeReferenceBinding.
Switch to Navigation Configuration tab of selected Modal Dialog, bind the created outport before of our TI with the standard inport InPreview of Reusable UI. Bind their parameters as well.
Create a new event handler to fire the created outport:
As the last step of UI creation, create a new preview button and assign the previewHandler event handler to its onClick event.
4. Deploy Business Configuration of your solution. You should see successful message before you test the form preview in the runtime.
Now go to your TI and press Preview button:
Form is previewed successfully: