Introduction

With the InContext Modeler you can create an integration between Infor LN and several Infor OS Portal or Infor Ming.le context widgets/applications. This integration is based on so-called context messages. In those context messages the characteristics of the Infor LN objects, which have focus in the UI, are sent to the context widgets/applications. Those context widgets/applications have functionality to display the data that is related to the Infor LN objects.

Integration examples:

• An address of a Business Partner (BP). When you look up this BP, the Map context widget/application will show the location.
• A Sales order can have many documents attached. This also applies to the BP for which the Sales Order applies. The Related Information context widget/application shows both the documents attached to the Sales Order and the BP.

This screenshot shows an example of the integration between an LN session and the Map context widget/application:

Different web parts may be interested in different context message types. The Map context widget/application, for example, is interested in a message that contains the address information. A Package Tracker context widget/application is interested in a tracking number. The Related Information context widget/application is interested in the id-fields of the current object.

The InContext Modeler is used to specify which context messages must be sent by a session and how the content of those messages must be filled. No changes are required in the source code of the standard session. This implies that you even can define your own context message types for own developed context widgets/applications and get this running without the need of customizing the standard sessions.

This guide will help you to use the InContext Modeler for making (small) changes to existing models, but also for generating completely new models for your own developed tables and sessions. The overall development procedure is described in Development procedure.

In the development process for InContext messages, there are two models. The first one is the InContext Reference Model (IRM). This model contains the relations between tables and context message types. This model is generated based on the tables in the LN Data Dictionary and the defined context message types. For more information on the IRM, see InContext Reference Model (IRM). The second model is the Incontext Implementation Model (IIM). It contains models for tables and sessions and generated 3GL libraries for the sessions. How the IIM can be generated is described in Incontext Implementation Model.

After the IIM is generated, the generated models in the IIM can be changed. Changes can be made by editing the models in Infor LN Studio. After regeneration of the InContext Library, the changes are active. The process of changing the models can be found in Model editing.

The runtime architecture is described in Runtime architecture.