How the Connectors for ECM work

In a typical process that interacts with an ECM system, a LiveCycle application retrieves a document from the ECM repository and stores content in the repository.

The following example shows a mortgage application that retrieves a form from an ECM repository and stores the final document in the ECM repository.

Here is how the mortgage application works in this example:

  1. A form author or form developer creates the form design in Workbench, as follows:

    • Goes to the ECM content tree within Workbench

    • Searches the ECM content and then uses the drag-and-drop functionality to add images and fragments to the form design

    • Saves the form design in the ECM system

  2. A developer creates the business logic and process for the form. The first step in the process uses a variable that retrieves a form from the ECM repository. Then, the process saves the data in a variable that a user submits from a client application. For example, a user can initiate the process from Workspace and submit the data by clicking a button on the form.

    Based on the amount of the mortgage that the applicant specified, the form data is routed to the appropriate individual for approval. After the form is approved, as part of the last step in the process, the form data is saved in the ECM repository.

// Ethnio survey code removed