This procedure describes how you design an offline form using an XML schema and an Adobe XDP (XML Data Package) file that is bound to the XML schema. With the XML schema, you define the data structure of the form. With the XDP file, you define the form template, that is, the design of the form which is based on the XML schema.
You create the XML schema and the Adobe XDP file in the SAP NetWeaver Developer Studio in a dedicated development component (DC) called Enterprise Content Management (ECM). This ECM DC serves as a repository where you store both the XML schema and the form template. Then you use the XML Schema Editor in the Developer Studio to edit the XML schema and the Adobe LiveCycle Designer to design the form appearance.
Finally, you have to build and deploy the ECM DC to transport its content into a runtime repository and to be able to browse its content and assign the form to a task.
You have the necessary knowledge in designing an XML Schema. For more information, see Creating and Editing XSD Files .
You have the necessary installations to use Adobe Document Services and Adobe forms in processes. For more information, see Using Adobe Offline Forms , Prerequisites .
You have configured the AS Java in the SAP NetWeaver Developer Studio to deploy to. For more information, see Configuring the Application Server in the Developer Studio .
1. Create the ECM Development Component
In the Developer Studio, choose .
Expand the development configuration in which you want to create the DC.
In the context menu of the software component (SC) in which you want to create the DC, choose
.In the dialog that appears, expand Content and choose ECM . Choose the Next pushbutton.
Specify the required information such as the DC name and choose the Finish pushbutton. Choose Yes when prompted to switch to the Resource perspective.
In the Project Explorer view, expand the ECM DC you have created, then expand and open the content.xml for editing.
You have to specify the repository name and the folder in which you want to store the XML schema and the form template and use them at runtime. To do that, enter BPM as the repository name and Forms as the target path in the content.xml file. The result looks as follows:
<?xml version="1.0" encoding="UTF-8"?> <!-- <!DOCTYPE ecm_content SYSTEM "ecm_content.dtd" > --> <ecm_content> <repository name="BPM"> <mass_import content_path="/" target_path="/Forms" /> <!-- delete path="/" /> --> </repository> </ecm_content>
2. Create and Edit the XML Schema
In the Developer Studio, choose .
Expand the XML node and choose XML Schema . Choose the Next pushbutton.
Enter a name for the XSD file and select the content folder in the ECM DC to store the XML schema. Choose the Finish pushbutton.
The XML schema is created and is openedfor editing.
Create the necessary types and elements of the XML schema.
In the context menu of the XSD file, choose Properties and copy the location of the XML schema. You need to know the location of the schema when you create the form template which is based on the schema.
3. Create the Form Template
In the Developer Studio, choose .
Expand the General node and choose File . Choose the Next pushbutton.
Enter a name for the file and .xdp as the file extension.
We recommend that you use the same name for the XDP file and the XML schema, since they are bound together.
Select the content folder in the ECM DC to store the XDP file. Choose the Finish pushbutton.
The form template is created and opens for editing.
If you have copied the XDP file, you have the option to update the licensing information of the form. Otherwise, the licensing information is not correct, since it is the same for the original and the copied form. To do that, from the context menu of the XDP file, choose Update Licensing Information .
In the Adobe LiveCycle Designer, choose
to import the XML schema.In the wizard that appears, select the XML Schema radio button and choose the Next pushbutton.
Provide the location of the XML schema you created and choose the Finish pushbutton.
The data from the XML schema is imported and you can see it in the Data View palette in the Adobe LiveCycle Designer.
4. Design the Form Layout
In the Adobe LiveCycle Designer, drag the elements from the Data View palette to the form template and arrange them in the desired way.
In the Library palette, open the Standard tab page, select Button and drag it to the form template.
Use only the plain Button with the described configuration in form templates for BPM, as the default configuration of the other buttons cannot be modified appropriately.
For more information about which control elements you can use, see SAP Note 1487659 .
Change the control type of the button to Submit . To do that, open the Object palette and then the Field tab page and select the Submit radio button.
On the Submit tab page, select PDF from the Submit Format dropdown list.
You do not need to enter the submit URL because the BPM system prefills it at runtime. For more information about configuring e-mail send options, see Wizard-Based Configuration for Business Process Management .
In the Developer Studio, choose to save the template.
5. Build and Deploy the ECM Development Component
Open the Development Infrastructure perspective and locate the SC in which you have created the ECM DC.
In the context menu of the ECM DC, choose Build and in the dialog that appears, choose the OK pushbutton.
The DC is built successfully if there are no errors.
In the context menu of the ECM DC, choose Deploy and in the dialog that appears, choose the OK pushbutton.
Log on to the AS Java with your credentials, if prompted, to start deploying.
After building and deploying successfully the ECM DC, its content is transported into a runtime repository and you can browse it and use the form in your process. For more information, see Assigning an Offline Form to a Task .