Release 10.11

Explore the release highlights, usage notes, and known issues for Integration.


New features and enhancements Description
Maintain execution logs If you want to view the execution logs for a workflow, go to Workflow > Settings > Execution Settings and select the Maintain execution logs check box.
In previous releases, the Maintain execution logs check box was selected by default for all workflows. In this release, the Maintain execution logs check box is not selected by default for newly created workflows.
This mechanism is applicable for custom, cloned, and imported workflows.

Undo and Redo changes for workflows You can now undo the changes made to your workflow and redo the changes made by the undo operation. This is attained by using the Undo and Redo options on the workflow canvas.

API Reference Integration provides a robust set of APIs that allow you to programmatically integrate your own applications with Integration in a simple and secure manner. Integration APIs permit access to Integration functionalities and data in an authorized way to accomplish integration of systems and applications. The APIs are based on the REST architectural style and can be communicated using HTTP requests.
Publish on-premises connectors to Integration tenant You can now deploy connector assets that reside within the on-premises application to your desired Integration tenant using the Software AG Designer.
Support for SAP® ERP SAP® ERP allows you to extend your SAP business processes and integrate non-SAP products using open and non-proprietary technology. SAP® ERP allows for bi-directional and real-time communication to and from the SAP system.
Overwrite existing FlowServices while importing FlowServices functionality has been enhanced to overwrite existing FlowServices. A warning message appears during the overwrite process indicating that existing FlowServices will be overwritten.
User Interface enhancements Workflows and FlowServices are now available under the new Integrations tab for enhanced usability.

New connectors The following new connectors have been added in this release:
  • Amazon EC2 - Allows you to run applications on the AWS cloud and scale up or down their computing capacity on demand.
  • ARIS - Allows you to create the connection between ARIS and the runtime systems, for example SAP® or Oracle® systems.
  • Atlassian Jira - Allows you to perfrom tasks related to bug tracking and project management.
  • Google AI Platform Training - Allows you to build, deploy, and manage machine learning models in the cloud.
  • Hyper Text Transfer Protocol - Allows you to send HTTP or HTTPS requests to web servers from within the Integration environment.
  • Magento eCommerce Platform Bulk - Allows you to develop a flexible shopping cart system as well as complete control over their online store’s appearance, structure, and functionality.
  • Pastebin - Allows you to upload and share texts.
  • Pretty Good Privacy (PGP) - Allows you to encrypt, decrypt, sign, and verify the stream or bytes of data.
  • Salesforce Bulk v2 Data Loader - Allows you to quickly load large amount of the organization’s data into the Salesforce system and bulk query the information using the APIs provided.
  • SAP S/4HANA Marketing Cloud - Allows you to create or update CRUD operations on business objects using the OData-based REST interface, which lets you to do only bulk imports.
  • OAuth 1.0 Keys - OAuth 1.0 Keys is the in-built action provided by Integration to generate OAuth 1.0 parameters.
Map by array Index for Document and Document References The Array Mapping feature in Pipeline has been enhanced in this release to support index mapping for Document, Document List, Document Reference, and Document Reference List data types.
New services The following new services have been added in this release:
  • Flow
    • getLastFailureCaught - Returns information about the last failure that was caught by a CATCH step.
  • IO
    • close - Closes an InputStream or a reader object and releases the resources.
    • createByteArray - Creates a byte array of the specified length.
    • mark - Marks the current position in the InputStream or reader object.
    • markSupported - Enables you to test whether your InputStream or reader object supports the mark and reset operations.
    • Read - Reads a specified number of bytes from the InputStream and stores them into a buffer.
    • readAsString - Reads the data from a reader object and converts it to a string.
    • Reset - Repositions the InputStream or the reader object to the position at the time the mark service was last invoked on the stream.
    • skip - Skips over and discards the specified number of bytes or characters from the input stream or a reader object.
    • streamToReader - Converts a to a object.
    • stringToReader - Converts a string object to a String Reader object.
  • JSON
    • closeArrayIterator - Closes the iteration. The iterator object used in an iteration cannot be reused after this service runs.
    • getArrayIterator - Returns a batch iterator object.
    • getNextBatch - Gets the next batch of array elements by parsing the array paths in the iterator object returned by the getArrayIterator service.
Edit messaging subscribers The new Edit option provided for subscribers enables you to update existing subscriber information such as description, destination, and invocation details.
Earlier, you had to delete and recreate the subscriber to modify any fields. Now, you can directly modify the subscriber without having to recreate it.
Message routing The Message Routing feature enables you to define one or more routing rules for messages within a subscriber. Upon receiving a message, Integration evaluates each routing rule. When the rule criteria matches, the application initiates the business processes (invocates target) that is configured in the rule or initiates the business process specified in Default invocation.
Setting routing rules allows you to define the actions that must be taken after receiving a message without requiring manual intervention.
Options are provided for add routing rules in one of the following ways:
  • Workflows - Creating a subscriber and defining filters
  • Messaging - Creating a subscriber and defining routing rules
