Section | |||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
|
The example below shows the parent Lodging-Meal Selections form and its two linked forms. Notice that the parent form and its linked forms initially all have the same name, but the linked forms are outlined by dashed lines rather than solid lines. Note also that the form displays three icons when you click on it, while the linked forms display only the remove icon.
- Click to create a linked step.
- Click to open a step in the Form Designer to edit it.
- Click to remove a linked step.
- Click to download the parent step as a standalone form. This icon will not display on the linked steps.
Linked Steps Workflow Example
Because the parent forms and its linked forms represent steps, you'll want to give them unique names. The parent form in this example has three tabs used for hotel check in, dinner selection, and hotel check out.
To rename the parent step and its linked steps, click on them and then use the Name setting in the Properties panel as shown below.
As with other forms you use to create steps, you can assign a linked-form step to a Role,so that the step is performed by someone with that role, or even by a specific user. In this example, we rename all three steps and assign each to a different role.
- CheckIn is assigned to the Reservations role.
- DiningRoom is assigned to the MaitreDHotel role.
- CheckOut is assigned to the Billing role.
You may also want only certain sections of the form to be visible in an specific step so that only users in a certain role see those sections. For example, in this flow, perhaps only the dining room staff needs to see the form's Guest Information tab.
To do this, you can edit the the form via the Flow Designer and use the Security Tab in the Forms Designer to assign a role to sections of the form. Click the form, and then click to open the form in the Form Designer.
In this example, we assign the Guest Information tab to the MaitreDHotel role.
When the flow runs, the first step, CheckIn, is performed by a user with the Reservations role, so that user does not see the form's Guest Information tab, which is only visible to a user with the MaitreDHotel role.
The next step in the flow, DiningRoom, is assigned to the MaitreDHotel role, so that user sees the Guest Information tab.
You can also use rules to show or hide parts of a form in an step. For example you could use the rule below to show the Guest Information tab only when a MaitreDHotel role is using the form.
This rule is useful in a workflow where you want to make the tab named Review visible only for the workflow step named Manager Review.
Code Block |
---|
if (form.load) { if (_data.getParameter('flow.step.name') == 'MaitreDHotel') { GuestInformation.visible = true; } } |
For more information about using rules this way, see the Security Subject topic in the Rules Examples section.
Linked Forms and the Submissions PDF
If you check the Save PDF property on the flow properties panel, a PDF image of the flow is saved in the Live Forms' submission repository. It is no longer necessary to uncheck the printable property for all but one of the steps if your flow is designed with Linked steps to prevent the form from being printed more than once in the default pdf. This was required in previous versions of Live Forms. Refer to this Printable property for more information.