ERPin Messaging

ERPin Messaging service is receiving messages about changes/events in one system and propagating them to other Moravia systems according to defined workflows.

Developed by Moravia PTG (support@rws.com)

How should message look like

• JSON format (application/json)
• Header
  • messageId: GUID representing message instance (recommended to prevent multiple-delivery)
  • name: URN-like identifier of a message that specifies both origin of the message and type of resource and event.
  • dependency: Representing dependencies of current message.
    • parentItems: Items which must be finished before this message. This parentItem == currentItem in previous message.
    • currentItems: Items which are affected by this message.
• Data (Body)
  • Custom key-value dictionary

{
    "messageId" : "25fc3f54-5be5-478a-b0c3-357b8313ea2e",
    "name" : "moravia:maconomy:vendor:edit:bank_account",
    "dependency": {
        "parentItems" : { "6HZB2byLcj", "ZzXSGs8Xb8" }
        "currentItems" : { "oY8PRNDc0w" }
    },
    "data" : {
        "vendor_id" : "D456874",
        "bank_account_id" : "main-account1",
        "back_account_name" : "Main Bank Account",
        "bank_account_currency" : "USD",
        "bank_account_number" : "115-145648915616/3006"
        "bank_account_bank" : "HSBC Bank"
    }
}

Authentication

AzureAd authentication is supported.