Extend the Connector Contract

Fluent Domains

These domains are based on - Domain Model

Naming rules

Fluent brings a list of predefined and reserved message names that are used across its standard workflows, but it is still possible for any partner or customer to define new ones, and use them in custom workflows. Each Fluent module should describe all available message names (commands and events) that are part of the module.

Public names

Public names are for public API or cross-domain use.

• The message name is formed of three parts: 

  `<fluentcommerce>.<connector/module><domain>.<action/event name>`

  . For example: 

  `fc.connect.product.upsert`

   a. Commands (aka action): 

  `<fluentcommerce>.<domain>.<action/event name>`

   b. Event: 

  `<domain>:<entity>:<event name>`

   c. 

  `fluentcommerce`

   should be replaced with account id for client-specific implementations For example: 

  `acme.connect.product.upsert`

• Complex names or domains should be lower dot case rather than using camel case
• Event names should not be in the past For example: status-update
• Command names should have the verb/action first For example: upsert-location
• The overall message name should very clearly state the intent of the message
• A message has a single purpose

Internal names

Internal names are for all intermediary steps of a flow and local to the domain and workflow.

• The message name is formed of 3 parts, the domain name followed by a fixed tag and step name: 

  `<domain>:internal:<step-name>`

  .
• Complex names or domains should be lower dot case rather than using camel case.
• Step names should have the verb/action first. For example: upsert-location
• The name should very clearly state the intent of the step.
• A step has a single purpose.