View and manage permissions for Actions
Not everyone who needs to know about an action should be the one to close it. Action Definitions now let you separate who can see an action from who can act on it: some user types can view the action in read-only mode, while others can also mark it as done or discard it.
For example, an Operator can see that a filter replacement is coming up, while only the Service Technician who performs the work can mark it as done.
This keeps the action history reliable, prevents actions from being closed by users who are not responsible for them, and still gives everyone the visibility they need.
In the Console, the General section of the Action Definition extends the existing User Type Visibility option: for each action, you can choose which user types can only view it and which can also mark it as done or discard it.
By default, actions remain visible to all users, so existing configurations are not affected.
Import and export event remedies
Remedies help DPS users solve problems on their own before they need to call for assistance.
In the Console, you could already import and export events in CSV format, and now you can do the same with their remedies.
Troubleshooting content can be long and is often written by service experts outside the Console. You can now prepare and review remedies in a spreadsheet, update many of them at once, and load them in a single step instead of editing each event by hand. This makes it easier to keep troubleshooting guidance complete and up to date, so DPS users always find the right steps to fix a problem themselves.
Remedies are imported and exported in their own CSV file, separate from the events file.
Bug Fixes (DPS)
The on-payment-update automation was triggered multiple times, causing duplicate emails to be sent.
An unexpected blank page was added to generated PDF reports.
Address autocompletion did not populate secondary fields (Zip code, State/Province) for UK addresses.
The thing list did not allow sorting things by country.