In addition, you can either modify, reorder, or delete routing rules for a subscriber.
Size limit for hybrid messages The maximum size limit for hybrid messages that can be transported between on-premises webMethods Integration Server and Integration is now 50 MB (52428800 bytes). If the message size exceeds the limit, compress the payload.
Tutorials The Tutorials section has been reorganized into generic and connectors related tutorials available in Software AG Tech Community.
Connector Monthly Releases (CMR) A new section is added for you to explore the release highlights, known issues, and usage notes for the Integration Connectors monthly releases.

Usage Notes

This section provides any additional information that you need to work with Integration.

Known Issues

This section lists the issues for this release that were known when this release readme was published.

This issue is related to deployment of SAP® ERP listener notification. If we deploy a project containing an SAP® ERP listener notification, the deploy wizard provides an option to create a new listener to associate with the listener notification. When a user tries to create a new listener, the Access is denied message appears.
Workaround: Close the deploy wizard and again deploy the project.

One routing listener is provided by SAP® ERP and is shared across projects. Routing listener notifications created using the shared routing listener are saved in a project. This allows the routing listeners to pass the data received to the matching routing listener notifications available across projects. However, it also makes it difficult to find the routing listener notification that processed the data.
Workaround: Create a routing listener notification with a unique combination of the sender, receiver, and message across the project. This ensures that only one routing listener notification across projects matches the criteria.

The httpPassword field in Routing Notification is stored as plain text.
The API response detailing routing notification for the httpPassword field is saved in plain text.
The API call is end-to-end encrypted and this API is called by authenticated users only.

Unable to edit imported action with created account.
An account name is associated with each SAP® ERP action. If the account with associated account name is not enabled in the project, the SAP® ERP action cannot be edited.
When an export/import function is used, the SAP® ERP action in the target project contains the associated account name.
However, the SAP® ERP account is not created in the target project.
Workaround: To edit the SAP® ERP action in the target project, do the following:
- If an SAP® ERP account with an associated account name exists in the target project, enable the SAP® ERP account in the target project and disable it in all other projects.
- If an SAP® ERP account with an associated account name does not exist in the target project, create and enable the SAP® ERP account in the target project.

In a transform pipeline, when both direct mappings and prediction mappings are present and you try to scroll the pipelineInput or pipelineOutput panel, the mapping lines are broken.
Workaround: Collapse and expand the direct mappings. The mapping lines will be repainted properly. This issue exists only when the scroll bar exists and you scroll either horizontally or vertically.

The icon position for adding a new FlowService step is not proper when the Expand All and the Collapse All buttons are used.
Workaround: Toggle the expanded state of the step on which the icon appears. This corrects the icon position when adding a new step.

Unable to create a REST API with JSON file.
This issue is observed when a REST API is created from a Swagger file, which has OAuth as the authentication scheme.
Currently, creating REST APIs from Swagger files which has OAuth as the authentication scheme is not supported.

Users are unable to update the custom time field under the Monitor tab with a simple click in Firefox browser.
Workaround: In Firefox, users can clear the time field value they want to update and re-enter the required value. Alternatively they can use any other browser to update the custom time field value with a simple click.

In the Database application, updating an Update operation leads to incorrect output.
Workaround: Once you add or delete the table columns or data fields, verify the input/output names and update the proper input/output names if they are not correct.

After logging out from Software AG Cloud, when a user logs in again using a different username and then navigates to Integration using the App Switcher, the user sees that the earlier user’s session has still not been logged out.
Workaround: Log out from Integration, instead of from Software AG Cloud.

Editing an imported workflow or FlowService having database application operations displays an error.
When a workflow or a FlowService is exported using the Integration export functionality, the connection name is not saved in the exported workflow or FlowService. On editing the database operation in the imported workflow or FlowService, the connection associated with the action is not found.
Workaround: The imported workflow or FlowService having database operations can be executed with a valid connection.

The SQL query in CustomSQL is parsed by the system using a third-party SQL query parser (FoundationDB SQL Parser) to populate the input and output. When the SQL query parser is unable to parse, the error “Failed to fetch Database Metadata” appears.
Workaround: If the input and output for CustomSQL operation is not populated, ignore the error and configure the input and output explicitly.

When you try to import a workflow that contains a Messaging trigger in another environment, the Messaging trigger is not imported.