Handlers

REST handler

See the REST chapter for details. See the Example - Projects topic for the complete Hello World example.

GraphQL handler

See the GraphQL chapter for details. See the Example - Projects topic for the complete GraphQL example.

Scheduled handler

Trigger the service based on a schedule defined by a cron expression.

The cron expression consists of five space-separated values: Minutes, Hours, Day-of-month, Month, and Day-of-week.

Define the cron expression for the deployed service in the service manifest. Define the local debug expression in local.settings.json.

The service runs at the zero second of the specified minute. Supported granularity ranges from minutes to yearly intervals. Time uses UTC in 24-hour format.

The baas-manifest.json and local.settings.json files include a tooltip with a dynamic description of the cron expression.

To update the schedule, open the command palette (F1) and select BaaS - Set Schedule Expression in Service Manifest.

[Schedule expressions](https://en.wikipedia.org/wiki/Cron#CRON_expression)

Storage handler

Trigger the service when data changes in storage. Use this handler for file processing scenarios. See the Example - Projects topic for the Storage Trigger example.

Queue handler

Trigger the service from a queue to process incoming messages. See the Example - Projects topic for the Asynchronous Job example.

Enterprise orchestrator handler

Trigger the service from Enterprise Orchestrator (EO). The service processes input variables and returns output variables to the EO symphony.

When you use the Enterprise Orchestrator handler, enable the API Service in the manifest. If the service does not call a specific API suite, specify the BaaS service itself.

See the Enterprise Orchestrator topic for details.

ION connector handler

The ION Connector handler enables bi-directional message integration between external systems and Infor Operating Network (ION).

Use this handler to send documents to ION and receive responses for processing or routing to other services. You can also trigger document sending using webhook patterns from external systems.

The ION Connector handler requires the Queue handler. When ION triggers the service, documents are placed on the service queue for processing. Logs for the ION Connector handler are available under the Queue handler.

The timeout, memory, and concurrency settings defined for the Queue handler also apply to the ION Connector handler.

Configure all supported ION documents in the service manifest. ION uses this configuration when creating the connection point. You can configure multiple documents and specify whether they are inbound, outbound, or both.

        "ionConnectorHandler": {
        "enabled": true,
        "documents": [
        {
        "name": "Sync.TestBOD",
        "type": "BOD",
        "subType": null,
        "retrieve": true,
        "send": true
        }
        ]
        }
      

Supported document types include:

• BOD
• JSON
• DSV
• ANY

See the ION documentation for additional details about connection points.