@5minds/node-red-contrib-processcube 1.8.3-feature-ce2509-m848p0ot → 1.8.3-feature-de7526-m876bxcq

package/dataobject-instance-query.html

@@ -7,6 +7,7 @@
             engine: { value: '', type: 'processcube-engine-config' },
             query: { value: 'payload' },
             query_type: { value: 'msg' },
+            onlyNewest: { value: true },
         },
         inputs: 1,
         outputs: 1,
@@ -43,6 +44,10 @@
         <label for="node-input-query"><i class="fa fa-tag"></i> Query</label>
         <input type="text" id="node-input-query" />
     </div>
+    <div class="form-row">
+      <label for="node-input-onlyNewest"><i class="fa fa-hand"></i>Only current instance per dataObject</label>
+      <input type="checkbox" id="node-input-onlyNewest" title="Applys a client-side filter, that returns just the newest instance per dataObject">
+    </div>
 </script>
 
 <script type="text/markdown" data-help-name="dataobject-instance-query">
@@ -113,6 +118,22 @@ A node to query dataobject instances on the ProcessCube Engine.
     - array: 2021-01-01T00:00:00.000Z,2021-01-02T00:00:00.000Z
   - Description: The created date of the DataObjectInstances to include in the results.
 
+### Only current instance per dataObject
+
+When checked, an additional filter is applied to the result of the query.
+For each `dataObjectId`+`processInstanceId` in the result set, only the instance with the newest `createdAt` timestamp will be returned.
+Therefore, it creates a list containing only the current values of each dataObject.
+
+**Note**: This is not guranteed to work as described above. Since this is a client-side filter, that is applied after executing the server side query, there are some limitations.
+Depending on your query, you might not load all instances of an dataObject. I.e. when setting a limit or offset. Or when querying such an amount of instances, that the engine applies an automatic limit.
+In these cases, this filter will still be applied and return the newest instance from the result set, but that might not be the actual newest value for this dataObject, which would be available in the engines database.
+To avoid thoses problems, make sure to write strict queries, which are guranteed to have a small result set, that can be retrieved in one request.
+The `totalCount` property will, as well, not work as expected. Since this is a value created by the engine, it will not line up with the actual amount of instances, that are returned.
+
+**Note**: This feature will be removed in a future version.
+Due to the problems described above, this functionality should rather be provided by the engines interface.
+As soon as the engine supports querying for the newest dataObject values, this filter becomes obsolete and you should instead alter your query to apply this filter server-side.
+
 ### References
 
 -  [The ProcessCube&copy; Developer Network](https://processcube.io) - All documentation for the ProcessCube&copy; platform

package/dataobject-instance-query.js

@@ -21,6 +21,19 @@ module.exports = function (RED) {
                 .then((matchingInstances) => {
                     msg.payload = matchingInstances;
 
+                    if (config.onlyNewest) {
+                      const newestInstances = {};
+
+                      matchingInstances.dataObjectInstances.forEach(instance => {
+                        newestInstances[instance.processInstanceId] ??= {};
+                        if (!newestInstances[instance.processInstanceId][instance.dataObjectId] || newestInstances[instance.processInstanceId][instance.dataObjectId].createdAt < instance.createdAt) {
+                          newestInstances[instance.processInstanceId][instance.dataObjectId]  = instance;
+                        }
+                      })
+
+                      msg.payload.dataObjectInstances = Object.values(newestInstances).flatMap(v => Object.values(v));
+                    }
+
                     node.send(msg);
                 })
                 .catch((error) => {

package/package.json

@@ -1,6 +1,6 @@
 {
     "name": "@5minds/node-red-contrib-processcube",
-    "version": "1.8.3-feature-ce2509-m848p0ot",
+    "version": "1.8.3-feature-de7526-m876bxcq",
     "license": "MIT",
     "description": "Node-RED nodes for ProcessCube",
     "scripts": {