Application save point and last-pages mechanism

Application save point

Application save point is a key element of the form flow in the Eximee system. It defines the moment when the application data is transferred to the form repository and related actions are invoked — such as starting a BPMN process, saving data in an external system, or displaying final informational pages to the user. It is configured in the tab Steps of the application editor and appears as one of the items in the form steps sequence. It is most often placed as the last step of the application. All pages located in the steps below the Application save point are treated as completion pages.

Illustration 1. View of the application save point in the "Steps" tab

When the application passes this point, crossing it causes the application to be saved to the form repository along with all data filled in on it.

Properties of the Application save point step

The step Application save point has the following properties:

• can be in any way moved using the drag & drop mechanism in the steps structure,

• cannot be deleted, because it constitutes an integral element of the template,

• you cannot place pages in it – it serves a technical function, not a visual one.

Configuration of the application save point

At the moment of crossing the save point the system performs a data save action. If a BPMN process should be started at that moment, add the element in the Application save point section EximeeRouter2.

Configuration of this element includes:

• Process name – the key of the BPMN process definition (matching the process identifier in EximeeBPMS).

• Case number (Business key) – the business identifier of the application. It may point to a form component or a session variable containing a unique case number. If the field is not filled in, the system will automatically use the application number as the business key.

Illustration 2. View of the application save point with an attached EximeeRouter2 process

Example XML configuration in the The number of page columns can be changed after creating the form by editing its definition. In the application edit mode go to the form tab:

<saveActions>
  <action xsi:type="eximeeWorkflow">
    <processDefinitionKey>process_name</processDefinitionKey>
    <businessKeyMapping>case_number</businessKeyMapping>
  </action>
</saveActions>

Setting these parameters causes that after passing the application save point the system:

1. Saves the form data to the repository (FormStore),

2. Initiates a BPMN process in the engine EximeeBPMS,

3. Passes the form data to the process according to the mapping in the Data model.

Last pages mechanism

After passing the application save point the system displays so-called final pages of the application – final screens visible after submitting the form. If there are no completion pages, the system automatically presents a standard thank-you page defined at the Forms application level.

Completion pages can be used to:

• present a confirmation message confirming the submission of the application (e.g. thank you, reference number),

• provide information about the further course of the process,

• invoke additional services or validators.

Characteristics of final pages:

• data from completion pages are not saved in the repository together with data collected from full-featured application pages,

• components on completion pages operate like regular components, they can perform validations, call services, or display dictionary data,

• after submitting the application and moving to the completion pages the user cannot return to previous pages,

• there is no possibility to park the application after its submission,

• after passing through the completion pages the application does not go to the pool of abandoned applications,

• completion steps behave similarly to regular steps and we can define their basic properties according to the manual.

Defining application final pages

The process of creating final pages is analogous to defining regular form pages. The only difference is their placement – they must be placed in the step below the Application save point.

The illustration below shows the steps of an example application template. This template has:

• three application pages placed in steps Step1 and Step2

• Application save point defining the location of the thank-you page,

• one completion page located in the step Step3.

Illustration 3. Example steps with a thank-you page

All pages placed in steps located below the Application save point are treated as completion pages.