Skip to content

Record manager

How-to8 minPractitioner

Before you start

A Record manager step creates, updates or deletes records. Use it to set a contract’s status to Published, to raise a purchase order from an approved RFx, or to save a whole list of lines at once.

Use it whenever a workflow must change data. It is the step on the Approved and Rejected paths of an Approval task, because the approval itself only pauses the run. For one-off arithmetic or odd cases, a Custom function is the fallback.

  1. Click + and choose Record manager. It sits in the Records group.
  2. Under What should it do?, choose Create, Update, Delete, Batch create or Batch update.
  3. In On which module?, choose the module.
  4. For Update or Delete on another module, set Which record?. See below.
  5. Under Fields to set, click Add a field, choose the field, and give its value.
A Record manager step selected in the Publish Contract workflow. It updates Contracts, the record that started the workflow, and sets two fields.
    Choose the action: Create, Update, Delete, Batch create or Batch update.
    Which record? here is the one that started the workflow, so no key is needed.
    Fields to set lists each field and its value.
SettingWhat it does
What should it do?The action: Create, Update, Delete, Batch create, Batch update
On which module?The module to change. Changing it clears the field list
Which list?For batches only: the list whose rows are saved, one record per row
Which record?The record to change, found by its Record ID (the key)
Fields to setEach field and its value. Fields you do not list keep their values

A value is typed text, a picked lookup value (Pick a value), inserted data, or a Smart Script. Plain text and numbers are saved as typed. Data or a calculation is worked out first. A file field offers Map a value from a field, Use the content of a field and Build from a text object. Rows are filled top to bottom, so a value can use a field filled above it.

  • Update on the workflow’s own module changes the record that started the workflow. No key is needed.
  • Update or Delete on another module finds the record by its Record ID. Give the value from a field of the record, a list, or the current item of a loop.
  • Batch update finds each row’s record through the key you set, and saves all rows in one request.

To update every record of a list, use Batch update and skip the loop. One request is faster than one request per record.

Layla’s workflow runs on Contracts. A Record manager chooses Update, on Contracts. It sets Status to Published with Pick a value. The step updates the contract that started the run, and the Send email below it tells the vendor.

  • A Batch step inside a Loop runs the whole batch in every round. With 12 items the list is saved 12 times.
  • To update by key, give the module a key field in the module settings.
  • Within a loop over one module’s records, updating that same module changes the current item directly.

Check yourself

A workflow on Contracts updates the Contracts record that started it. What does the step need to find the record?
Show the answer

Nothing, it updates the record that started the workflow. Updating the workflow's own module changes the record that started it directly. No key is needed.

Which action finds each record by its key and saves every row of a list in one request?
Show the answer

Batch update. Batch update saves all rows in one request. Each row finds its record through the key.

What's next

Last checked