Limitations of Infor AI Platform and RRS Integration

RRS only supports two Infor AI Platform endpoints: item-item.similarity and user-user.similarity. As of now, there is no option to add more Infor AI Platform endpoints.

For the input.params.mapping RRS tenant setting, only these two fields are supplied with actual values: ItemNumber, Customer. Other fields such as Quantity, OrderNumber, and ItemDesc are supplied with empty values when defined in the input.params.mapping.

Complete these steps to check what fields are used by Infor AI Platform endpoint:

  1. Sign in to your Mingle tenant.
  2. From the application tray, select Rhythm Services.
  3. On the Available APIs, select the Infor AI Platform.
  4. On the COLEMANAI/aiplatform endpoint, click the Document icon under the Documentation column.
  5. Click GET/v1/endpoints/{endpoint}/schema.
  6. Click Try it out.
  7. Specify the Infor AI Platform endpoint name. For example, recUPCELLitems.
  8. Click Execute.
    Example of a Response body:
    {
      "type": "object",
      "properties": [
        {
          "name": "Customer",
          "schema": {
            "type": "string",
            "nullable": true
          }
        },
        {
          "name": "ItemNumber",
          "schema": {
            "type": "string",
            "nullable": true
          }
        },
        {
          "name": "Quantity",
          "schema": {
            "type": "integer",
            "nullable": true
          }
        }
      ]
    }
    

    For this example, it has the fields in this order: Customer, ItemNumber, Quantity

    Only the ItemNumber and Customer are supported.

    The payload that is sent to Infor AI Platform is similar to this code with the unsupported fields left empty:
    {
    "data": [["CLD-CUST1","Y00001", ""]]
    }
    

    You can verify the items displayed in Rhythm by running the POST /v1/endpoints/{endpoint}/prediction in the Infor AI Platform documentation.