SendEventOnVerifyingAttributeValue
Changed on:
27 Nov 2023
Overview
The rule sends and event with the name specified in the input parameter in case the incoming entity has an attribute name and value that matches with the name and value provided in the input parameters. Otherwise, a no match event is sent.
| Plugin Name | Order Reference Module |
|---|---|
| Namespace | [[account.id]].order |
The Order Reference Module is the foundation for order-related implementations. It provides reference workflows for click & collect, home delivery and mixed baskets and those needed to build your own. Extensible by design, use this Module as a base to build a solution to your customers' needs.
UI Description
Sends an event with name "PROP_EVENT_NAME" in case the attribute name and value matches the given name and value. Otherwise sends "PROP_NO_MATCH_EVENT_NAME" event.
Accepts
- ORDER
- ARTICLE
- FULFILMENT
- FULFILMENT_OPTIONS
Actions
- This rule sends an event eventName if the incoming entity has the given attribute {attributeName} and the attribute value matches the given value {attributeValue}.
Rule parameters
Parameter | Description |
PROP_EVENT_NAME | Output event name to be created and sent if the attribute name and value matches. |
PROP_NO_MATCH_EVENT_NAME | Output event name to be created and sent if the attribute name and value doesn't exist or match. |
PROP_ATTRIBUTE_NAME | Attribute name to be matched in the incoming entity. |
PROP_ATTRIBUTE_VALUE | Attribute value to be matched in the incoming entity. |
Event attributes
This rule does not directly identify any event attributes.
Exceptions
This rule will throw an RubixException: 400 (wrong data) if attempted against unsupported entities.
Configuration example
1{
2 "name": "<ACCOUNTID>.order.endEventOnVerifyingAttributeValue",
3 "props": {
4 "eventName": "testEventName",
5 "noMatchEventName": "NoMatch",
6 "attributeName": "testAttributeName",
7 "attributeValue": "testAttributeValue"
8 }
9}Language: json
Version History
v1.0.0
refers to the plugin
