How to automate “Read Values” tab in SPSS Modeler? - transpose

I am working on fully automating a model I have created in SPSS Modeler. My model consists of source nodes that get updated everytime I run the scripts. The datamodel then goes through multiple node including a transpose node. Though, everytime the datamodel is updated, I have to manually press "Read Values" tab to grab the updated fields otherwise SPSS creates an error. I need to know is there any way to automate the "Read Values" tab function?

There is to my knowledge no way to automate the "Read Values" button function. The only way to trigger the node to read the values is to manually click it each time.

Related

Run two keywords in Robot Framewok in parallel

I use robot framework with Appium library to automate an application.
I want to test there a graph functionality. When user long presses somewhere on the graph and holds his/her finger the values are shown for that date, as soon as user stops pressing the values disappear.
I tried to Long Press the graph and check that page should contain text or wait until page contains passing the expected text to appear, but the case always fails, as at the time when robot framework starts to check the text it is already disappeared.
So as I understand what I really need is to make two keywords run in parallel. The following two ones:
Long Press 5000
wait until page contains someText
I googled and seems that some time ago there was a way to run parallel keywords, but now they removed it from framework.
So does anyone know how can I test this case or is it possible at all?

Undo an operation in the neo4j schema

After hitting call db.schema() in a neo4j command shell in my browser, I got the graph representation of the schema.
After hitting on one of the nodes, generally, there are set of buttons(as shown in the picture below), By mistake I hit the cross button.
Doe this modify the data in the database? If yes How do I undo this?
Any help is appreciated.
No, the graphical view is only for display purposes currently, all you did was remove the node from the visualization. Your data hasn't been modified.

How to announce to user when a Google Script is completed

On a Google Sheet, I have an extensive OnOpen script (viewable here) to refresh data on several sheets within the workbook. It all takes a while for all script lines to execute, i.e. to import new raw data and to then perform five different Unique Queries against that new data and thus update data on five sheets. When the Google Sheet is opened the user does see two successive pop-up yellow "Working" boxes, then five subsequent progress bars (while each of the queries do their thing). This all takes quite a while. I'd like to make an addition to the script routine to announce to the user that "all data is now refreshed and ready to view." A simple MessageBox ("Data now refreshed') placed at the end of the scripts seems to pop up before all script commands are actually completed. Thus the message box gives misleading info and I think it also interrupts some script lines from executing until "OK" is checked. So, MessageBox doesn't seem to work. So, I'm looking for a way to confirm that all script line (and all unique queries) are, in fact, complete before informing the user that it's OK to start viewing the data. Thanks.
Place a SpreadsheetApp.flush() before the "finished" alert box; the flush() method:
Applies all pending Spreadsheet changes. Spreadsheet operations are sometimes bundled together to improve performance, such as when doing multiple calls to Range.getValue(). However, sometimes you may want to make sure that all pending changes are made right away, for instance to show users data as a script is executing.

Using Asana events API for task monitoring

I'm trying to use Asana events API to track changes in one of our projects, more specific task movement between sections.
Our workflow is as follows:
We have a project divided into sections.
Each section represents a
step in the process. When one step is done, the task is moved to
section below.
When a given task reaches a specific step we want to pass it to an external system. It doesn't have to be the full info - basic things + url would be enough.
My idea was to use https://asana.com/developers/api-reference/events to implement a pull-based mechanism to obtain recent changes in tasks.
My problems are:
Events API seem to generate a lot of information, but not the useful ones. Moving one single task between sections generates 3 events (2 "changed" actions, one "added" action marked as "system"). During work many tasks will be moved between many sections, but I'm interested one in one specific sections. How can I finds items moved into that section? I know that there's a
resource->text field, but it gives me something like moved from X to Y (ProjectName) which probably is a human readable message that might change in the future
According to documentation the resource key should contain task data, but the only info I see is id and name which is not enough for my case. Is it possible to get hold on tags using events API? Or any other data that would allow us to classify tasks in our system?
Can I listen for events for a specific section instead of tracking the whole project?
Ideas or suggestions are welcome. Thanks
In short:
Yes, answer below.
Yes, answer below.
Unfortunately not, sections are really tasks with a bit of extra functionality. Currently the API represents the relationship between sections and the tasks in them via the memberships field on a task and not the other way.
This should help you achieve what you are looking for, I think.
Let's say you have a project Ninja Pipeline with 2 sections Novice & Expert. Keep in mind, sections are really just tasks whose name ends with a : character with a few extra features in that tasks can belong to them.
Events "bubble up" from children to their parents; therefore, when you the Wombat task in this project form the Novice section to Expert you get 3 events. Starting from the top level going down, they are:
The Ninja Pipeline project changed.
The Wombat task changed.
A story was added to the Wombat task.
For your use case, the most interesting event is the second one about the task changing. The data you really want to know is now that the task changed what is the value of the memberships field on the task. If it is now a member of the section you are interested in, take action, otherwise ignore.
By default, many resources in the API are represented in compact form which usually only includes the id & name. Use the input/output options in order to expand objects or select specific fields you need.
In this case your best bet is to include the query parameter opt_expand=resource when polling events on the project. This should expand all of the resource objects in the payload. For events of type: "task" then if resource.memberships[0].section.id=<id_of_the_section> is true, take action, otherwise ignore.

Project Gantt with roll up/down Tableau

I have done quite a few Gantt Charts in Tableau, but this one is stumping me.
I am trying to create a project type Gantt chart that displays the project level due date at the top of each grouping. This should show the due date from the case and the duration so far. That works fine until I attempt the next part which is to allow the consumer to click on that bar and have the tasks roll down with each of their project and in many cases actual durations. (scheduled start and finish if not completed and actual start and finish if it is)
The problem is that Tableau wants to make the Project an aggregate of the tasks' durations. I need to show what we specced the project out to, then the actual task break down so we can see where we are misjudging our estimates. Also would like a dropline for today that goes to x axis and one for when project is due that goes to the pane axis for the project. Yes of course there are multiple projects being plotted across the departments as well. Has anyone ever done something like this in Tableau? Any idea how I can get this to stop summing the tasks and use the project projected duration?
Thanks in advance,
Karen E. Hannum

Resources