More control over matching and Workflows
Move from a suggested match to an assignment or conversation, access more supported Workflow actions, and work more confidently in private workspaces and documents.
A closer look
What changed
The matching widget now offers actions beside each suggested person. You can fill the shift Assignee field from a match, or open a direct Engage conversation with the record attached. This release also restores supported actions in the Workflow editor and improves private workspace editing, document filters, file deletion and collection creation.
Why it matters
Schedulers can move from a suggested match to the next step without finding the person again elsewhere. The assignment stays an unsaved edit until you confirm it with the record Save button, so you remain in control of the final change.
How to use it
- 1Open a shift record with the matching widget and review the suggested people.
- 2Hover over or focus a matching row to reveal its available actions.
- 3Choose Assign to fill the Assignee field, review the change, then select Save on the record.
- 4To discuss the shift first, choose Message on desktop. Engage opens a direct conversation with that person and attaches the record to the draft.
- 5Review the message and attached record before sending.
Example
A scheduler reviewing an open shift can message a suggested worker with the shift already attached. Once the worker confirms, the scheduler can choose that match, review the Assignee field and save the assignment.
Availability
Assign appears on shifts with user matches when you can edit the Assignee field. Message requires Engage access and the Chat permission and is available on desktop. Workflow actions depend on the triggering record and event. Record locking actions appear only where record locking is enabled.
Ask Customer SuccessGood to know
- Choosing Assign does not save the shift automatically.
- Message opens an existing direct conversation when one is found in the selected department, or starts a new conversation. It does not send a message automatically.
- Private workspace content editing is available to the owner and people with Edit access. View access does not allow editing.
- Tables and reports retain their existing permissions, including Data Builder where required.
Step by step guides
Move a process from a draft to a published Workflow, with clear conditions, a timeout path, and a check of what actually happened.
Assign or message a suggested matchReview a suggested worker, inspect the matching criteria, and move to an assignment or conversation with the shift in context.
Create and share a private workspaceStart with a workspace for yourself, give selected teammates view or edit access, and understand what changes when you publish it to a team section.
Highlights
Act from matching results
Choose a suggested assignee or open a conversation with the shift attached. Review and confirm before saving or sending.
More complete Workflow actions
Configure supported request approvals, shift ending and record locking actions with the appropriate triggers and permissions.
Smoother everyday editing
Add private workspace content, configure document filters and name new collections with fewer interruptions.
Act on a match, with the shift in context
Open a shift with the matching widget to review suggested people. Hover over or focus a row to reveal Assign and, on desktop, Message. Assign fills the Assignee field as an unsaved edit: review the change and use the record Save button to confirm it. Message opens a direct Engage conversation with the person and attaches the record to the draft, so you can discuss the shift before assigning it. Assign requires permission to edit the Assignee field. Message requires Engage access and the Chat permission. The matching breakdown shown below helps you inspect the criteria behind a suggestion.
Use more supported actions in Workflows
The Workflow editor now includes seven supported actions that were missing from its picker: approve a shift request, deny a shift request, approve a shift group request, approve a release request, end an ongoing shift, lock a record and unlock a record. Approval actions need a compatible claim or request trigger, and ending an ongoing shift needs a user trigger. Lock and unlock appear only where record locking is enabled. Existing Workflows using these actions now display their configured action instead of appearing unconfigured. Run job matching is shown as unavailable rather than allowing a choice that cannot be published.
Add content to your private workspace
Private workspace owners and teammates with Edit access can add text, images, videos and buttons to a blank canvas without Data Builder permission. This restores the content drawer when you have permission to edit that private workspace. Teammates with View access still cannot make changes. Creating tables and reports retains the existing collection and feature permissions, including Data Builder where required.
Confirm before deleting a file
Choosing Delete from a file chip menu now opens a confirmation dialog before the file is removed. This applies to file cells and the Documents tab. The confirmation gives you a chance to stop an accidental deletion before it reaches the underlying file. It does not add an undo or recovery feature.
Keep document table filters open while editing
In Document Studio, selecting a linked table filter column, operator or value no longer closes the configuration panel. Newly created linked tables start with centered data rows and normal text weight. Existing saved tables keep their stored formatting. The linked table placeholder also keeps a consistent height after applying settings, clicking away and reopening the document.
Name a new collection before creating its workspace
When you create a List workspace with a new blank data source, the wizard now asks for a collection name before creating it. The name is used for both the collection and its workspace. The field starts with New Collection selected, ready to replace. Enter a name and choose Create workspace, or press Enter. Clearing the field prevents creation until a name is entered. Going back or cancelling leaves no new workspace or collection behind. Template based creation continues to use the template name.
