Persist Repeating Form Rows in a Relational Table¶

Scenario¶

Use this example when a process should maintain a simple address book by saving form rows into a relational database and loading them back into the form later.

What You Will Learn¶

• model repeating form rows with a stable identifier
• persist those rows with ImportFromXml
• load the saved rows back into the form with ExportToXml

Difficulty and Estimated Time¶

• Difficulty: Intermediate
• Estimated time: 25 minutes

Assumed Knowledge¶

You should be familiar with table-content forms, XML paths, prework, postwork, and relational schemas.

Required Reading¶

• Relational Databases
• Table Content
• Data Model
• Prework Script
• Postwork Script

Prerequisites¶

• permission to create processes and relational schemas
• access to prework and postwork scripting
• a process form that can host repeating contact rows

Steps¶

Create the Folder, Process, and Task¶

1. Create an application folder, for example Address Book.
2. Create a process and open it in edit mode.
3. Rename the opening task to Definition.
4. Add Update and Cancel actions.

Build the Form¶

1. Open the form designer.
2. Add a tabbed content control, for example Contacts.
3. Add a table-content control inside that tab.
4. Create the columns required for the contact rows, such as name and phone number.
5. Set the phone field type to Telephone.

Extend the Data Model¶

Add an Id field under the repeating contact structure so each contact row can be uniquely identified.

Define the Relational Database¶

1. Open the database area of the process.
2. Create a schema such as AddressBook.
3. Add a table such as Contacts.
4. Define the required fields, including a unique identifier column for the contact ID.

Save the Form Data in Postwork¶

In the task postwork, write the submitted rows to the relational database with ImportFromXml:

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12

if ($WorkItem.SelectedAction == 'Update') {
    $Database.ImportFromXml({
        Parameters: {
            TargetSchema: "AddressBook",
            TargetTable: "Contacts"
        },
        XPath: "AddressBook/PersonalInformations/Personal",
        Map: function (xml) {
            this.Phone = xml.Evaluate("PhoneNumber")
        }
    });
}

This persists the rows from the XML form data into the Contacts table.

Load the Existing Contacts in Prework¶

In the task prework, load the saved rows back into the form with ExportToXml:

1
2
3
4
5
6
7
8

$Database.ExportToXml({
    TargetSchema : 'AddressBook',
    TargetTable : 'Contacts',
    XPath : 'AddressBook/PersonalInformations/Personal',
    Map : function (row) {
        row.SetValue("PhoneNumber", this.Phone)
    }
});

This makes previously saved contacts appear when the form is opened again.

Test the Address Book¶

1. Commit the process changes.
2. Start the form.
3. Add a contact row.
4. Select Update to save it.
5. Open the form again and confirm the saved contact is loaded back into the table.

Result¶

The process now behaves like a lightweight address book: it saves repeating form rows into a relational table and loads them back when the form is reopened.

Verify the Result¶

Save two rows, reopen the task, and confirm that both rows retain their values and stable IDs. Edit one row and verify that it is updated instead of inserted again. Repeat the action once to check for duplicate writes.

Security and Portability Notes¶

• Authorize relational reads and writes for the current tenant and process context.
• Keep stable primary keys for updates, and make repeated postwork execution safe before using the pattern in production.
• The sample data is illustrative; apply the target domain's retention and privacy requirements to real contact data.

What to Learn Next¶

• Populate a Dropdown with Data from a REST API
• Generate Worklist Tags from Form Data

Related Pages¶

• Relational Databases
• Table Content
• Data Model