Infor Technology Blog

« | Main | »

Infor Document Management – What’s new in 12.0

July 5, 2016

By Jorgen Andersson, Product Manager – Infor Document Management

Infor Document Management (IDM) 12.0 was released this last spring and includes a number of enhancements that may interest our readers.  For more details see the Net Change Report that is available on Infor Xtreme.

Support for MS SQL Server

With the Infor Content Repository support for Microsoft SQL Server, the Infor Technology Stack can now run on a common, well known database platform. IDM with the Infor Content Repository can still run on PostgreSQL.

Note: It is highly recommended that you use PostgreSQL Plus Advanced Server for any production environment because PostgreSQL community (free edition) comes without support.

Enhanced ION integration

The enhanced ION integration in IDM enables the CaptureDocumentBOD (used for capturing, for example scanning, documents) and introduces support for ION Workflow BODs, which enables an IDM user to launch a specific workflow for a specific document. Previously, it was possible to notify ION about changes to a document and then configure ION to launch a specific workflow as a reaction to that change. The enhanced ION support also enables creation of documents by the use of the ContentDocumentBOD, enabling other systems to create documents in IDM by sending a ProcessContentDocumentBOD.

Integrated Capture solution

IDM is integrated with Ephesoft, and the ability to capture documents is added as a feature to IDM, seamless to other systems. If IDM is supported by another system, that system can also use the capture feature in IDM through Ephesoft.

.Net API

With this version of IDM, the IDM .Net-based API is released and can be accessed through the information page of IDM (http://idm-server:idm-port/ca) where you can download the API for your version, download sample code, and get access to the API documentation. The .Net API should be the first choice for any .Net-based application that requires integration code with IDM.

Attribute level permissions

The Attribute level permission feature enables attributes to have a different security model compared to other attributes and the actual content (file) of the document. This can, for example, be used to control a “Status” attribute where only some can control its value. This feature can also be used to give users access to edit some attributes but not the ability to edit the content/file of the document.

Configuration export/import

Being able to import and export the configuration of IDM helps when you set up secondary systems, such as your TEST or DEV environments, where you want a copy of your production environment. It also helps when you migrate your system to a new server or between versions/editions.


The new IDM Batch API helps integrating developers to run multiple actions on documents in IDM. For IDM editions that support transactions, you can use a transaction around the entire batch of actions and roll them all back if something fails. The different document actions that can be used in the Batch API are:

  • Add
  • Update
  • Delete
  • Search
  • Count
  • Check out/in/undo

You can run 100 operations in one batch, and depending on the operation type (which document action), each operation can contain up to 100 document actions. For example, you could run 10,000 searches in one batch (100 operations * 100 document actions). The order of the operations and document actions are guaranteed so that you can run multiple document actions on the same document, one after the other.

See the IDM API documentation for more information about the Batch part of the API.

Note: You must consider that the batch transaction as well as the entire batch method may time out when working with many documents and/or document actions.

Minor enhancements

Other changes to IDM include:

  • Enhancements were made to the Business Context Messages so that you can automatically set attribute values to fields from your ERP but still be able to change them in IDM without losing the connection between the ERP entity and the Document in IDM. Previously, you could only set key attributes. Changing them would result in a broken relation. You can now also set the ACL (access control list) on the document by using data from your ERP to make your security model easier to maintain.
  • With the ability to multi-select in the client, it is now easier to work with many documents at one time. Select several to delete, check in or out, and so on.
  • The ability to sort search results in the client by columns makes it easier to find your documents quickly.
  • The addition of Thai to IDM opens new markets.
  • The M3 Event Hub integration has been enhanced with the ability to set the ACL on documents from data sent by M3. This feature is similar to the enhancement of the Business Content Message.

Caution: The classic IDM (DAF) Java API was deprecated in version 10.0.3. If you are using Infor Smart Office 10.2, you must be on IDM v10.1 or later. If you upgrade to IDM v11.1 or later, you must upgrade to Smart Office 10.2 or later. Any IDM integration that is based on the classic DAF API will stop working when you upgrade IDM to version 11.1 or later.

This release also contains performance improvements, discrepancy corrections, and usability enhancements.

For more information on Infor Document Management or other Xi Platform Technologies contact your Account Executive or contact us.


8 responses to “Infor Document Management – What’s new in 12.0”

  1. Ajesh Alvoor says:


    Can i have more information on IBCM(Infor Business Context Messaging)? How does it works etc?


  2. Heath says:

    Hey Ajesh,

    If you would like I can share some documentation with you on the Infor Business Context. Feel free to reach out via email.

  3. Saradhi says:

    Hi ,
    Please provide some documents on how to configure Documentation context application for M3 H5

  4. Gagan Shidhay says:

    Hi Heat,
    I need documentation on Infor Business Context.
    Please share that with me.

  5. Gabrielle Dixon says:

    Can this be used as a form document. and imported into SXe?

    That is for Price Discount records:

    can a user enter data on a form and that form go through an approval workflow which then imports into SXe?

  6. Heath Branum says:

    Yes that is correct. We call this service Document Output and SX.e was one of our first adopters. You can reach out to the SX.e team to find a list of document types that they support out of the box.

  7. nominal says:

    Great post. I’m dealing with a few of these issues as well..

Leave a Reply

Your email address will not be published.