Upgraded the Executions page interface to include a visual representation of the Mapper step, inspired by the design on the Flow Queues page. This enhancement offers users a more structured and organized view of the mapper step within the thread context, enhancing clarity and accessibility of information.
Implemented a timestamp display feature on the Step Execution Error page to give users clear context and information about the timing of the error occurrence.
Enhanced the contract list interface by introducing a dedicated “Search” field, enabling users to swiftly locate desired contracts for easy access. With this new feature, users can input search queries to filter and display specific contracts, facilitating quick and convenient retrieval of contract information.
Implemented a “Search” field for searching workspaces, complete with paging support to enhance usability and efficiency. This new feature empowers users to enter search queries to find specific workspaces, with the ability to navigate through multiple search results using pagination.
Enhanced the spam prevention strategy within the webhook microservices to address repeated attempts from third-party systems to send events to inactive or deleted flows.
Upon detecting 10 consecutive requests to an inactive or deleted flow(status code error 404: Flow XXXXXXXXXXX either does not exist or is inactive), the system now responds with a status code error 409, indicating that the flow has been blocked due to excessive calls. The error message specifies Flow XXXXXXXXXXX was called while inactive or deleted more than 10 times, providing transparency to users.
Note: To unblock the flow, users are required to manually run it, ensuring responsible flow management and system integrity.
View All Workspaces page in the UI.Warning for a step via the UI.Other Contract Workspaces section when the user had the Member role in the contract.1.2.0Get New and Updated Objects Polling TriggerUpsert Object Action1.6.2component-commons-library version to 3.2.1Sailor version to 2.7.4Size of Polling Page value resulted in a validation error instead of reverting to the default setting1.7.0component-commons-library version to 3.2.1Node engine to version 20.xSailor version to 2.7.4Verify Credentials by adding validation to reject admin panel URLs in Magento configurationGet New and Updated Objects Polling TriggerLookup Objects ActionLookup Object by ID ActionDelete Object by ID ActionMake Raw Request ActionLookup Objects Action