Magic xpi 4.13.2
Release Notes
In this release of maintenance version of Magic xpi 4.13.2, we are delighted to offer you enhancements on top of the existing features.
New Features
Microsoft Dynamics 365 for Finance and Operations Connector
Magic xpi has introduced a new Dynamics 365 Finance and Operations connector which enables integration with Microsoft Dynamics 365 APIs.
This connector offers the following features:
A query wizard to build complex queries while still allowing the user to manually enter and modify queries
Cross-company support to fetch the data from the user's default company or all the companies accessible to the user
Support for Dynamics 365 CE module Local Agent Compatibility
File Watcher
The File Watcher is a new trigger to monitor the files created on the file system. It provides support for Local Agent.
The trigger supports two types of file systems, Disk and FTP. The Disk option includes physical as well as network storage. For the FTP option, the SFTP protocol is supported.
This trigger can perform Move, Delete and Rename operations on the files.
2
Enhancements
API Support
The Salesforce and ServiceMax connectors are now upgraded to support the API version 51.0.
FTP Local Agent Compatible
The FTP connector is built using the new SDK and provides Local Agent support.
Read Interface in SAP ERP
The SAP ERP component has a new interface type Read which introduces two new operations namely Query and Table. The Query read operation is performed using the RSAQ_REMOTE_QUERY_CALL function and the Table read operation is performed using the RFC_READ_TABLE function. Users can also define filter criteria for selected columns and provide additional custom filters.
Behavior Change
The TIMESTAMP field in the Data Mapper is now shown as Alpha type instead of DATE type. For the projects migrated from Magic xpi 4.7.x to 4.13 and above, to extract the DATE portion of the TIMESTAMP, use the DVal function in the Data Mapper. This change has to be done manually.
Migration/Upgrade Considerations
The project build may not work at Command Line for a project with an FTP component after upgrading or migrating it to the Magic xpi 4.13.2 version. To resolve this, open the project in the Studio once for any migration activity that may be needed.
3
Known Issue
SAP B1 resource may fail to validate for SAP B1 V10 with MSSQL database. To fix the issue, install SAP B1 and MSSQL database before installing Magic xpi.
The Dynamics CRM Resource helper will not be able to retrieve the Organizations List for the On-Demand Deployment Type due to discontinuation of the Discovery service from Microsoft. As a solution enter the name of the Organization manually or select the Environment Variable that contains the same.
It is mandatory to have the Magic Monitor password as Alpha-numeric combination. Numbers only password will fail. For example, password 1234 is invalid and A1234 is valid.
The FTP DAM methods File Exists, Get Operating System and Directory Listing are not supported in a single step when the FTP resource is configured with Local Agent value as True.
In some scenarios, it has been noticed that the Dynamics CRM component gives an error "Arithmetic operation resulted in an overflow" when fetching the data from the server.
4
Here is a list of your important issues that have been addressed in this release.
Fixed Issues
Issue ID | Description |
MXPI-13968 | In the Magic Monitor, when the Date & Time column in the Activity Log was |
used for sorting the logs, the order got mixed up. | |
MXPI-16305 | The Magic Monitor did not show any errors and the error code and error |
description were not updated for the DCRM component. | |
MXPI-16399 | The Salesforce component gave an error, "Premature end of file" when |
performing the UPSERT operation in the Data Mapper. This can now be | |
fixed by adding a logical name IncludeEmptyRootElement with value as Y in | |
the logical names. | |
MXPI-16572 | On migrating a project from Magic xpi 4.9 to 4.13, the SAP ERP steps |
failed to work if they used a dynamic resource. | |
MXPI-16858 | The REST Client Get operation failed, when the URL was constructed using IP |
address instead of HostName. To skip the host name verification, add an | |
underscore (_) character as a suffix to the HTTP protocol. | |
For example, HTTPS_:\ | |
MXPI-16881 | The detailed annotations of all the nodes were missing from the GSA XML |
configuration files in the gsa directory of GigaSpaces making configuration | |
a difficult task. | |
MXPI-18223 | The Web Services Client component failed to invoke a particular service |
with a "Web Service Client invocation failed | |
java.lang.NullPointerException" error. | |
MXPI-18722 | The Insert operation for column name ending with dot (.) character in the |
Data Mapper failed. This can be fixed by wrapping the column name in | |
square brackets ( [] ). | |
MXPI-18770 | A particular project got restarted when deployed in cluster of four servers. |
MXPI-19002 | The Web Services Client component showed a higher latency for particular |
projects invoking a JDE Web service. | |
MXPI-19030 | For a particular project configured with the Websphere MQ trigger, the |
workers in the Magic xpi runtime went into an unresponsive state resulting in | |
the Magic xpi server crash. | |
MXPI-19110 | The Web Services Client component failed to invoke a particular service |
with an error "Web Service Client invocation failed | |
java.beans.IntrospectionException: Method not found: setCCustos". | |
5
This is an excerpt of the original content. To continue reading it, access the original document here.
Attachments
- Original document
- Permalink
Disclaimer
Magic Software Enterprises Ltd. published this content on 04 October 2021 and is solely responsible for the information contained therein. Distributed by Public, unedited and unaltered, on 05 October 2021 14:18:03 UTC.