
You use this procedure to create a schema-based composite form object that utilizes a pre-filling service for retrieval of the current user's details. The form is configured as a step in Guided Procedures (GP) and has dynamic properties.
You have created a pre-filling service as described in Configuring Pre-Filling Services .
In this example, we use the local Java persistence to store the template. For this purpose, you should first configure the Java back end and its connection to the Adobe Document Services.
More information: Configuring Forms with Java Back End
Browse the folders in the gallery to locate the Read User Info callable object you created previously.
More information: Configuring Pre-Filling Services
On the Build Form Context tab page, select the parameters User Data and Unique ID from the pre-filling service and add them to the form context.
You do not need to map service input parameters, since the Read User Info callable object uses the current user details as input. However, you must map the output parameters so that the form receives as input the data from the pre-filling service.
On the Map Output Parameters tab page, map the following output parameters:
Mapping Service Output Parameters
Additional Form Context Parameters
| Context Parameter | Technical Name | Type |
|---|---|---|
|
Medical Services |
medical |
String |
|
Education Assistance |
education |
String |
|
Dependent Care |
dependent |
String |
|
Unemployment Insurance |
unemployment |
String |
|
Retirement Account |
pension |
String |
|
Date |
date |
Date |
|
Comment |
comment |
String |
You use these parameters in the next step, where you design the layout of the schema-based form template.
More information: Designing the Form Template Layout
Once you have created the form object, you can expose it as a callable object and include it in the GP process flow.
More information: Modeling the Composite Form Activity