Live Forms Latest - This documentation is for Live Forms 7.4 Not for you? Earlier documentation is available too.

Skip to end of metadata
Go to start of metadata

To design/modify a form step in the flow designer, first click it to select it; it turns light blue. Click the pencil icon  to launch the Form Designer. For more information on designing forms, please see the Form Designer documentation.

As a reminder, when a form is added to your flow it is added as a copy. When you edit it, your changes will be saved to the copy and will not affect the original form that was dragged in from the palette. However, you can download a form step from a workflow as a standalone form by clicking the forms icon.

On This Page:

 

Choosing a Design Pattern for your workflow

There are two design patterns to be considered when designing your workflow. Choosing one design pattern over the other really depends on the purpose of your workflow. The choices are:

  • Use individual form as your steps
  • Use Linked steps

For example, if you were creating a workflow from a fifty tab Excel spreadsheet, you can create forms for each tab then drag the individual forms into your flow for your steps.

Workflows where one form gets routed to a lot of people and they all have to work on it collaboratively, typically use the Linked steps approach.

Just a reminder, there are several design paradigms for workflows that you may want to consider depending on your flow requirements. You can find examples of each type here.

Form Control Names and Schemas 

When you create a flow, Live Forms creates an XSD schema of the flow that combines all the fields in all the forms in the flow. For example, if you go to the Flows home page and click  to download or open a flow's schema, you'll see that it contains elements for all the controls in each form in the flow.

When designing the forms you want to use in a flow, be aware that if controls in the different forms have the same name, their data will merge in the XML document that Live Forms generates when the flow runs and is submitted. While the Form Designer automatically prevents you from giving two controls the same name within the same form, it doesn't prevent you from giving controls in different forms the same name.

For example, suppose one or more forms in a flow have a text control named FirstName. On one form, this might be an employee's first name; on another, it might be a manager's or customer's first name. When the flow runs and is submitted, the two first names will merge in the resulting XML file. To avoid this, you should give the fields unique names — such as EMPFirstName' or MGRFirstName' — so they'll be separate elements in the flow's XSD schema and separate pieces of data in the submitted flow's XML file.

Another way to avoid data merging is to "nest" controls with the same name within Section controls (which control nesting) that have different names in different forms. For example, suppose you have one form with a Section Control named Employee' that contains a text field named FirstName. A second form has a Section control named Manager that also contains a text field named FirstName. If you use both of these forms in a flow, the FirstName data does not merge because the two controls are nested — at the same level — within Sections that have different names.

See Section Controls in Designing Forms for more information on using these controls. Be aware that Section controls can themselves contain Section controls, and that this affects the nesting level of the controls they contain.

The same data merge consideration is true for form data generated by schemas. For example, suppose you're designing an employee performance review flow that includes two forms. Form 1 contains past performance review data (perhaps read-only) from a database; Form 2 is the same but blank for the current review.

If both forms update the same database table, they may be generated from the same XSD created by a database connector. The issue is that data in Form 2 (current review) will merge with the Form 1 values (past review) if their schemas are the same.

One solution for this problem would be to write two different queries in the database connector so that the past review and current review schemas have different namespaces, which would prevent them from merging.

Digital and Wet Signatures in Signed Sections named the same in more than one form used in a flow will not be merged. However, identically namesignature controls in two different steps in a flow share the same wet signature.

  • No labels