Permanent Assignees on Subprocesses and Templates
You can now set a "forever assigned" maker and approver on templates and regular subprocess forms. If responsibilities in your team rarely change, this removes the need to assign people on every deadline.
Key things you can do with this:
Define assignees on the template so they carry over automatically when deployed, with no manual assignment needed.
See assigned users as avatars on the process card in the dashboard for clear ownership visibility.
If someone is unexpectedly unavailable, their assignment can be temporarily changed from the dashboard without editing the process.
A new Assignees tab lets you define who is responsible for each subprocess, both on the template and on the process form.
Self-Assignment for User and Approver Roles
Users with a User or Approver role can now assign themselves to a subprocess as maker, approver, backup maker, or backup approver directly from the dashboard. Previously, this required a team admin.
This makes it easier for team members to claim work items or handle temporary coverage without waiting for a team admin.
Cross-Team Process Ownership
For organizations with team boundaries, you can now set a team you do not belong to as the process owner. This makes it possible to create shared processes across teams that collaborate with each other.
In the process form, the process owner field shows your own teams by default. A "Show All" option lets you expand the list and select from other teams in the organization.
Bug Fixes
Fixed an issue where configuring notifications with multiple recipients, including the dynamic Maker recipient, could incorrectly apply a "Before deadline" rule to the Maker.
Fixed an HTTP 500 error that prevented subprocess template details from loading when the template had notifications configured.
Fixed an issue where the subprocess owner dropdown only showed the user's own teams, even on templates shared across multiple teams. It now shows all teams the template belongs to.