AEM Forms provides custom workflows to invoke the following Assembler service APIs:
The Invoke DDX workflow invokes the Invoke
Assembler service API, which you can use to assemble or disassemble documents, add watermark to a PDF, and so on.
The Invoke DDX workflow requires the following input documents:
DDX: It is a mandatory input for the Invoke DDX workflow step and can be specified by selecting one of the following options from the DDX input drop-down.
Create Map from PayLoad: When selected, all documents under the payload folder are added to Input Document’s Map for the invoke
API in Assembler. The node name for each document is used as a key in the map.
Input Document’s Map: Specifies the Input Document’s Map. You can add any number of entries, where each entry specifies the document’s key in the map and the source of the document.
The Environment Options tab lets you set various processing options for the invoke API.
Job Log Level: Specifies the log level for the processing logs.
Validate Only: Checks the validity of the input DDX.
Fail On Error: Specifies whether the call to Assembler service should fail if there is an error. The default value is False.
Depending on the input DDX, the invoke API can produce multiple output documents. The Output Documents tab lets you select where output document will be saved.
Save Output in Payload: Saves output documents under the payload folder, or overwrites the payload, if payload is a file.
Output Document’s Map: Lets you explicitly specify where to save each output document by adding one entry per output document. Each entry specifies the document and where to save it. An output document can overwrite the payload or saved under the payload folder. It is useful when there are multiple output documents.
Job Log: Specifies where to save the job log document, which is helpful in troubleshooting failures.
The Convert to PDF/A workflow step invokes the toPDFA
Assembler service API. It is used for converting PDF documents to PDF/A compliant documents.
Drag the ConvertToPDFA workflow step under the Forms Workflow tab in Sidekick.
Double-click the added workflow step to edit the component.
In the Edit component dialog, configure input documents, conversion options, and output documents, and click OK.
Specify the source of the document to convert to a PDF/A compliant document in one of the following ways.
Conversion Options let you specify options that alter the process of PDF/A conversion.
Compliance : Specifies the PDF/A standard to which the output PDF/A must comply.
Result Level : Specifies the log level to be used for PDF/A conversion logs.
Signatures : Specifies how the signatures in input document must be processed during conversion.
Color Space : Specifies the predefined color space to be used for output PDF/A document.
Verify Conversion: Specifies whether the converted PDF/A document should be verified for PDF/A compliance after conversion.
Job Log Level : Specifies the log level to be used for processing logs.
Metadata Extension Schema : Specifies the path to the metadata extension schema to be used for XMP properties in PDF document’s metadata.
The Output Documents tab lets you specify the destination for the output documents
The Render PDF Form workflow is a wrapper around renderPDFForm
Forms service API to create a PDF form using an XDP template and data xml.
Template File: Specifies the location of the XDP template. It is a mandatory field.
Data Document: Specifies the location of data xml that needs to be merged with the template.
The Generate Non Interactive PDF Workflow is a wrapper around generatePDFOutput
Output service API. It is used to generate non-interactive PDF documents from XDP template and data xml.
Template File: Specifies the location of the XDP template. It is a mandatory field.
Data Document: Specifies the location of the data xml that needs to be merged with the template.
Output Document: Specifies the name of the generated PDF form.