@5minds/node-red-contrib-processcube 1.1.4-develop-6d3478-m0m7vuis → 1.1.4-develop-9a2b44-m0m8kbzf

package/message-event-trigger.html

@@ -6,7 +6,6 @@
             name: { value: '' },
             engine: { value: '', type: 'processcube-engine-config' },
             messagename: { value: '', required: true },
-            processInstanceId: { value: '' },
         },
         inputs: 1,
         outputs: 1,
@@ -30,10 +29,6 @@
         <label for="node-input-messagename"><i class="fa fa-tag"></i> Message Name</label>
         <input type="text" id="node-input-messagename" placeholder="Name of the Message-Event" />
     </div>
-    <div class="form-row">
-        <label for="node-input-processinstanceid"><i class="fa fa-tag"></i> Process Instance Id</label>
-        <input type="text" id="node-input-processinstanceid" placeholder="Id of the recipient process instance" />
-    </div>
 </script>
 
 <script type="text/markdown" data-help-name="externaltask-input">
@@ -44,6 +39,7 @@ From the config the `messagename` and the `processInstanceId` must be set.
 ## Inputs
 
 : payload (Object) : The payload will be sent to the message event and be used as a new token payload.
+: processInstanceId (string) : The process instance where the message event should be triggered.
 
 ### References
 

package/message-event-trigger.js

@@ -15,7 +15,7 @@ module.exports = function (RED) {
 
             engine.engineClient.events
                 .triggerMessageEvent(config.messagename, {
-                    processInstanceId: config.processinstanceid,
+                    processInstanceId: msg.processinstanceid,
                     payload: msg.payload,
                     identity: engine.identity,
                 })

package/package.json

@@ -1,6 +1,6 @@
 {
     "name": "@5minds/node-red-contrib-processcube",
-    "version": "1.1.4-develop-6d3478-m0m7vuis",
+    "version": "1.1.4-develop-9a2b44-m0m8kbzf",
     "license": "MIT",
     "description": "Node-RED nodes for ProcessCube",
     "scripts": {

package/signal-event-trigger.html

@@ -6,7 +6,6 @@
             name: { value: '' },
             engine: { value: '', type: 'processcube-engine-config' },
             signalname: { value: '', required: true },
-            processInstanceId: { value: '' },
         },
         inputs: 1,
         outputs: 1,
@@ -30,10 +29,7 @@
         <label for="node-input-signalname"><i class="fa fa-tag"></i> Signal Name</label>
         <input type="text" id="node-input-signalname" placeholder="Name of the Signal" />
     </div>
-    <div class="form-row">
-        <label for="node-input-processinstanceid"><i class="fa fa-tag"></i> Process Instance Id</label>
-        <input type="text" id="node-input-processinstanceid" placeholder="Id of the recipient process instance" />
-    </div>
+    
 </script>
 
 <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.
 ## Inputs
 
 : payload (Object) : Will sent to the event and used an new token payload.
+: processInstanceId (string) : The process instance where the signal event should be triggered.
 
 ### References
 

package/signal-event-trigger.js

@@ -15,7 +15,7 @@ module.exports = function (RED) {
     
             client.events
                 .triggerSignalEvent(config.signalname, {
-                    processInstanceId: config.processinstanceid,
+                    processInstanceId: msg.processinstanceid,
                     payload: msg.payload,
                     identity: engine.identity,
                 })