@5minds/node-red-contrib-processcube 1.1.4-develop-6d3478-m0m7vuis → 1.1.4-develop-9a2b44-m0m8kbzf
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
|
@@ -6,7 +6,6 @@
|
|
|
6
6
|
name: { value: '' },
|
|
7
7
|
engine: { value: '', type: 'processcube-engine-config' },
|
|
8
8
|
messagename: { value: '', required: true },
|
|
9
|
-
processInstanceId: { value: '' },
|
|
10
9
|
},
|
|
11
10
|
inputs: 1,
|
|
12
11
|
outputs: 1,
|
|
@@ -30,10 +29,6 @@
|
|
|
30
29
|
<label for="node-input-messagename"><i class="fa fa-tag"></i> Message Name</label>
|
|
31
30
|
<input type="text" id="node-input-messagename" placeholder="Name of the Message-Event" />
|
|
32
31
|
</div>
|
|
33
|
-
<div class="form-row">
|
|
34
|
-
<label for="node-input-processinstanceid"><i class="fa fa-tag"></i> Process Instance Id</label>
|
|
35
|
-
<input type="text" id="node-input-processinstanceid" placeholder="Id of the recipient process instance" />
|
|
36
|
-
</div>
|
|
37
32
|
</script>
|
|
38
33
|
|
|
39
34
|
<script type="text/markdown" data-help-name="externaltask-input">
|
|
@@ -44,6 +39,7 @@ From the config the `messagename` and the `processInstanceId` must be set.
|
|
|
44
39
|
## Inputs
|
|
45
40
|
|
|
46
41
|
: payload (Object) : The payload will be sent to the message event and be used as a new token payload.
|
|
42
|
+
: processInstanceId (string) : The process instance where the message event should be triggered.
|
|
47
43
|
|
|
48
44
|
### References
|
|
49
45
|
|
package/message-event-trigger.js
CHANGED
|
@@ -15,7 +15,7 @@ module.exports = function (RED) {
|
|
|
15
15
|
|
|
16
16
|
engine.engineClient.events
|
|
17
17
|
.triggerMessageEvent(config.messagename, {
|
|
18
|
-
processInstanceId:
|
|
18
|
+
processInstanceId: msg.processinstanceid,
|
|
19
19
|
payload: msg.payload,
|
|
20
20
|
identity: engine.identity,
|
|
21
21
|
})
|
package/package.json
CHANGED
|
@@ -6,7 +6,6 @@
|
|
|
6
6
|
name: { value: '' },
|
|
7
7
|
engine: { value: '', type: 'processcube-engine-config' },
|
|
8
8
|
signalname: { value: '', required: true },
|
|
9
|
-
processInstanceId: { value: '' },
|
|
10
9
|
},
|
|
11
10
|
inputs: 1,
|
|
12
11
|
outputs: 1,
|
|
@@ -30,10 +29,7 @@
|
|
|
30
29
|
<label for="node-input-signalname"><i class="fa fa-tag"></i> Signal Name</label>
|
|
31
30
|
<input type="text" id="node-input-signalname" placeholder="Name of the Signal" />
|
|
32
31
|
</div>
|
|
33
|
-
|
|
34
|
-
<label for="node-input-processinstanceid"><i class="fa fa-tag"></i> Process Instance Id</label>
|
|
35
|
-
<input type="text" id="node-input-processinstanceid" placeholder="Id of the recipient process instance" />
|
|
36
|
-
</div>
|
|
32
|
+
|
|
37
33
|
</script>
|
|
38
34
|
|
|
39
35
|
<script type="text/markdown" data-help-name="signal-event-trigger">
|
|
@@ -44,6 +40,7 @@ From the config the `signalname` and the `processInstanceId` must be set.
|
|
|
44
40
|
## Inputs
|
|
45
41
|
|
|
46
42
|
: payload (Object) : Will sent to the event and used an new token payload.
|
|
43
|
+
: processInstanceId (string) : The process instance where the signal event should be triggered.
|
|
47
44
|
|
|
48
45
|
### References
|
|
49
46
|
|
package/signal-event-trigger.js
CHANGED