AgentCreator

• Introduced the MCP Client Snap Pack, which adds the capability of connecting to your MCP Server

APIM 3.0

• GA release

• Tracing added for new components

SnapLogic Community

• Integration Nation has moved to Slack to enhance user engagement

Monitor

• Multiple UI enhancements on the Pipeline execution and Infrastructure pages

Snaps

• Enhanced the visual styling and color palette of Snap components to improve usability

• Added the PostgreSQL Bulk Upsert Snap to the PostgreSQL Snap Pack

• Added the Teradata Multi Execute Snap to the Teradata Snap Pack

• The API Management 3.0 settings page now contains the following options for the Developer Portal. If you change the URL, toggle, or logo, the Developer Portal site rebuilds, and the Build site button shows the build progress.

  Open

  

The MCP Client Snap Pack is now available on the latest and stable versions. It enables you to connect to MCP servers as part of your Agent. This Snap Pack contains the following Snaps and Snap Accounts:

• MCP Function Generator: Use this Snap to convert the tools available from an MCP server to a list of function definitions, with the additional ability to add "list resource" and "read resource" to the function definitions list.

• MCP Invoke: Use this Snap to execute the operations you want the MCP server to perform. This Snap formats the generated results into a unified structure within SnapLogic.

• SSE Account: Use this account type to connect the MCP Client Snaps to a remote MCP SSE Server.

• Streamable HTTP Server Account: Use this account type to connect MCP Client Snaps to a remote MCP Streamable HTTP Server.

• SSE OAuth2 Account: Use this account type to connect MCP Client Snaps using an SSE server using OAuth2 authentication.

• Streamable HTTP Server OAuth2 Account: Use this account type to connect MCP Client Snaps to Streamable HTTP Servers using OAuth2 authentication.

API Management 3.0 is now GA. To enable it for your production Environment, contact your Customer Success Manager.

• The following rules now emit tracing: HTTP Response Cache, HTTP Retry, Outbound TLS, Request Transformer, and Response Transformer. Learn more

• To enable Try it out and use API keys or JWTs for authentication, you no longer have to pass the key in a custom header or query parameter. Now, the Authorization Scheme field has a value of bearer, which fetches the key or token from the Authorization Header.

• The beta DeveloperHub has been replaced with the APIM 3.0 Developer Portal and the Site Manager is no longer available. If your environment has a DeveloperHub site with customized pages, you must use the Admin Manager to rebuild the site and replace it with the GA Developer Portal. This will remove all customizations and custom pages. To keep the same URL for the Developer Portal site, change the logo or toggle to allow access without login as described in the next bullet. Learn more

• The API Management 3.0 settings page in Admin Manager now contains the following options for the Developer Portal. If you change the URL, toggle or logo, the Developer Portal rebuilds. Learn more

  Open

  

• DeveloperHub has been renamed to APIM 3.0 Developer Portal. It is available from the Resources section of the waffle menu:

  Open

  

• You now create Developer Portal categories and select the categories for the Service from the Documentation tab. Learn more

  Open

  

• When the left navigation menu is expanded, it now returns to the expanded state after you exit the Policy Builder.

• The Authorize button now correctly appears when you configure Try it out with a bearer token.

• Disabled tasks are no longer available for selection when you add an endpoint to a Service.

• In a Developer Portal Application, the Get Key button now displays when a subscription is approved that uses a JWT for authentication.

• After you revoke a JWT, you can now generate a new one with the same name.

• To enable Try it out and use API keys or JWTs for authentication, you no longer have to pass the key in a custom header or query parameter. Now, the Authorization Scheme field has a value of bearer, which fetches the key or token from the Authorization Header.

• Fixed the issue of logging an extra, incorrect token revocation event in the Activity table when an Environment admin or owner rejects a subscription request.

• To use Subscriptions, you must upgrade to Snaplex version 4.43 or later. The recommended version is currently main-37701 or 4.43.1.0. For the best results, update the Policies Snap Pack to 443patches33227 or later.

• When you edit the value in Rule input fields, the cursor jumps to the end of the string after every keystroke.

• If the Policy applied to an endpoint includes a Generic OAuth2 rule, the endpoint must support the GET method. Otherwise, requests fail with a 405 Method Not Allowed error.
  Workaround: Configure the endpoint to support both the GET and any other required methods, and the request will succeed. 

• When a new Developer Portal user receives a welcome email with a default password, login fails with the error Login Failed: Invalid Username or Password.
  Workaround: Use the Reset Password link in the email or the Forgot Password link on the login page. After a password reset, the user can log in.

• If a Service version is configured with routing rules as a header and has Try it out enabled, the route fields don’t show up in the Authorize dialog.

• Previously, when selecting a table in the AutoSync data pipeline wizard, the selected table would remain in its original position within the list, making it difficult to locate your selection, especially when working with a large number of tables. Now, the selected table is automatically moved to the top of the list, allowing you to easily identify the selection during pipeline creation.

  Open

  

• For environments with APIM 3.0 enabled, both 3.0 and Classic APIM are available from the APIM option on the waffle menu:

  Open

  

• The Developer Portal continues to be available from the newly renamed Classic APIM Developer Portal link in the Resources section of the waffle menu:

  Open

  

• For Git commit operations, the UI now correctly displays Tracked Modified Locally in the Git Status column instead of git_app.

