MaestroThe UI design product. | Form Builder | All versions This feature is related to all versions.
Maestro forms require configuration before you can use them with collaboration jobs, including:
In this example, we use the Maestro form configured with the Review and Approval – Multi Step Group Review job controller service in Manager.
Some form components are required to be saved as data extracts so they can be used with collaboration jobs. For example, the forms used in this example where an applicant enters a loan amount. If the reviewer approves the loan, the Loan Amount on the Request tab must be checked to validate if it exceeds the threshold of $20,000. In this case, the loan must be also approved by a manager. To achieve this, we will pass the entered loan amount from the form to the job controller service in Manager using the form of data extracts.
To include a component into the data extracts:
Collaboration job components have been created to assist the form builder in combining the collaboration jobs features into their forms.
To use a collaboration job component in Maestro:
The collaboration job components can be one of the following:
This component is used for form bundles as a way of navigating and keeping track of forms that are still to be completed. It appears as a set of links for navigating to the applications for products previously selected. It has extra features such as allowing a user to click on only the applications that have not been completed and allowing to download a copy of any completed application.
It provides a similar feature as the form bundle job tasks, but it is presented as a simple dropdown.
This component is for displaying collaboration job details on the form.
To display the collaboration job details:
This component displays the collaboration job number.
This component displays the step's name the collaboration job is currently at.
This provides a section in your form that can be used to test the form without having to render the form in Manager. The block is used for testing purposes and can be viewed from the preview mode in the Maestro editor. This allows the form builder to preview the form and make sure that the rules are set up correctly without having to leave Maestro. That is, without the form being first deployed to Manager and associated with a job controller. It is important to note that the Preview Test Block will never display in a built / rendered form as it only appears when using the Maestro Preview mode.
The following components may be entered:
This component is a dropdown that will present to a reviewer or manager reviewing the application a list of options. A review or manager will choose an option to indicate their decision. This component will dynamically plug-in the values for the options from the job controller associated with the form. This may be useful but there has been a preference towards using radio button group component instead. For more information, see below.
A collaboration job workflow is often required to be shared amongst the relevant parties, such as an applicant, a reviewer and a manager. For the form to be presented suitably to each user, you need to specify the form rules, such as:
To allow only the applicant to enter and update their personal or form request details, you must create editability rules in your form as shown below.
Create the editability rule with the second parameter matching the step name in your intended job controller service configured in Manager. In this example, the step name requesting the applicant to update their details is the Applicant Update step.
Add this same editability rule to the applicant’s request.
Create the following visibility rule to present the relevant information to the applicants when their application was declined. This rule allows them to choose whether to update or terminate their loan application.
This rule is only relevant for this section to appear when the application was previously declined.
A visibility rule is created to only show this tab to both reviewers and managers.
Create a new rule as shown below.
Both the reviewer and the manager need to be able to indicate their decision on the form. Previously, we covered the Route Select component, which dynamically loads each of the possible decisions for a reviewer and a manager, using the job controller service. However, a radio button group is much better choice because:
The only negative side is that the radio button group doesn’t allow for the dynamic load of the radio button options based on the job definition service. You must hard code the possible decisions as radio button options on the radio buttons group.
In this example, the reviewer and the manager are both involved in the collaboration job, so we will use the Review and Approval – Multi Step Group Review job controller service.
As this decision feature is not available for the applicant, it makes sense to add a separate tab, the Approval tab, to your form, which can be shared amongst the reviewer and manager, so it is only visible to them.
To create a new visibility rule:
Click Save.
Being a shared tab, we need to manage the form interaction correctly for each of the parties involved. For example, the following rules apply:
To keep it simple, we will cover some of the rules here, but you will need to determine all the rules that apply for your form.
To create a radio button group for the reviewer decision:
To create a radio button group for the manager decision, repeat the above steps 2 to 8 and give it a suitable name, for example Additional Review Decision.
As explained above, the two radio button groups require different rules, so for the reviewer, the Initial Review Decision radio button group, you need to create the following two rules:
An added complexity exists with sharing this form regarding which decision must be used for the job controller to decide what to do next. For this, you need to create a change rule which plugs the reviewer decision to the system profile route name, Job.RouteName, only when the reviewer has changed this. This means that, on change, the reviewer decision will be used by the job controller. To do this:
As the reviewer can also be seen by the manager we need to make sure that only the reviewer can update this. To do this:
For the manager, the Additional Review Decision radio button group, we need to create the following two rules:
The same change rule as for the reviewer needs to be added here to allow the manager’s decision to be used for directing what happens next when this has been changed.
This radio button group must only be visible to a manager. To do this:
Some other rules that may be relevant are:
In this case an Approve Advice Block pops up when the reviewer or manager clicks the Approve radio button option, to highlight the decision they are about to submit.
For this the visibility rule is:
When either the reviewer or the manager declines the application, they must enter a reason for their decision.
The following visibility rule is required for the Reason for Decision field which is ticked as Mandatory.
The visibility rule is:
Now, your Maestro form is ready to be used with collaboration jobs.
Next, learn how to configure Composer forms for use with collaboration jobs.