on 04-29-2014 6:19 AM
Hi All,
I am facing a critical problem. I have a screen with two List tile view. The object assigned to the screen is MainObject and the two List tile views display Collection1 and Collection2.
Now the requirement is user should select an object from either Collection1 or Collection2 and press on continue button.
I am using an iPad as device. The problem is when the screen is displayed, the first object from each List tile view is automatically focused. I can't change the Initial focus setting at all. Whatever entry is given in the Focus field, the first objects of both the List Tile views kept on selected.
Is there any resolution so that I can atleast define the initial focus??
In terms of setting the selected item in a tile list you can use the List Selection action step.
So in your action that displays the screen, after the navigates step add a List Selection step (or two in your case) to set the initially selected item in each list.
You will specify the Screen Set / Screen and List Control that the step will act against and then define how you want rows selected (By Rule, First Row, Last Row, Next Row, None). In my example about I am using a rule to select the first row where my rule returns true.
While I have done this for a single list successfully I have not tried with two lists but don't see any reason it shouldn't work.
--Bill
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Sourav,
You could also set the List Tile controls to single-click. That way they will not auto select the first row, and you would not even need a continue button. As soon as the user clicks a row, the select action on the List Tile control would run.
Jason Latko - Senior Product Developer at SAP
Lau,
Here is an example of a rule to select a particular row on iPad for a List Tile control. This assumes that the list is displaying Order objects:
EQSTR
Order Object -> ID Property
[Test]
[Test] above is a string constant, but you could point to a property, global, or any other valid target. The above rule will find the Order row in the list that has an ID with a value of "Test" and select it.
Jason Latko - Senior Product Developer at SAP
Lau,
Don't just use OperationID Property. Always fully qualify the object type when possible: Whatever Object -> OperationID Property. This will often help Agentry to know exactly what you are trying to do, instead of letting it guess. Do this by right-clicking the object and changing context in the property browser. This might not fix your problem in this case, but it is good practice in general.
Always assume Bill F. and I are using the current Agentry version which at this moment is 7.0.3 on SMP 3.0. I know this worked in 6.x though. The better question is, what version are you using?
Jason Latko - Senior Product Developer at SAP
Hey Bill and Jason. I am also configuring a solution based on WM 5.3. We have used the editor and server install files that were in the SAP WM 5.3 installation package. Our server and editor runs on Agentry 6.0.22.0, and we use the most recent version of the "Syclo Agentry" application on the appstore (the one with IOS 7 look). I can't find any patches to this setup on the SAP marketplace ?
User | Count |
---|---|
101 | |
13 | |
13 | |
11 | |
11 | |
7 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.