8 October 2012
This article discusses some of the best practices for creating LiveCycle processes using Adobe LiveCycle Workbench. It does not apply to a particular version of Workbench and should not be considered as a step-by-step guide for creating LiveCycle processes, but it represents general practices to improve and standardize practices. Before implementing these best practices, ensure that they fit into your overall strategy for designing LiveCycle processes and align with your organizational needs.
Defining best practices and molding them into usual procedure is an on-going activity as individuals and teams gain experience with creating LiveCycle processes.
An important aspect of any LiveCycle process is its design and layout. Ideally, a process should be uncluttered, logically laid out, and easy to implement and understand:
Another important aspect of standardizing processes while creating LiveCycle processes is to follow a naming convention. Naming conventions are usually specific to one's organization, and therefore should be defined keeping the requirements and policies in mind before the development of LiveCycle processes begins.
The optimal performance of processes, sub-processes, and applications reduces the resource utilization, computational time, and prevents applications from entering into stalled state.
Here are some best practices for increasing the performance of the LiveCycle processes:
Here are some best practices for coding:
/process_data/dataXML/CandidateDataCaptureForm/dataCapture/pmiData/pmiForSelf = “1” or /process_data/dataXML/CandidateDataCaptureForm/dataCapture/pmiData/pmiForSelf = 1
number(/process_data/dataXML/CandidateDataCaptureForm/dataCapture/pmiData/pmiForSelf) = 1
Consistency and completeness among all the processes makes processes understandable, improves performance, and reduces the clutter in the code.
Here is the checklist to ensure consistency and completeness among LiveCycle processes:
We have discussed, in brief, the best practices for creating LiveCycle Workbench processes.
Although the documentation should answer most of your questions, feel free to initiate and participate in discussions.