Agents can associate and execute post processing workflows on letters and intreactive communications. 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 or interactive communications, you first need to set up the post processes. Two types of workflows can be executed on submitted letters:
Forms Workflow: These are the AEM Forms on JEE process management workflows. Instructions for setting up Forms Workflow.
AEM Workflow: AEM workflows can also be used as post processes for submitted letters. Instructions for setting up AEM Workflow.
In AEM, open Adobe Experience Manager Web Console Configuration for your server using the following URL:
On this page, locate AEM Forms Client SDK Configuration and expand it by clicking it.
In Server URL, enter the name of your AEM Forms on JEE server, login details, and then click Save.
Specify the username and password.
Ensure that sun.util.calendar is added to Deserialization Firewall Configuration.
Go to Deserialization Firewall Configuration and under Allowlisted classes of package prefixes, add sun.util.calendar.
Now your servers are mapped and the post processes in AEM Forms on JEE are available in the AEM user interface while creating letters.
To authenticate a process/service, copy the name of a process and go back to the Adobe Experience Manager Web Console Configurations page > AEM Forms 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
To use AEM Forms on JEE 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 > Correspondence Management Configurations and set up the following parameters:
Your forms workflow must have either PDF document parameter or XML data parameter as input with the same name as specified in Correspondence Management Configurations. This is required for the process to be listed in the Post Process dropdown.
While using either Forms or AEM workflows, before you make any submission from the publish server, it is necessary to configure the DS settings service. Otherwise, the Form submission shall fail.
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|
In the CCR user interface, complete the following steps to associate a post process with a letter:
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.