Changelog

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.

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

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!

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.

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 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 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.

Now lookup tables can be both programmatically created or deleted using the Workato Developer API. Tables can be created and scoped dynamically based on the provided schema, and then deleted in batches as required.

With Audit Log Streaming Notifications, breakages in streaming connections will be detected and an email will be sent to users with troubleshooting steps. This allows users to immediately detect both voluntary and involuntary breakages so that it can be resolved in a timely manner.

Exciting news! We’ve introduced two enhanced security features: project-level properties and lookup tables access limit, now available to all users without any limitations or specific requirements!

Project-Level Properties: Located in the ‘Project settings’ tab, these properties are exclusive to recipes in the same project and are accessible to users with the appropriate permissions and visibility.

Lookup Tables: Users can now adjust the availability zone for lookup tables from ‘All projects’ to a specific project, making them accessible only to users with the right permissions and visibility to that project.

Quick Overview:

• Open Access: Available to all, no additional requirements.
• Enhanced Security: Better control and management of sensitive data.
• API Accessibility: Both features are available via API.