Now comes an important part of the collaborative design cycle: testing the form from a portal.

 

For this to work, the appropriate Collaborative Job Controller service must already have been set up in Transaction Manager. You then publish the form to TM and associate the Collaborative Job Controller with the form:

 

You must also have some appropriate groups set up for the "reviewers", that is, the users internal to your organization. How to do this is beyond the scope of this document: please refer to the TM Administration Guide.

 

Note: in the JSON object, there are some values which are, quite properly, not hard coded into the JSON. These are marked by "##GET FORM PROPERTIES". In TM, you can specify parameters which are local to that particular form. Please consult the Transaction Manager Administration Guide on how to create a property type (with its scope restricted only to the form) and then apply it to the particular form as a parameter.

 

Then use the form in the portal, and select "Open a New Form". You may have to create a new login on-the-fly as the applicant. Fill in the form and submit. Logout of the portal and login as the reviewer of the Initial Review step.

 

The form should be now allocated to that user's Task List. Open the form from the tasks, and select the route you are testing. And so on.

 

If all is well, TM will display the following details for a job. (Here, Start by the applicant -> declined Initial Review -> resubmitted by the applicant -> Initial Review a second time and routed to Additional Review -> Approved -> Data goes to the enterprise's back end.)