Infor Technology Blog

« | Main | »

Infor OS Update – April 13 2018

April 13, 2018

April 13th marks the following new feature roll-out to users of Infor OS Cloud Edition (CE).

iPaaS (Infor ION & Infor ION API gateway)

  • ION Connect:  The IMS interface for sending and receiving documents can now be used via the ION API Gateway. In hybrid scenarios where ION is in the cloud and the application is in an external network, this feature allows the application to interface with ION directly without having to install any Infor component in their network. This scenario is often referred as ‘Zero foot print’ integration. To receive messages, the application can also expose its IMS interfaces through the ION API Gateway that can be called by ION.*
  • ION Connect: In database connection points of type AnySQL you can now use the DB2 database.
  • ION Connect: When using AnySQL models in a database connection point, you now have the option to either use JSON arrays or line-delimited JSON (also known as JSON Streaming or JSON Lines).
  • ION Connect: The ION API Connector can now handle deflated responses from an ION API method. If the http header indicates Content-Encoding: deflate, then ION will inflate the data before sending it to the next step in the document flow.
  • ION Connect: You can now install and run multiple Enterprise Connectors on a single host. This is useful if you have applications for multiple tenants (such as test and production) deployed on a single host and you want to connect these to multiple Infor OS cloud tenants.*
  • Mapper: In the function editor, when using a global user-defined function (UDF) in the function editor, an copy of that UDF will be created in the mapping you are editing. This allows you to edit the function, and it avoids problems when importing the mapping into an environment where the global UDF does not exist.
  • Mapper: Switching from a graphical mapping to the advanced XSLT edit mode has been improved. When typing XSLT code, you will be asked whether to switch to advanced mode. You can cancel the action, which will revert your changes.
  • Mapper: The version comparison was improved. When switching on the comparison, you will immediately see the differences with the previous latest version (but you can switch to another version if needed). Additionally, an option ‘Custom Code’ exists, which enables you to compare the current version to any XSLT that you paste in the text area. When comparing, up and down arrows are available to walk through the differences.
  • Decision Services: When exporting a matrix to CSV, the column having the date and time is renamed from ‘DATETIME’ to ‘DATETIME (UTC)’, to indicate that the date and time are always in UTC format.
  • Data Catalog: In addition to normal JSON, you can now also select line-delimited JSON (also known as JSON Streaming or JSON Lines). You can use this if your data objects contain multiple JSON instances are line-delimited rather than combined in a JSON array.
  • OneView: Event names to be BOD-agnostic Event names in OneView were referring to BOD terminology even if they also applied to other document types, such as JSON or ANY. This is corrected now.
  • Data Lake: In the Settings > Configuration > Storage Policy page, the Infrequent Access option is removed. From now on, Data Lake data will remain in the normal storage until it is moved to Long-Term Storage.
  • ION Desk UI: From now on the patch number is shown in the ‘About’ information from ION Desk, to provide more details on the version that you are using. Instead of version ‘12.0’ it will show ‘12.0.22’, for example.

A similar set of features is available in the 12.0.22 release for on-premise customers. A full list of new features, bugs fixed, and other documentation can be found on Infor Xtreme.  Learn more about Infor OS here or contact us anytime.

Don’t see a feature you want?  Log into Infor Xtreme and click on Resources > Enhancement Requests.  You can enter your own and vote for others.

* = only available in the cloud edition


Leave a Reply

Your email address will not be published.