Set Key-Values

This document was autogenerated for the Set Key-Values Node.

Revision History

1.0.0.0 Initial Release
1.0.0.2 Bug fix and added support for assigning JSON or XML containers into the Key-Value value
1.0.0.5 Performance improvements
1.0.0.7 Performance improvements
1.0.0.8 Performance improvements
1.0.0.9 Performance improvements

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 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 Node to determine the correlating order ID when the update is made to the accounting system

Key-Values are shared between site environments, and we recommend including the environment in the group name if it needs to be specific to an environment. Ensure the new group name will be less than 50 characters.

Examples

See Sample Workflow for examples.