Activity - Publish Data

Overview

• Pushes data from a work item or asset to another work item or asset
• Which work items or assets the data is pushed to is dependant on a set of filters
• One example is that if both work items have the same value in a text component then the data will be pushed

Steps to set up this activity

1. Create or have an existing workflow (I’ll call this Workflow A in this example and we will be publishing data FROM this workflow)
1. You need Ecosystem Orchestrator permission to create a new workflow or Workflow Owner permission to edit an existing workflow
2. Create or have another existing workflow (I’ll call this Workflow B in this example and we will be publishing data TO this workflow)
3. Set up a publish data activity on the task that you want to publish data on Workflow A and set up these properties
1. “relatedWork”: {
1. “flowName”: the flow name of Workflow B
1. Can be found under the “name” property in the “Properties” page on Workflow B
2. “stepName”: is the name of the step that the component that you will use
1. e.g. if the step’s “name” property is
1. "name": "ecosystem/workflow/entity/generated-1af2a966-8383-467c-abe7-3be40544217b/untitledstep__generated-27fb4531-de5f-4bdf-8d1d-921f5f3c418b"
2. Then the value to use in “stepName” would be
1. /untitledstep__generated-27fb4531-de5f-4bdf-8d1d-921f5f3c418b
3. “targetName”: “any string” (just used for labelling purposes)
4. “sourceName”: “any string” (just used for labelling purposes)
5. “workFilters”: [
1. {
1. “targetPath”: the data path from the component in Workflow B to match with the valuePath
2. “valuePath”: the data path from the component in Workflow A to match with the targetPath
1. When the task is submitted it will find the value in the valuePath property from Workflow A and check all the open work items in Workflow B and see if the value in targetPath matches, if they do match then the data from the dataMapping property will publish to these Workflow B work items
2. }
6. ],
7. “createWorkIfNotFound”: false (set to false if you want to update existing work items, set to true if you want to create a new work item)
2. },
3. “publishDataDirection”: “ToRelatedEntity”,
4. “operations”: [
1. {
1. “sectionName”: is the name of the task that the component that you will use in “workFilters” in Workflow B
1. Like stepName but for the task not the step
2. “dataMapping”: [
1. {
1. “fromPath”: the dataPath of the component in Workflow A that you want to take a value from
2. “toProperty”: the dataPath of the component in Workflow B that you want to send a value to
2. }
3. ],
4. “updateType”: “Set”,
5. “targetPath”: “$”,
6. “dataType”: “String”
2. }
5. ],
6. “attachmentOperations”: [
1. {
1. “sourceFolder”: the dataPath of the attachments folder in Workflow A that you want to take attachments from
2. “destinationFolder”: the dataPath of the attachments folder in Workflow B that you want to send attachments to
2. }
7. ]
4. Create two work items in Workflow B, one with a particular value in a component (the one used in workFilters) and another with a different value in the same component
5. Create a work item in Workflow A and add the same particular value to the component that is that is used in workFilters
1. Also add a value in the component used in the dataMapping property
2. Publish this work item
6. Done!
1. You will see that on Workflow B work item, that had a value in the workFilters component that matches the value form the Workflow A work item, now has the value in the component used in the dataMapping property from the Workflow A work item

Advanced Editor properties and what they do

Properties shared between activities

Properties unique to this activity

• All of these unique properties sit within a “properties” object e.g.

{
	"property one shared between components": "",
	"properties": {
		"entityType": "",
		"etc": "",
	}
}

Operation

Attachment Operation

Related Work

Advanced Editor example of this activity fully set up

{
  "continueOnError": false,
  "executeWhen": "AfterExecute",
  "runOnSystemEvents": [],
  "properties": {
    "saveEmptyValue": true,
    "publishDataDirection": "ToRelatedEntity",
    "attachmentPaths": [],
    "operations": [
      {
        "sectionName": "untitledtask__generated-f11b49f2-b2b6-453a-a28e-ffa361db8a11",
        "dataMapping": [
          {
            "fromPath": "$.myText1",
            "toProperty": "targetText"
          }
        ],
        "updateType": "Set",
        "targetPath": "$",
        "dataType": "String",
        "excludeProperties": []
      }
    ],
    "attachmentOperations": [
      {
        "sourceFolder": "firstStep-attachment",
        "destinationFolder": "targetFirstStep-anotherAttachment"
      }
    ],
    "relatedWork": {
      "flowName": "walking-duck-four/workflow/entity/generated-842df0c3-f6ec-4056-82af-42db5c289115",
      "stepName": "untitledtask__generated-f11b49f2-b2b6-453a-a28e-ffa361db8a11",
      "targetName": "Delivery",
      "sourceName": "Order",
      "workFilters": [],
      "createWorkIfNotFound": true,
      "removeExisting": false,
      "addRelationship": true,
      "isOneWayRelationship": false
    }
  }
}

Video explanation

• Coming soon…