Authenticated Form Bundles

   Journey Manager (JM) Previously known as Transact Manager (TM). |   System Manager / DevOps |  v5.1 & Higher This feature is related to v5.1 and higher.

You can enforce an authenticated access to form bundles by using authenticated tasks that are assigned to a group. Authenticated form bundles can be built based on a form and Review Tasks types. However, we recommend you use the Form Task types.

Authenticated tasks can be one of the following:

User Task

The current user is assigned to a new task:

{"name": "Task Assign User", "value": "$func.startUser()" }

Alternatively

{"name": "Task Assign User", "value": "$func.previousUser()" }

Non Claimable Tasks

This task is assigned to a group the current user belongs to, for example, the accounts group:

{"name": "Task Assign Group", "value": "accounts" }

It can be assigned to two groups, if there is a supervisor group for the task:

{"name": "Task Assign Groups", "value": "accounts,supervisor" }

Claimable Group Tasks

This is also required to be claimed by the current user, which is required for the redirectNext to work:

{"name": "Task Assign User", "value": "$func.startUser()" }

{"name": "Task Assign Group", "value": "accounts" }

If there is a supervisor group for the task:

{"name": "Task Assign User", "value": "$func.previousUser()" }

{"name": "Task Assign Groups", "value": "accounts,supervisor" }

Note

A hard-coded address is not recommended.

Job Definition - Additional Products

The job definition for additional products shows the form bundle configuration below:

{
	"name": "Additional Products",
	"type": "",
	"dynanicPreConditions": true,
	"shareExtractData": true,
	"shareFormData": false,
	"allFormsEditable": true,
	"showPreviousForms": true,
	"redirectNext": true,
	"actions": [
		{
			"name": "Credit Cards Application",
			"type": "Job Task Assign",
			"preCondition": "$formDataMap.productCreditCards == 'true'",
			"redirectNext": true,
			"properties":[
				{"name": "Task Assign User", "value": "$formDataMap.startUser()"},
				{"name": "Task Form Code", "value": maestroonboardingcred2},
				{"name": "Task Message", "value": "Please complete the Credit Card Application form."},
				{"name": "Task Subject", "value": "Complete Credit Card Application"},
				{"name": "Task Input XML Prefil", "value": "$func.stepOrStartSubmissionXml()"},
				{"name": "Task Type", "value": "Form"},
			]
		},
		{
			"name": "Insurance Application",
			"type": "Job Task Assign",
			"preCondition": "$formDataMap.productInsurance == 'true'",
			"redirectNext": true,
			"properties": [
				{"name": "Task Assign User", "value": "$formDataMap.startUser()"},
				{"name": "Task Form Code", "value": maestroonboardinginsu2},
				{"name": "Task Message", "value": "Please complete the Insurance Application form."},
				{"name": "Task Subject", "value": "Complete Insurance Application"},
				{"name": "Task Input XML Prefil", "value": "$func.stepOrStartSubmissionXml()"},
				{"name": "Task Type", "value": "Form"},
			]
		},
...	]
}

Example 1

The job controller below has been extracted from the mOnboarding - Form Tasks - shareExtractData job definition. Its features setup in the with step level attribute flags dynamicPreConditions, shareExtractData, as well as the standard allFormsEditable, showPreviousForms and redirectNext.

All form tasks in the form bundle require action properties, such as:

  • { "name": "Task Type", "value": "Form" }
  • { "name": "Task Input XML Prefill", "value": "$func.stepOrStartSubmissionXml()" } or { "name": "Task Input XML Prefill", "value": "$func.stepOrPreviousSubmissionXml()" }
Note

$func.stepOrStartSubmission or $func.stepOrPreviousSubmissionXml() are required for dynamic preconditions to work. They also work for the static bundles.

Example 2

This example uses a form task bundle configured with the shareFormData attributes:


"shareExtractData": true,
"shareFormData": false	

Review Task

Review tasks are primarily used for review and approval processes that use the same form to review as was submitted by the user. They are configured by specifying a previous step or submission. The review task will copy the XML data, attachments from the triage form. You need to specify a form code so the review task doesn't use the triage form. Review tasks should be only configured with the shareExtractData option.

Example 3

This example is extracted from mOnboarding - Review Task - shareExtractData. The attributes are the same as in the job definition of the Example 1.

The Task Type should be Review:

{ "name": "Task Type", "value": "Review" }

The following code snippet retrieves the review data from a previous step:

{ "name": "Task Review Previous Step", "value": "true" }

"dynanicPreConditions": true,
"shareExtractData": true,
"shareFormData": false,
"allFormsEditable": true,
"showPreviousForms": true,
"redirectNext": true

Next, learn about anonymous form bundles.