🐞 Bug Fixes

• Fixed missing file function errors in Gloop services
  Resolved an issue where Gloop services encountered errors due to incomplete type resolution when processing certain generic types. (MR-8949)

  Details:
  The fix enhances generic type argument resolution in the runtime, specifically addressing cases involving primitive arrays (e.g., byte[], int[]) and multi-dimensional arrays. Previously, the resolver only supported limited type scenarios (e.g., ClassType, TypeVariable), leading to failures when encountering other valid signature types.

  The implementation refactors typeArgumentToType and objectTypeArgumentToType in JavassistUtils, introducing a fallback to signatureTypeToType to ensure all valid type arguments are correctly resolved.

This release introduces no new features. We recommend upgrading to v2.7.2 to ensure stable execution of Gloop services, especially for workflows and services that rely on generic types with array-based inputs.

• MR-8949 - Missing file functions causing gloop service errors

However, the current approach of locking down the marketplace—combined with limited or no response to community inquiries—creates a significant obstacle to delivering this value.

For a tool like the Groovy linting extension to be effective, it must be easily accessible to developers through the marketplace. Restricting access prevents adoption, limits visibility, and ultimately diminishes the impact of solutions that are designed to improve the platform itself.

At the same time, the lack of support and engagement from administrators compounds the problem:

• Questions about integration, compatibility, and deployment remain unanswered

• Developers lack guidance on publishing or distributing extensions

• Potential contributors are discouraged due to uncertainty and lack of feedback

This directly affects the success of the Groovy linting extension. Without a responsive support channel or a more open marketplace, even well-built tools struggle to reach their intended users.

There is also a broader implication. Extensions like the Groovy linter represent opportunities to strengthen the Martini ecosystem by:

• Enhancing developer experience and efficiency

• Promoting best practices and code consistency

• Encouraging community-driven innovation

Yet these benefits cannot be realized if contributors face barriers to distribution and communication.

To move forward effectively, the following improvements are critical:

• Improve responsiveness to community inquiries, especially those related to extension development and publishing

• Provide clearer guidelines and support channels for marketplace contributions

• Reevaluate marketplace restrictions to allow controlled but practical access for tools that add value to the ecosystem

• Consider AI-assisted support to ensure inquiries are acknowledged and addressed in a timely manner

In summary, the Groovy Linting Extension for Martini Designer Desktop is not just a standalone tool—it is an example of how the ecosystem can evolve through community contributions. Enabling access and providing support are essential steps to ensure such innovations can succeed and deliver value to all users.

Implementing an AI agent to handle community inquiries provides an immediate and scalable solution to this problem. An AI-driven system can:

• Ensure timely responses by providing instant replies 24/7, eliminating long waiting times

• Improve user experience by acknowledging concerns and guiding users toward solutions

• Reduce operational load on administrators by handling repetitive and common inquiries

• Maintain consistency in responses, ensuring accurate and standardized information delivery

• Capture insights from user interactions to identify recurring issues and improve services

In the absence of consistent human support, an AI agent serves as a reliable first line of communication. It ensures that the community feels heard and supported, even when administrative resources are limited.

Ultimately, deploying an AI agent is not just a convenience—it is a necessary step to uphold service quality, maintain user trust, and ensure the platform remains responsive and user-focused.

🛠️ Bug Fix

• AI Features Activation Issue Resolved
  Fixed an issue where AI features remained disabled even after successfully completing the AI Setup Wizard. Users can now access AI functionality immediately after setup as intended.

• MIDE-2601 - AI features remain disabled even after completing AI setup wizard

Martini Designer v1.5.0 is a major step forward in AI-assisted development, workflow automation, and API design. This release introduces powerful new Designer Agent capabilities, expanded workflow node support, stronger API tooling, and significant stability improvements — all designed to help you build faster and with greater confidence.

🤖 A More Powerful Designer Agent

The Designer Agent takes center stage in v1.5.0 with expanded creation, editing, and automation capabilities.

Create & Edit with AI

• Generate and edit workflows directly through the Designer Agent

• Create REST APIs with workflow handlers automatically

• Generate and send HTTP requests using AI

• Generate and edit data mappings via Ask AI in the mapper

• Generate model expressions with ease

• Automatically generate package documentation

Agent Diff & Transparency

• View diffs for AI-proposed changes across:

  • Workflows

  • Data models

  • REST APIs

You stay fully in control while leveraging AI acceleration.

Workflow Agent Expansion

The workflow agent now supports a wide range of nodes, including:

• Invoke Service

• Invoke Workflow

• Wait Time

• Wait Event

• Random

• MongoDB Query

• Email Trigger

• Directory Watcher Trigger

• JMS Listener Trigger

• Retry in Try-Catch

• Repeat node filter conditions

This dramatically expands what can be generated and automated through AI.

🔗 Enhanced API & Integration Capabilities

v1.5.0 significantly improves HTTP, authentication, and API tooling:

• Lonti authentication support

• OAuth 2.0 Header Prefix configuration

• Generated headers visibility in HTTP editor

• Store authentication as package properties in ad-hoc services

• Update GraphQL API schemas

• Select specific operations from API schemas in the marketplace

• Send HTTP requests and run workflows via built-in tools

• Retrieve Martini runtime logs directly

Integration workflows are now more secure, flexible, and transparent.

🧩 Smarter Workflow Design Experience

We’ve improved usability and configurability across the workflow builder:

• Hover-based Configure button for steps

• Scheduler trigger delay configuration

• Workflow node comments

• Auto-reveal support in navigators

• Reveal in Navigator from search results

• Improved schema validation for workflow agent

• Smarter node connection behavior when dragging

Building complex automation flows is now more intuitive and error-resistant.

🔍 Improved Search & Developer Productivity

Developer productivity gets a boost with:

• Double-click Groovy methods to open directly in editor

• Search support for triggers and database connections via API

• Reference search inside Groovy files

• Create CQL/SQL query files from database schema tables

• Improved Ask AI context access in Problem View

• Editable previous Ask AI messages

Everything you need is easier to find, access, and modify.

🎨 Refined UI & Experience Improvements

We’ve enhanced polish and consistency across the platform:

• Improved alignment of icons, checkboxes, toolbars, and radio buttons

• Cleaner AI Chat wizard text

• Streamlined agent architecture (Ask & Edit modes unified)

• Better messaging in Data Mapping tab

• Improved license validation timing during startup

• Smarter user edit behavior in Users & Groups

The result: a smoother, more predictable design experience.

🛠 Major Stability & Bug Fixes

This release resolves a large number of workflow, editor, HTTP client, deployment wizard, and UI-related issues, including:

• Workflow opening errors

• HTTP response tab inconsistencies

• GraphQL and REST configuration bugs

• Drag-and-drop issues (including Linux support)

• Content assist and auto-completion fixes

• Word wrap editor boundary issues

• Deployment wizard problems (Windows included)

• Data model JSON schema creation issues

v1.5.0 delivers stronger stability across core Designer functionality.

• Version 2.7.1

Stories completed

• MIDE-1440 - Open groovy methods in code editor when double clicking it in the navigator

• MIDE-1504 - Add support for searching trigger and database connection names via the search API

• MIDE-1576 - Add Header Prefix field to HTTP request editor Oauth 2.0 form

• MIDE-1577 - Add a way to show generated headers in request editor header table

• MIDE-1591 - Add Reveal in Navigator support in Search view results

• MIDE-1621 - Add a way to generate model expression in set expression dialog

• MIDE-1669 - Add support for workflow node comments

• MIDE-1854 - Support importing extra properties via JSON in run dialog

• MIDE-1902 - Add support for Lonti authentication in HTTP Requests

• MIDE-1908 - Implement auto reveal for the navigators

• MIDE-1946 - Add support to select operations to consume from an API schema in the marketplace

• MIDE-1968 - Add support for generating HTTP request using the Designer agent

• MIDE-1969 - Add support for Ask AI in mapper to generate and edit mappings

• MIDE-1971 - Add support for creating and editing workflows via Designer agent

• MIDE-1975 - Add "Configure" button on hover or selection of steps

• MIDE-1996 - Support updating GraphQL API editor schema

• MIDE-2025 - Add support for storing authentication details as package properties in generated adhoc HTTP services

• MIDE-2039 - Add support for configuring delay of a scheduler trigger

• MIDE-2045 - Support diff for agent proposed changes of workflow, data model and REST APIs

• MIDE-2051 - Add support filter condition for repeat node of workflows

• MIDE-2052 - Add support for retry in try catch node of workflows

• MIDE-2067 - Add support for invoke service node in workflow agent

• MIDE-2068 - Add support for invoke workflow node in workflow agent

• MIDE-2069 - Add support for wait time node in workflow agent

• MIDE-2070 - Add support for wait event node in workflow agent

• MIDE-2071 - Add support for random node in workflow agent

• MIDE-2072 - Add support for MongoDB database query node in workflow agent

• MIDE-2073 - Add support for creating REST API with workflow handlers via Designer agent

• MIDE-2076 - Add support for email trigger node in workflow agent

• MIDE-2077 - Add support for directory watcher trigger node in workflow agent

• MIDE-2078 - Add support for JMS listener trigger node in workflow agent

• MIDE-2091 - Implement tool to get the logs from Martini runtime

• MIDE-2092 - Implement tool to send HTTP request

• MIDE-2093 - Implement tool to run workflow

• MIDE-2095 - Support generating package documentation with the designer agent

Improvements made

• MIDE-1554 - Hide some of the root data model configuration fields

• MIDE-1757 - Support reference search results in groovy file

• MIDE-1898 - Add support for creating CQL/SQL query file from a database connection schema table

• MIDE-1950 - Modify messageAttributes properties of AWS SQS Listener Trigger node

