Set Key-Values 2

Revision History

3.0.0.1 Initial Release for new platform
3.0.0.2 Fixes due to platform updates

Properties

Group

Type: String Input
Provides a collation of related key-values. For example invoices.

SourceDocument

Type: Multiline Text Input
Provides an XML or JSON document that contains the set of key-value pairs to be stored.

Namespaces

Type: Multiline Text Input
If SourceDocument is an XML document, provides a set of prefix and namespace associations for the prefixes referenced in the KeysPath and/or ValuesPath. Provide one per line, using the syntax {prefix}:{namespace} .

KeysPath

Type: String Input
Provides a JSON Path or XPath that matches the set of fields in SourceDocument representing the keys for the key-value pairs.

ValuesPath

Type: String Input
Provides a JSON Path or XPath that matches the set of fields in SourceDocument representing the values for the key-value pairs.

Status

Type: List Input
Provides optional status metadata for the record identified by the key-value pair. Note that these statuses have no internal effect in Flowgear.
Unknown
InProgress
Warning
Error
Success

Remarks

Key-Value pairs provide a fast technique for permanently creating associations between equivalent records in a source and a target app or service.

Example scenario:

A workflow retrieves an order placed in an e-commerce platform (order 232 )
The order is integrated into an accounting system. On completion, the accounting system generates it's own order number ORD00412
Use the Set Key-Value 2 Node to associate Key 232 with Value ORD00412
If a change is made to the order in the e-commerce platform and that change needs to be integrated into the accounting system, use the Get Key-Value 2 Node to determine the correlating order ID when the update is made to the accounting system

Key-Values are not shared between site environments, which means the value could only be retrieved from the environment where it has been set. Ensure the new group name will be less than 50 characters.