I added a parameter at a business component.
This parameter will not added to the testplan/parameters.
Same if I change a default value. It will not be refreshed, even it's the default value.
I even restarted HP QC.
Any recommendations?
I have stumbled upon similar problem.
I have tried to do it other way round and it partially helped:
Add new parameter in HP QC in Business Component area, Parameters tab.
Go to Test Plan -> Test Script tab. In Iterations column click on 1 Iterations link.
In right top corner click on button Create Test Parameters and Create. New value will be added in grid below.
Go to Parameters tab - now you should be able to use this param.
Go to UFT - parameter should be also visible.
Related
I have a D365 form with two subgrids. I have to add a button on one of the subgrid.
I'm trying to achieve this using ribbon workbench, but facing issues.
Issue 1: How to specify the subgrid on which i want to show my button?
Issue 2: Right now, button is not visible on either of the two subgrid.
Please suggest any solution.
As you mention "D365", I assume your Dynamics version is greater than v9.0. Below suggestion for issue 2 only works for v9.0 or later.
For issue 1: You can add an enable rule for your ribbon, and write some JS function for this enable rule. You can pass primaryControId as a parameter this should be the subgrid name and then use it in your code to determine show/hide your ribbon.
For issue 2: You can use the ribbondebug function to debug your ribbon, you can enable it by adding &ribbondebug=true at the end of the URL. After you refresh your page, at the end of the ribbon area will occur a ribbon called "Command checker", click the "Command checker" and switch to "Command properties" tab, finally you can see all the rules and function results bound to the ribbon, check all the listed result. You can see more info from here
I'm creating my own version of a wizard form using Asp.Net Webforms.
The form contains multiple steps and each step contains multiple input fields of varying types. Data is validated after each step is completed before moving onto the next step.
In addition to moving forward, each completed section also has an Edit facility.
I was hoping to have 2 buttons available in Edit mode - one to Continue and re-validate and another to Cancel and forget everything.
However, it seems that isn't so easy.
The continue button works exactly as the Continue button in add mode - in fact it's the same button - so no issues there.
But there is an issue with the Cancel button.
Suppose a user enters edit mode and changes their name from 'John' to 'Jon'. They could press Continue to accept and revalidate. however, if they were to press Cancel, they would expect so see the original spelling of 'John' restored.
This doesn't happen automatically.
So, as I currently see it, I have two options. The easy option - remove the Cancel button (and potential confusion) - or the hard option, to code a backup and restore solution in edit mode, which is likely to be a pain as it will need to cover all input types.
However, I'm hoping there's a third option available - one that offers some kind of built in functionality to help manage this problem.
So that's the question - is there any other solution aside from the two options I've already outlined?
First I want to make clear that my problem is not a technical question. I want to talk about usability.
In my company we have a function to check if a scale works properly. We have the button you see bellow (1) to start a function named scaleCheck(). During the scale check the weight of the scale is set to 0 and then a specified weight is put on the scale automatically and when the weight matches the number set in a config file the scale is OK. So when you click on the button, it gets the white border (2) and when the check is finished the button turns normal again (3).
This is the automatic process, but not every customer has a scale which can put automatically a weight on it. So in this case the customer has to go to the scale an put a weight on it by his own. In our application the customer can configure, if he wants the process to be manual or automatic and the button will adjust to this. So when the configuration is set on manual we have to interrupt our function an wait for the customer until he is ready. Because we don't know how many time he will need, he has to click on the button again to tell the application that the process can continue. Therefore we changed the button a bit when we are in manual mode. As you can see below the button (1) changes the image, when the customer clicks the first time on it (2), to show that the weight has to be put on the scale. When he clicks the second time the process proceeds (3).
So this is the current state. The automatic mode works how the customers imagine it to be, but in the manual mode many people have problems with it and need a lot of time the recognize that they have to click on the same button again they clicked before.
And here is my question, is there a better way to show the customers that this button should be clicked again. Are there some people who have experiences with a similar kind of functionality? Or is there a better way to do it? I'm open for every idea which comes in.
We ended up with the opinion that it is not a intuitive solution to click twice on the button. We solved it by showing the user a message after the first click on the button, and accepting that message is count as the second click. With usability in mind this i by far a better solution and the customers can handle this situation much better.
Today I faced a strange issue (could be a silly one) for data binding while navigating to 2nd view which is showing List of data coming from OData model and Panel at the bottom
I have replicate the code into this link - http://plnkr.co/edit/ClZqvo?p=info (You can run this as well through RUN on the Top) - Kindly run it in chrome with disabled security (Due to CORS issue)
Now the problem is when I am navigating to 2nd view (OData Table) and then Select any List Item, you will see in the bottom, the Panel will reflect the selected item (as I have used BindElement method to bind the path). After this I clicked back and then my 1st view will appear (JSON table) again I clicked on Next Button and then 2nd view will appear again. When I select the same item which I have selected previously then this time Panel will not show the selected items. This issue is coming only when I navigate back and forth and select the same item. Not able to understand what caused this?
But if I choose any other item then it will show me the selected item.
Anyone having any idea about this?
~Rahul
This is common issue when using bindElement, I have faced it too. It might be failing to resolve context of referenced entity. So, fields are not binded with respective values.
As a alternative you can use setBindingContext to bind fields within panel.
Since you are using named model, it should be specified as argument to setBindingContext.
So your code will be like
onSelect: function(oEvent) {
var oContext = oEvent.getSource().getBindingContext("odataModel");
var oProductDetailPanel = this.getView().byId("prodDetailsPanel");
oProductDetailPanel.setBindingContext(oContext, "odataModel");
}
I am printing a details subreport that gets printed let's say 5 times on the overall report, for 5 query results. I compute some stuff for it with my code, and so I use BeforePrint event on an XRTable widget that I have in that subreport. So far so good.
What I don't like is that when the BeforePrint executes for that table for the first time and I change its cells' text to something, that this renders on all subsequent instances of this report and table being printed. Now, obviously, since BeforePrint gets called again, I get the opportunity to reset the text to what it should be. So this is not a show stopper.
Yet, this somehow fills wrong, and an invitation to bugs. Is there a way for me to explicitly access "the instance of the table/other widget being printed" rather than "the widget in general, with changes being rendered in all instances that it prints"?
Indeed, you are right. If the formatting should be based on the earlier created data or summary, formatting rules won't work. A possible solution to this problem is to implement a special approach when a developer manually browses all printing system bricks and changes their content manually. You will find some examples on how this can be done at:
Implementing Page totals
subtotal on page bottom and on next page on top