• MIDE-1956 - Check the license during the application startup instead of after the UI is displayed

• MIDE-1965 - Add Ask AI context menu item to the problems of the problem view

• MIDE-1997 - Show previous messages in the Ask AI input and support editing last message

• MIDE-1998 - Remove "Configure" button from Input/output toolbars

• MIDE-2015 - Clicking on Add User while editing a User with changes does not prompt for discarding changes/saving

• MIDE-2035 - Show message about the Data Mapping tab in the database node query tab

• MIDE-2036 - Improve alignment of user form icon buttons

• MIDE-2038 - Improve AI Chat wizard text

• MIDE-2040 - Do not auto connect workflow nodes on dragging if the node is already connected to the source or target node

• MIDE-2042 - Improve styling alignment of all checkboxes, toolbar items and radio buttons

• MIDE-2075 - Hide sub chat agent in chat input that are not meant to be used directly by the user

• MIDE-2116 - Refactor agents to only keep the Designer agent with Ask and Edit mode

• MIDE-2118 - Improve workflow schema validation for workflow agent

• MIDE-2119 - Update workflow agent prompt for try catch node to include the new configuration fields

Bugs fixed

• MIDE-1585 - Using the "." key on a workflow throw an error due to content assist or wrongly opens the content assist

• MIDE-1604 - The delete button in model tree widget toolbar is always enabled when it first appears

• MIDE-1606 - Leaving an integer property with null value throws out error.

• MIDE-1656 - Prompt to Discard changes appear for Fork and Script step

• MIDE-1658 - Deleting a header while editing one throws an error

• MIDE-1676 - Clicking on the skeleton loader of Martini Designer causes it to throw an error

• MIDE-1724 - Range validation for character properties does not work.

• MIDE-1805 - Find button in Workflow's mappers triggers the Find for the whole workflow

• MIDE-1855 - Doing multiple right clicks in a workflow's empty space changes the context menu's display

• MIDE-1923 - Configure button is hidden if the comment on the property is too long

• MIDE-1929 - Text editor goes out of bounds when Word Wrap Setting is on wordWrapColumn

• MIDE-1947 - Auto completion in scripts and expressions add an extra $ for proposals which starts with $

• MIDE-1990 - Toggling the Bottom panel while an Embedded Text Editor is opened cuts the written text in the Editor

• MIDE-1995 - Find widget blanks out when re-toggled

• MIDE-2000 - Cannot DnD local filesystem directories into a package in Navigator

• MIDE-2005 - Pressing the Alt + Arrow Up/Down shortcut while editing a table cell cancels the edit and moves the item

• MIDE-2011 - Navigating through command palette search results is not working

• MIDE-2013 - User & Groups Wizard Edit Panel's layout is cut off on initialization

• MIDE-2014 - Deleting the currently focused user (being viewed/edited) does not close the edit panel

• MIDE-2029 - Save Changes Dialog repeatedly appears after switching users and discarding changes in Users and Groups dialog

• MIDE-2044 - Error when opening a workflow

• MIDE-2054 - Requests done from another request tab affects the response tab of other request tabs

• MIDE-2055 - Cannot drag and drop to workflow editor canvas on Linux

• MIDE-2056 - Refactoring properties with the same name affects input set expressions

• MIDE-2057 - Adding URL Path in REST configuration of a Service leads to a blank request body in HTTP Client

• MIDE-2059 - Cannot send HTTP request with file on desktop

• MIDE-2081 - Cannot create data model from JSON schema

• MIDE-2086 - Deployment wizard's Next button disable feature not working as intended

• MIDE-2088 - maxArraySize being assigned with the value of minArraySize

• MIDE-2101 - HTTP Response disappears after making a request and switching back to the tab

• MIDE-2104 - Error when using deployment wizard on windows

• MIDE-2112 - Todo list tool sometimes throws errors when rendered which breaks the chat view

🐞 Bug Fixes

• Fixed issue consuming Adhoc REST/HTTP APIs when loadUrl is set to true
  Adhoc REST/HTTP APIs can now be consumed correctly with loadUrl enabled. (MR-8872)

• Resolved REST API routing issues with "/" base path or operation path
  REST APIs configured with a root ("/") base path or operation path now function as expected. (MR-8886)

• Corrected 404 error when setting global or operation-level consume type for GET requests
  Adding a consume type no longer causes GET operations to return 404 errors. (MR-8887)

• Fixed failure to generate data model from JSON schema
  Data model generation from JSON schema now completes successfully. (MR-8900)

This release introduces no new features. We recommend upgrading to v2.7.1 to benefit from improved REST API stability and schema processing reliability.

• MR-8872 - Cannot consume Adhoc REST/HTTP API with loadUrl set to true

• MR-8886 - Fix REST API not working with "/" base path or operation path

• MR-8887 - Adding a global or operation consume type make a GET operation return 404

• MR-8900 - Unable to generate data model from Json schema