v2.0.7

Bug Fix

• Orchestrations are now all recorded (no longer over-written)

v2.0.6

Minor bug fixes

Use axios config as source of orchestration data

This ensure that all parameters and data are resolved when creating orchestrations. This is the correct place to capture orchestration data as it represents the final state of the request.

v2.0.5

Bug fixes

• Fixed bug where the OpenHIM transactions weren't being updated
• Fixed bug where OpenHIM transaction orchestrations weren't being passed back to the OpenHIM

v.2.0.4

New feature

The building of query parameters for external requests can now be done using the timestamps and constants specified in the endpoint details on endpoint creation.

v2.0.3

Bug fix

• The regex for matching did not have opening and closing tags ^ and $, and this was resulting in endpoint creation duplicate errors as exact matching was not happening.

v2.0.0

Version 2.0.0 release

Features:

A few cool new features have been added in this version:

URL parameter support for custom endpoints

This enables us to have url parameters in our custom endpoints. The parameters are specified in the endpoint pattern. Example pattern - /path/:parameter1/:parameter2. These parameters can then be used in our external requests.

URL parameter support for lookup and response requests

This feature gives us the ability to populate the external requests' url parameters. The values for the url parameters for the external requests can be extracted from the request body, query, and request url parameters. For more on this visit.

Forwarding of incoming request body in the lookup requests

This gives us the ability to forward the request body in our lookups. The property forwardExistingRequestBody will have to be set to true for the lookup in the endpoint configuration. For more on this visit.

v1.0.1

Bug Fixes:

• Mediator urn
  • Enable configuring of mapping mediator's 'urn' via the MEDIATOR_URN environment variable.

v1.0.0

Official v1 Release!

Features:

• Endpoints API
  • CRUD endpoints for the management of the endpoints.
  • Endpoint schema has been moved from static JSON files to JSON objects within MongoDB
  • MongoDB needs to be a replica set for service to work correctly as it makes use of database listeners to restart endpoints
• Content Negotiation
  • Define the input and output content type of the payload
• Payload validation
  • Set various validations on the various data points to enforce data quality. This feature makes use of AJV for data validations
• Object Mapping
  • Create a completely new object for constructing specifically formatted payloads. This feature makes use of Node Object Mapper for creating new data objects
• Field transformations
  • Manipulate fields to transform them into the desired output needed. This could include concatenating string values or performing calculations. This feature makes use of JSONata for data transformations
• State Management
  • Define certain values to extract from the data points to store in the endpoint state. These values can then be extracted/used in a follow-up request. This is quite useful for polling channels that need state of the previous request
• External Requests
  • Define various HTTP requests to be executed before any mapping occurs so that these return objects could be used as a data point for extracting values into the new object
  • Define various HTTP requests to be executed after the mapping occurs so that the new object can be sent via HTTP to an external service for processing