Matthew White

{

	"name": "Referee",

	"type": "",

	"actions": [

		{

			"name": "Assign Review",

			"type": "Job Task Assign",

			"properties": [

				{

					"name":...

Upon first submission of a form by a user we trigger a Job Task Assign action:

{

	"name": "Referee",

	"type": "",

	"actions": [

		{

			"name": "Assign Review",

			"type": "Job Task Assign",

			"properties": [

				{

					"name": "Task Assign Email",

					"value": "$formDataMap.RefOneEmail|$formDataMap.RefTwoEmail"

				},

				{

					"name": "Task Form Code",

					"value": "$func.startFormCode()"

				},

				{

					"name": "Task Form XML Data",

					"value": "$func.stepOrPreviousSubmissionXml()"

				},

				{

					"name": "Task Attachments Submission Step",

					"value": "Application Start"

				},

				{

					"name": "Task Send Email",

					"value": "true"

				},

				{

					"name": "Task Type",

					"value": "Anonymous"

				},

				{

					"name": "Task Assign Repeating",

					"value": "true"

				}

			]

		},

		{

			"name": "Review Wait",

			"type": "Job Task Wait"

		}

	],

	"routes": [

		{

			"name": "Default",

			"nextStep": "Deliver Submission"

		}

	]

}

which assigns a task to 2 different reviewers in parallel. We want to process the Delivery of each completed review task as they arrive rather than waiting for both to complete via the "Job Task Wait" and then performing an action. So, according to the config above we want "Deliver Submission" to actually run for each task immediately that it completes. Is this possible? How might we go about doing it?

Matt

It turns out that this was due to the lookup user not being found for the given ldapSearchBase. Unfortunately TM gives you the same error 'Bad Credentials' for both an incorrect service account username/password combo and also for a user not being found against a search Base, this took some time to get to the bottom of as I thought that the service account was failing for some reason.

Can I suggest as a future update that Manager be more explicit in the error messages about what is failing and why, specifically to distinguish between the service account bind failing vs the user not being located due to an invalid search base.

Matt

Hi

I'm getting a Bad Credentials Error when authenticating to an ldap (Active Directory) server from an ldap authenticator in Journey Manager. I can write custom groovy code that runs from the Journey Manager console to authenticate (bind) successfully but the same parameters don't work from the authenticator. How can I enable debugging/logging for this module in standalone.xml?

This has worked on previous TM versions.



Matt