Am not able to capture the updated order of nodes in DragDropTree
However Am able to capture the order of nodes when a node is checked or unchecked.Because "nodeCheckStateChanged" event triggered which captures the object as shown in below screenshot. newCheckedNodes has the nodes in updated order
Gone through list of events fired when we do drag and drop but none of them capture the order of nodes checked. https://www.igniteui.com/help/api/2018.1/ui.igtree
Is there any alternate way by which I can capture the order of checked nodes when I do drag and drop.
We can make use of method as shown below in the nodeDropped event which will have the latest order of the nodes checked.
nodeDropped: function (evt, ui) {
//This will have the latest order of nodes checked
var nodes = treeElement.igTree("checkedNodes");
}
Related
I use the select node to filter out some of the entries in the dataset, and then run a model.
I want to save time and not go through all the rows again when I rerun the model. I tried the Run from here option, but the execution goes through all the rows again. Also tried the sequal pushback purple button, but to no effort.
Is it possible to only go through the selected rows when running a model, without having to export the newly filtered database?
If this makes any sense to you, I guess it might work:
Once you have specified the required options for streams and
connected the required nodes, you can run the stream by running
the data through nodes in the stream. Run part of a data stream by
right-clicking any non-terminal node and clicking Run From Here on
the pop-up menu. Doing so causes only those operations after the
selected node to be performed.
Can you provide a snapshot of your data?
Do you use more than one column as a target in your time series?
You can change the selection and just click somewhere behind the nugget and use run from here maybe?
What's the error message or does it just rerun the model?
How can I update a particular node that all users have in their own branch?
I am trying to update a users set of points back to 15 after a certain amount of days by a push of a button. I know how to update 1 users node but can't seem to figure out how to do create a function that when I push a button it resets all users that have that branch/var back to 15.
Otherwise, I would have to do it individually which is obviously not efficient.
This is my code to reset 1 of the student's node by a click of a button
Database.database().reference().root.child("students").child(userId).updateChildValues(["points": self.newPoints])
How do I write a method to reset all students who have the value "points" key by a press of a button?
Any help would be appreciated.
Thanks
You can't use wildcards to replace userId and therefore apply it to every node. You would probably need to fetch the entire students node, and update them one by one using a for loop, which would be very inefficient.
You probably want to use a different data structure in your database that would be more appropriate to your situation. Thats said, if you still want to stick with your current structure you can try having your client update a single boolean flag in your database, and then program a trigger function in node.js so that the update is handled on the server side directly. Check out : Firebase Cloud Functions
I made a zabbix template and scripts for my OpenVPN server. This template generates VPN users (as discovered nodes) from certificate list. Every node is monitored for traffic, up/down, uptime. All users are placed in VPNUsers group.
I'm trying to make trigger to raise alert when new users added or removed. I studied documentation and found groupsum function, but can't figure out how use it to compare current sum and previous.
Is it possible ?
The discovery part was not clear to me, but grpsum is an aggregate item function. The values would be stored in an item, and then on top of that you'd create a trigger with, for example, abschange()<>0 trigger function.
I want to show a different option to the user in workflow through input node, depending upon whether the user has modified the record or not.
Problem is if I would use a condition node with custom class to detect whether object has been modified by some person or not in between the workflow process then as soon as the person clicks on route workflow the save is automatically called and isModified() flag gets false, How do I get in condition node whether some person has modified the record or not.
I have to show different options to the user if he has modified and different option on routing workflow if he have not modified.
Sounds to me like you need to enable eAudit on the object and then to check whether eauditusername on the most recent audit record for that object bears the userid of the current user.
It's a little hokey and tempts fate, but if your condition node is early in the workflow's route when this button is pressed, you could try and check to see if the changedate on the object (assuming you are working with one of the many objects that has one) is within the last 5 seconds. There is a gap where the record could be routed twice within a few seconds, but the gap is fairly hard to hit. There is also a gap where if the system slows down at that point and takes more than 5 seconds to get to and run your condition, then it would appear to be not modified. You can play with the delay to find a sweet spot of the fewest false positives and negatives.
I am using fancytree's multi-hierarchy select mode (selectMode 3) to select which nodes to remove from the tree. The problem is when all the children are selected - the parent is selected as well, but the user may not want to remove the parent from the hierarchy. I checked the documentation and other Stack Overflow articles but couldn't find a workaround. Any ideas? Thanks!
As the author notes in https://github.com/mar10/fancytree/issues/626 , this situation could be handled by using selectMode: 2.
This mode does not implement any additional logic on its own.
But the click event can be implemented and data.node.visit() can be used to modify the selection state of child nodes.
One complication though is that all child nodes may need to be selected when a parent node is selected. It may help to disable child nodes when the parent is selected.