Configure Form Bundles

   Journey Manager (JM) The transaction engine for the platform. |   System Manager / DevOps |  All versions This feature is related to all versions.

Manager allows you to configure form bundles using the following pre-defined set of job definition elements that are part of step and action attributes or properties.

Step Attributes For Form Bundles with More Than Two Tasks

Note

The following are ignored if there is only one task in a step.

dynamicPreConditions -re-evaluates action preconditions for forms with the multiple step, if set to true. Otherwise, they are only evaluated on the triage form.

shareFormData - copies the entire form XML data between form tasks within a form bundle step.

shareExtractData - copies data between form tasks within a form bundle step using a publish subscribe method.

allFormsEditable - if set to true, the form tasks within a form bundle are mutable, until the step is completed.

Step Attributes For Form Bundles with One or More Tasks

showPreviousForms - shows the previous forms.

redirectNext - allows form chaining along with the action attribute redirect next.

Step Properties

This is used to specify the triage step and is only required if triage form is not the start form.

"properties": [
    {"name": "Pre Condition Submission Step", "value" : "Triage Step Name"}
  ],

Action Properties

preCondition - allows you to use the Apache velocity templatesApache Velocity Templates are used extensively throughout Temenos Journey Manager platformto define html page layout, email body and subject. A template is combined with model containing a number or objects to produce a String. For more information see http://velocity.apache.org/engine/devel/user-guide.html.

redirectNext - allows form chaining along with the step attribute redirect next.

Next, learn about anonymous Form Bundles.