ALM Workflow - Script Editor - Update custom field on Refresh of Execution Grid - hp-alm

In HP ALM, using the Script Editor in Workflow, I created some code to count the number of fails for a selected test in the Test Execution grid. This calculation updates in the TestSetTests_MoveTo module. Not the most elegant solution since the user has to click every line to update, but it works.
My lead wants to have all of the values update on using the ALM Refresh button on the same page. I am looking through all of the different modules, but I don't see anywhere that I can add an update on refresh. Any ideas on how to accomplish this?
Thanks!

I figured out how to add functionality to the refresh button. I created a message box that showed the Action being performed when it was clicked. It's ExecutionGrid.RefeshAllExecGrid Then I added an if statement on ActionName to call my update code and it worked. Hopefully, this helps someone else.
**The misspelling is correct, unfortunately.

Related

Tosca not edifying field in FIORI test automation

I'm currently using Tosca to automate a specific SAP process in FIORI. At the end of the process, I need to click a specific field to finish the process.
What happens is that the program doesn't recognize the field. I tried multiple scans and rescans and nothing worked.
Any advice to overcome the situation?
Please see screenshots.
thanks in advance.
Try to find RadioButton inside the DIV in XScan.
It is better to use set value True/False (if possible) than to click on the element.

BigQuery is deleting lines in my script when I only run part of it

I have a moderately complex script (create about 20 different tables, approx 1500 lines). When making changes, I only need to run the part of the code that comes after the change. I normally dont have any issues with this, but today, I selected lines 800-1500, hit ctrl + enter, and when it completed the run 6 minutes later, I found that all of the code above the line I started the run from (ie lines 1-799) had been deleted.
When I hit ctrl+z nothing happens, so somehow the change has been locked in. I have some earlier versions of the script, but there are changes in here that got deleted that I dont have saved anywhere else.
Two questions:
why is this happening? any way to prevent it from happening again? (other than stricter version control, or running the subset of the query in another query editing window)
Any way to recover the deleted code if ctrl+z doesnt work, and it's not in the query history as I didnt run that piece of it today?
notes: using BigQuery web interface for this
Something caused your browser tab to reload itself. The URL in the browser immediately updates itself with a new job_id parameter every time you execute a query, and going to that URL (via reloading the tab or otherwise) will display the exact SQL executed by that job and the resultset if the job has finished. If you've only highlighted a portion of the query -- welp, that's the query that got run so that's the query that will be displayed when you revisit that url. :(
The new "editor tabs" feature has been causing this for me: I have to click the "disable editor tabs" button at the top of the bigquery UI to prevent the page from reloading when running queries with multiple stages. But there are an endless number of possible reasons that your particular tabs might be reloading on your particular system, so here's a second fix:
Use /* */ SQL comments to block off the parts of the query that you don't want to run. The comments are part of your query and will therefore still be visible even if the browser tab reloads.

Unable to manually trigger pipeline - Trigger button grayed out

The trigger button is grayed out and disabled. I cannot select it.
Pipeline has been published and zero errors on validation.
Pipeline is running on a schedule with no errors, but want to run manually as needed.
Tried Edge and Chrome
Pipeline-Before-Publish
Pipeline-After-Publish
Didn't repro on my side. Which browser do you use? Could you share a screenshot of the disabled trigger button?
It seems like a bug, here is a workaround:
on top of the trigger button, right click and then left click inspect
find the trigger tag and remove disable
What's your factory version? If it's preview (2018-07-01-preview), then publish/debug/trigger are all blocked. Please refresh the page and go to overview page, you will see a prompt dialog suggesting you move to GA version.

Undo functionality in Dojo

I'm using an enhanced grid in Dojo and I would like to implement "Undo" functionality .
For example after editing a cell, adding/deleting a row the user should be able to revert that action.
Any pointers how to get started?
Thanks!
Well maybe you could get inspiration from this Comand History pattern : https://gist.github.com/c210c0344ca4d4bdfacb
About the actions on DataGrid I assume you know what to do and you were just asking about some "undo mechanism" :)
I hope this will help. I've been using it for a while and it works well
Fetch and save the grid store in some variable before editing . Upon clicking the undo button/link set the grid store with the saved old store.

How to fix a non responding ext.list?

I've got a problem with an Ext.List:
You press a button on the main menu and are shown the list. Everything on it works fine and it let's you choose, where to go deeper inside the app. No problems so far.
But if you then go back to the main menu by pressing a "back"-button and reenter the page, that shows this Ext.List, it doesn't work anymore: you can't select an entry of the list.
The "back"-button removes the list, if you return to the main menu this way:
setTimeout(function(){page.removeAll();},100);
What's my mistake? Do you know a better method than "page.removeAll()" that really kills this Ext.List to let it then be completely recreated when I choose to see it in my main menu?
Thanks in advance, you guys have the best tips and tricks.
It's hard to tell without seeing your code but I suspect that there is a javascript error somewhere in the program flow that you described. If you display the javascript console in either Chrome or Firefox it should show the error.
Depending upon how the function that creates the list is defined it would normally recreate the list upon page/function entry and there should be no need to 'kill' the list explicitly.