• Added a new page for the Installation and configuration of the Oracle Instant Client for use by Oracle Bulk Load Snap.

• Updated the TLS cipher list and added the frequently asked questions to the Groundplex deployment plan.

Watch this video to know how to create a tool pipeline in SnapLogic Designer that searches the web. This tool pipeline can be called by your SnapLogic Agent.

• Updated the filter labels and a button on the Pipeline executions page.

  • Removed the Pipeline grouping label and Filter presets labels from both tables (the buttons are still there). Removed the Ultra pipelines filter button from the Non-running pipelines table.

    Open

    

• Updated the Activity logs in Monitor to display activity logging for CI/CD actions for the following Git-related events:

  • Git checkout on a project.

  • Git pull on a project.

  • Git commit on a project.

  • Untracked project from Git.
    You can filter these events within the Monitor -> Activity Log view.

• In the Snap statistics panel, the row expansion interaction has been changed from hover to click for better usability. You can now click a Snap row to expand it and view detailed information, and expand multiple rows simultaneously. Hover over the bar graphs to display tooltips as before.

  Open

  

• Readability of project names in the filter for the Project column has been improved. The Project space name now only appears as the parent of projects and isn’t repeated as part of the child Project names:

  Open

  

• You can now control automatic data refresh for the Pipeline execution tables using the new Automatic Refresh toggle in the Table configuration and filters dialog. By disabling it, you can pause the page refresh and get a stable view of the data for analysis.

  Open

  

   

• For better visibility, the Collapse or Expand header button on the Pipeline execution details panel has been moved to the top-right corner of the header. This functionality has also been added to the Node details and Snaplex details panels.

  Open

  

   

• The .csv file download from the Monitor Pipeline executions page now only includes the data from the columns and rows selected in the interface.

• The Infrastructure view for non-Linux Snaplexes reports disk usage as a single percentage instead of separate values for home and tmp, which are usually separate mounts on Linux machines.

On the Admin Manager Users page, the Roles dropdown includes an All roles option that is available in the role selector for an individual user row. It appears that you can change a User role to All roles from the dropdown. A confirmation message is shown indicating that the role was changed. However, the User role is not updated. This is a UI bug that will be fixed in the upcoming release.

Workaround: Avoid selecting All roles from the role dropdown on individual user rows. Use All roles from the filter at the top of the Users page to view users across roles.

• The Project filter now displays APIM projects with the correct nesting and without duplication.

• You no longer have to Stop completed pipelines that the Monitor app displays as running.

• Added custom claims snaplogic_org and snaplogic_aud for organization identification and to address a Microsoft Entra limitation that restricts modification of the aud claim required for JWT authentication on the public API. Learn more.

• To enhance user engagement, Integration Nation has moved to Slack. Learn more.

• The technical blogs and Sigma framework architecture documents have moved to the SnapLogic corporate website. Contact Scott Olsen (solsen@snaplogic.com) with any questions regarding this move.

• EDIFACT: Introduced the EDIFACT Snap Pack with the following Snaps:

  • EDI Formatter: Reads incoming JSON document data and formats it in the selected EDIFACT type and version.

  • EDI Parser: Reads the incoming EDIFACT binary input data of the selected EDIFACT type and version and formats it into JSON.

• PostgreSQL:

  • Added Postgres Bulk Upsert Snap that enables you to perform bulk insert or update operations (using the MERGE command) into the existing tables or any input data stream.

• Teradata:

  • Added Teradata Multi Execute Snap that enables you to execute multiple write statements as a single transaction for every input document.

• Kafka:

  • Enhanced the Kafka Consumer Snap with the Client ID field that correlates requests sent to brokers with each client and tracks the source of requests.

• ServiceNow:

  • Added Skip records without sys_id checkbox to the ServiceNow Query Snap that enables the Snap to ignore the records without sys_id. This checkbox is not selected by default for backward compatibility.

• When you provide a relative or absolute path to a directory in SLDB, the Directory Browser Snap displays the following warning:
  The provided file path format is not allowed
Resolution: Please provide the file path in this format /Org/ProjectSpace/Project/<file>. The following relative paths are also acceptable:
1] filename.json (stores the file in the directory from where the pipeline is running.)
2] ../shared/filename.json (file in project space shared)
3] ../../shared/filename.json (file in Org space shared)

This warning occurs because the Snap is designed to process file paths, rather than directory paths, so supplying a directory causes it to raise an incorrect alert.

• Enhanced the visual styling and color palette of Snap components to improve usability. Overall, the Snap background colors are lighter, and borders are slimmer compared to the previous release. The table below compares the updated Snap components with their earlier versions:

Selected Snaps: The border for the selected Snap has a thin inner border with a slight shadow in the new version.	Old Open	New Open
Disconnected Snaps: The disconnected Snaps are marked with a light green thin border in the new version.	Old Open
	New Open
Validated pipeline: The validated data output takes the shape of the peg (output type). Binary type: Rhombus Document type: Semi-circle	Old Open
	New Open
Non-validated pipeline: The inner peg border is slim and light in color in the new version.	Old Open
	New Open
Executed pipeline: The background color is light in color, and the borders are slim in the new version.	Old Open
	New Open
Failed pipeline: The background color of the failed pipelines remains the same; however, the external red border is slim and light in color in the new version.	Old Open
	New Open