Agents can associate and execute post processing workflows on letters. Post process to be executed can be selected in the Properties view of the Letter template. You can set up post processes to email, print, fax, or archive your final letters.
To associate post processes with letters, you first need to set up the post processes. Two types of workflows can be executed on submitted letters:
To authenticate a process/service, copy the name of a process and go back to the Adobe Experience Manager Web Console Configurations page > Adobe LiveCycle Client SDK Configuration and add the process as a new service.
For example, if the drop-down in Properties page of letter displays name of the process as Forms Workflow -> ValidCCPostProcess/SaveXML, add a Service Name as ValidCCPostProcess/SaveXML.
To use LiveCycle workflows for post processing, set up the necessary parameters and outputs. Default values of the parameters are indicated below.
Go to the Adobe Experience Manager Web Console Configurations page > Asset Composer Configurations and set up the following parameters:
- inPDFDoc (PDF document parameter): A PDF document as input. This input contains the rendered letter as input. The parameter names indicated are configurable. They can be configured from Asset Composer configurations from configuration.
- inXMLDoc (XML data parameter): An XML document as input. This input contains data entered by user in the form of XML.
- inXDPDoc (XDP document parameter): An XML document as input. This input contains underlying layout (XDP).
- inAttachmentDocs (Attachment Documents parameter): A list input parameter. This input contains all the attachments as input.
- redirectURL (Redirect URL Output): An output type indicating the url to redirect to.
Your forms workflow must have either PDF document parameter or XML data parameter as input with the same name as specified in Asset Composer Configuration. This is required for the process to be listed in the Post Process dropdown.
If you do not already have the required tag, create a tag named Correspondence_Management under the Standard Tags folder. For more information on creating tags, see Adminstering Tags.
In the Step Properties dialog:
- On the Process tab, select the name of the custom process and check Handler Advance. For more information on creating custom workflow steps, see Developing and Extending Workflows.
- On the Common tab, give a title to the process step.
The workflow you created is now activated and appears in the list of workflows when you try to create a letter in your Correspondence Management implementation with the prefix: AEM Workflow ->.
Your integration of the Letter and the post process is complete. Further, you need to design the post process for the e-mailing. Similarly, you can integrate other workflows and then go on to create the back-end workflows.
For more information on creating AEM Workflows, see then AEM Workbench documentation.
Saved letter instances can be manipulated further, such as retrieval of letter instances and deletion of letter instances, by using the following APIs defined in LetterInstanceService.
|Server-side API||Operation name||Description|
|getLetterInstance||Fetch the specified letter instance|
|Public void deleteLetterInstance(String letterInstanceId) throws ICCException;||deleteLetterInstance||Deleted the specified letter instance|
|List getAllLetterInstances(Query) throws ICCException;||getAllLetterInstances||This API fetches letter instances based on the input query parameter. To fetch all letter instances, query parameter can be passed as null.
|Public Boolean letterInstanceExists(String letterInstanceName) throws ICCException;||letterInstanceExists||Check if a LetterInstance exists by the given name|
A draft letter instance can be reloaded in user interface by using the following url:
LetterInstaceID: The unique ID of the submitted letter instance.
For more information on saving a draft letter, see Saving drafts and submitting letter instances.