Skip to main content

Output logic for QU4RTET supply chain messaging.

Project description

https://gitlab.com/serial-lab/quartet_output/badges/master/coverage.svg https://gitlab.com/serial-lab/quartet_output/badges/master/build.svg https://badge.fury.io/py/quartet_output.svg

Output Rules and logic for QU4RTET supply chain and trading-partner messaging.

Intro

The quartet_output module is responsible for inspecting inbound messages and, based on criteria defined by users, singling out some of those messages for further processing. Once a message has been filtered, it is typically used to create a new message from some existing EPCIS data or to simply create a new message using the same data with the intent of sending that message to another system.

Criteria

The quartet_output module allows users to define EPCIS Output Criteria definitions. These definitions allow users to instruct the module to look at inbound EPCIS events and look for events that meet certain selection criteria. For example, users can define criteria that would inspect all inbound Transaction Events of action ADD from a specific bizLocation with a Purchase Order business transaction attached. Once an event arrives meeting these criteria, the system allows a user to use that event to trigger the generation of a shipping event along with all of the serial numbers for the epcs specified in the triggering event. Other scenarios are possible as well and, of course, users can implement Rules and Steps of their own that do just about anything once an inbound event has been filtered.

Transport

quartet_output allows users to configure transport configurations using both EndPoint and AuthenticationInfo database models. These models are attached to the criteria that filter EPCIS events and allow the user to specify where messages should be sent once an event has been filtered and has triggered any outbound processing logic.

Documentation

The full documentation is located here:

https://serial-lab.gitlab.io/quartet_output

Quickstart

Install quartet_output

pip install quartet_output

Add it to your INSTALLED_APPS:

INSTALLED_APPS = (
    ...
    'quartet_output.apps.QuartetOutputConfig',
    ...
)

Add quartet_output’s URL patterns:

from quartet_output import urls as quartet_output_urls


urlpatterns = [
    ...
    url(r'^', include(quartet_output_urls)),
    ...
]

Features

  • Output determination allows you to create filters on inbound EPCIS data and determine which inbound EPCIS events trigger outbound business messaging.

  • Define HTTP and HTTPS end points for trading partners.

  • Define various authentication schemes for external end points.

  • Outbound messages take advantage of the quartet_capture rule engine by creating a new outbound task for every message. This puts every outbound task on the Celery Task Queue- allowing you to scale your outbound messaging to your liking.

Running The Unit Tests

source <YOURVIRTUALENV>/bin/activate
(myenv) $ pip install tox
(myenv) $ tox

Project details


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

quartet_output-1.0.6.tar.gz (35.8 kB view details)

Uploaded Source

Built Distribution

If you're not sure about the file name format, learn more about wheel file names.

quartet_output-1.0.6-py2.py3-none-any.whl (33.2 kB view details)

Uploaded Python 2Python 3

File details

Details for the file quartet_output-1.0.6.tar.gz.

File metadata

File hashes

Hashes for quartet_output-1.0.6.tar.gz
Algorithm Hash digest
SHA256 7226a356c8b4d4dec8fbceede6625137e7f0b1be8bdafa33e81dad83601c6e58
MD5 9171e82265480bd26d42acbb7bd0785b
BLAKE2b-256 df27dcbaa04ad3ac2f24966f952979035509ebbfc4319438a747e538a0c34cb6

See more details on using hashes here.

File details

Details for the file quartet_output-1.0.6-py2.py3-none-any.whl.

File metadata

File hashes

Hashes for quartet_output-1.0.6-py2.py3-none-any.whl
Algorithm Hash digest
SHA256 1fbb850f128c1ef59b79664f7ff5b8edf6aefb58b066c36c5820e3d1fd48c27a
MD5 53c46330ad1d0c7148bc8601db4ce84f
BLAKE2b-256 9007f22fbb2d567f245d9e7249d83c1b5ed36d1adbbefc2b425f4a2f852b3583

See more details on using hashes here.

Supported by

AWS Cloud computing and Security Sponsor Datadog Monitoring Depot Continuous Integration Fastly CDN Google Download Analytics Pingdom Monitoring Sentry Error logging StatusPage Status page