Trouble with Operations on a queries

eyles

Just to go over my situation and whats happening

On all queries on business objects throughout my system i have some standard operations buttons on each item it brings back such as the standard edit and delete item.

Now i have edit to be the default operation so that when you click on the item it would open the edit form, this was working perfectly fine before i moved over to version 6 of awareIM.

Whats happening now is when i click on the delete operation or any operation for that matter it would open the edit form.

customaware

Eyles,

This is the new functionality of V6.

V 5.9 Functionality.

If Edit checked as Default.
Click Edit button to Edit OR any ACTUAL text on Row
Delete, only but clicking Button

If Edit NOT checked as Default
Click Edit button to Edit
Delete, only but clicking Button

V 6 Functionality...

If Edit is checked as Default.
Clicking ANYWHERE on the row will invoke the Edit
Clicking on Edit Button will invoke Edit twice
Clicking on Delete Button will invoke Delete AND Edit

If Edit is NOT Checked as Default
Clicking on row has no effect.
Clicking on Edit Button will invoke Edit
Clicking on Delete Button will invoke Delete

Before you say, "that's crazy" please note that while it is a change in functionality, it also provides significant benefit.

You can now invoke a process every time you move to a new row either but clicking on it OR using Up/Down Arrow keys. Hence, great funtionality
to display additional data relevant to the current record on the fly.

Check out the Customer table in the new CRM. Change records and see the Customer data to the right..... Nice!

eyles

Except that editing twice is absolutely crazy and editing AND deleting is just wrong.

We're aware than some additional functionality is handy but obvious double edits and or edit/deletes is just what you said! Crazy. Is there no work around for this except removing all default functions?

This will in effect mean that in 80% of our screens we will have to turn off this default functionality and every user of our system will spend hours clicking in the wrong place thinking that something is broken until they remember that they HAVE to now click on the button to edit details.

Guys this is NOT good functionality.

Yet again we have to redesign major parts of our system due to removed/changed/modified "default" functionality that is sold as an improvement but in actual fact means more work and confused existing users.

Again is there a workaround for this lack of functionality?

Rennur

Default edit action should not be invoked when you click on the row operation buttons. As it stands, it is a truly user unfriendly.
The end user user does not expect the edit form to be opened if they click on a operation.
Not very user-friendly.

aware_support

"Clicking on Edit Button will invoke Edit twice
Clicking on Delete Button will invoke Delete AND Edit"

This is not happening for us and works as expected. Clicking Edit will invoke Edit once and Delete will just delete.

eyles

Hi aware_support

So what is actually expecting when it comes to edit being the default operation ?

eagles9999 is stating that
"If Edit is checked as Default.
Clicking ANYWHERE on the row will invoke the Edit
Clicking on Edit Button will invoke Edit twice
Clicking on Delete Button will invoke Delete AND Edit"

in my situation i try to delete an item from a query and it keeps bringing up the edit form and wont actually evoke the delete operation even thou i am clicking on the delete button, this is the same for any other operation.

I really don't want to completely abandon the default operation on all queries on my system just for a work around to simply use any other operation on an item.

aware_support

If Edit is checked as Default.
Clicking ANYWHERE on the row will invoke the Edit
True
Clicking on Edit Button will invoke Edit twice
Not true - just one
Clicking on Delete Button will invoke Delete AND Edit"
Not true - just Delete

Make sure you are using the latest build. If the behaviour you see is different from above please send us a proper bug report

eyles

Where can find out the latest build of version 6 ? I cant find anywhere on the aware site stating the build number.

My current build is 2010

and where do i send a bug report ?

customaware

You can get the latest from your Account Update Eyles.

Rennur

Support,

I'm finding the same issue eyles described.
I have posed this here:
https://forum.awareim.com/d/7432>

Are you saying you are not getting this problem with the query operations buttons?

customaware

In Build 2014 it is a bit different to what I described above.... that was in a previous build.

Now, from what I can see, the only issue is Edit being invoked when Delete clicked if Edit is checked as default.

Clicking Edit button does not now invoke twice (unless user double clicks of course)

Have sent sample bsv to support who are checking out the issue.

Rennur

If you have time, please create a test process and include it in the operation as an icon.

See when you click on this, if the edit (default) & the process are executed at the same time.
This is what I'm getting in 2010 (I didn't test this in 2014 before I reverted back to 2010).

aware_support

Yes, reproduced it finally. The bug will be fixed in the next build.

The latest build number can be seen on the Download page on our web site.

ACDC

There is also a problem with the expand option in the grid. When selecting the + to expand, the record expands as it should but then presents an edit form. I don't know if this is part of the same problem, please could you check this while correcting the bug

Thank You

aware_support

These problems should be fixed in build 2017