Creating custom context messages

  1. Click the Data files tab in administration tools and select the Configuration file type.
  2. Select the ContextApplicationsConfiguration.json file and click Export.

    The ContextApplicationsConfiguration.json file is used to manage the Context Messages that you can publish in H5 Context Publisher. The file contains an array of JSON objects. Each JSON Object should contain these elements:

    • uid: A unique ID (any unique value) for the Context Message.

    • title: The menu item that is displayed in the Context Publisher Sub-Menu (any value).

    • type: The message type for the Context Message. This type should match the expected message type of your Infor Ming.le Context applications or Infor OS Portal Context widgets.

    • data: The data template for the Context Message. This template should match the expected data structure of your Infor Ming.le Context applications or Infor OS Portal Context widgets.

    See this sample of a ContextApplicationsConfiguration.json file:

    
[
            {
                       "uid" : "M3_BC",
                       "title" : "Currency Converter",
                       "type" : "currencyExchange",
                       "data" : {
                                       "baseCurrency" : "USD",
                                        "baseValue" : "1",
                                        "targetCurrency" : "EUR"
                       }
            },
            ......

]
    Note: Do not change or remove the entry with the uid=M3_BC because it has a special function in the Context Publisher.

    ", ......" indicates where you can add other valid JSON array of objects. If there is only one object in the JSON array, you should remove this.

  3. Open and edit the file by using a text editor.

    We recommend that you use a text editor that supports json and json formatting.

  4. Validate the son format in the editor, if possible. You can use Notepad ++ with JSON Viewer Plugin which is an open source free tool for Windows.
  5. Return to Data files and select Configuration category.
  6. Import the file that must be named ContextApplicationsConfiguration.json.

    The existing file is replaced.

    Note: The file name must be ContextApplicationsConfiguration.json. All other files are ignored in this Configuration category.