My mm.dh.vflowpipeline operator is based on the standard com.sap.dh.vflowpipeline operator. The important difference is that it could receive substitution parameters from the input port.
The following parameters can or must be provided in order to execute a pipeline:
graphName
| Type: string
| Default: ""pipelineOutPortName
| Type: string
| Default: ""configurationSubstitutions
| Type: array
| Default: []false
. If set to true
, the given graph will be stoped immediately after finishing processing the subgraph.\
ID: stopGraph
| Type: bool
| Default: falseNote that the value help for the property Graph Name
displays always the list of possible graphs from the Modeler instance on the current machine.
Remarks:
substitutions: The input message, with substitution parameters.\
Type: message
Example:
{ Attributes: {}, Body: [{ "name": "BATCH", "value": 1000 }] }
any.*
It’s required to set port as “exported”. Right click on out port and select “Export port”.
const SDK = require("@sap/vflow-sub-node-sdk"); const operator = SDK.Operator.getInstance(); operator.getOutPort("out1").send({ Attributes: {}, Body: [{ "name": "BATCH", "value": 1000 }] });
Please let me know if, you think this is a useful solution. If you use the operator in your development, please tell me about it!
Please feel free to make any changes, starting from the ID to the program code.
Click below image, to read a full blog at blogs.sap.com
Quick Links
Legal Stuff