Changelog
Keep up with the latest updates we’ve made in Workato.
Update to dashboard job totals
As part of a slow rollout, some customers will now see that the Dashboard counts jobs only once, by the last repeated job (e.g. a single job that has been repeated three times and failed each time will display as one failed job in the Dashboard). This behavior matches the Jobs History table, and should result in clearer analytics about the total successful and failed job counts for a given time period.
Once released widely to all existing workspaces, this will be the default behavior for all net new workspaces.
Cancel multiple jobs in process
You can now select multiple jobs in the Jobs History table and cancel. Only jobs in process can be canceled.
Select/deselect all tables when creating a manifest
When creating a manifest file for your project, you can now select/deselect all tables that you would like to include from the project. This update brings the table select behavior in line with the properties select behavior, allowing you to more quickly create manifests for complex projects.
Environment deployment permission update
Our latest update introduces a new Deployment permission for deploying project across environments. Effective December 12, 2023, users need this permission in both Development and target environments in order to deploy, replacing the Recipe lifecycle management requirement.
The Deployment permission is enabled for system roles and custom roles as follows:
- Admin: Enabled
- Analyst: Enabled
- Operator: Disabled
- Custom: Disabled until an admin manually enables it
This security enhancement provides better control over who can deploy to production or test environments by separating deployment permissions from recipe lifecycle management permissions.
Manage workspace users with the new User Audit API
The developer API just got more powerful with the addition of the user resource. This new set of endpoints allows you to perform the following actions:
- Get details of the authenticated user
- Get a list of members in your workspace
- Get details about a user you specify
- Get the role and privileges for a workspace user you specify
Navigate faster than ever with our Workspace settings and profile settings split!
We've revamped our navigational experience by separating workspace related settings from your personal profile settings. Our new Workspace admin tab is your go-to tab to find all environment related features such AI usage, Secrets Management, Key management, Audit Log Streaming, and more!
The personal profile tab on the other hand houses your personal information such as your name, email, workspace memberships and is the place you go to configure 2FA for your own account!
Streamline asset management with new filtering options
Discover assets more efficiently with our enhanced filters. Previously, you could only filter assets by type and status. Now, you can also filter by apps, recipe trigger, and editors.
Recipe Lifecycle Management Enhancement: Option to Disregard Submit Button Command Recipe when Building Package
If a project includes a bot that is calling a recipe using a "Submit button command", we now allow building and deploying packages without the recipe in the folder. Previously, users would experience an error preventing them from building or deploying packages based on the missing recipe. This error can now optionally be disregarded. This aligns behavior to how packages can be built and deployed that reference Recipe Functions from different projects.
Logging Service Scoped to Project Permissions
Logging Service has been updated to allow user access based on project permissions. Now, users will only be able to see log entries for projects they have access to. This enhancement both makes logs easier to parse for users by making sure they only see relevant logs, and improves security by limiting access to logs based on user permissions.
Recipe Version Comments in Recipe Lifecycle Management
Recipe version comments will now follow recipes through their lifecycle. As a recipe is deployed from development to test, and from test to prod, recipe version comments will be preserved. This provides additional visibility and traceability as recipes are deployed between environments.