Buttons do not work

robleer

Hi,
I've created a simple query. Then I've added a query menu with buttons.

Somehow the standard Edit and View operations do not work. No reaction at all of the system. I m sure I clicked a record before I click the button.

When I use a process as a operation, the buttons do work. So processes work, standard operations don't.

What can cause this?

Btw: at another place in my system the standard Delete operation works as an Edit operation. So this is a strange behaviour also.

Btw: I use version 6, build 2008

kklosson

Just a tip, check to see how the Default function is employed as this behavior did change in V6.

customaware

You cannot put an edit in the query menu as
Aware does not know which record you want to edit.

In V6, having a default operation checked means that
operation will execute as soon as the record is selected
either by clicking ANYWHERE on the row or moving to that
row using the arrow keys.

robleer

@eagles9999

I do not understand.
AwareIM is giving the View, Delete and Edit action as an standard option you can choose when you define a query menu.

If Aware cannot determine which record is selected, then why are those options there???

And, when I select/click a record, why should Aware not know which record is selected???

aware_support

There is a big difference between operations defined in a query menu and operations defined for items of the query (in the dialog itself). Operations on items are placed next to each record and they do know which record they apply to. Operations placed in the menu are displayed above or below the query and they do not know which record(s) they apply to unless the user selects these records explicitly (the operation must be marked as "applicable to multiple" for this to work)

robleer

Hi Aware_support,

Ok, I understand what you are saying. But still: why can I choose 'Edit or View' then? I tried the Applicable to multiple, but that is not doing anything also.

I've added the screen I'm talking about as an attachment. If the Edit and View does not work the way I think it works, can you explain in what situation the Edit and View actions are working??
Just to learn from it.

customaware

Hi Robleer,

I posted a more detailed explanation of the new functionality over the weekend but it seems that it that it disappeared in the change over of forums.

So, let me explain again.....

In previous versions when you added an Edit operation it automatically was checked as Default which meant that if you clicked on a row then the Edit operation was triggered.

There were some issues with that methodology.

You had to actually click some text on the row....clicking space between text have no effect.
There was no way to capture a change row event.
Excluding the Edit button was not an option.

With the introduction of V6, the functionality has changed.

Let's look at the situation with no operation checked as Default. In this situation the only way to execute an operation such as an Edit is to display a Button to the right and force the user to Click the button.

Changing rows using the Up/Down Arrows has no effect.

However, if an operation IS checked as default (the most obvious being Edit) then that operation is executed EVERY time the user clicks ANYWHERE on the row.

It will also be executed if the user changes the selected row by using the Up/Down arrow keys.

Pros:
Allows dynamic changing of associated forms of row dependent data as soon as the row is changed.
Allows the same functionality using the Up/Down arrow keys.
Allows the developer to have an operation called just by clicking anywhere on the row rather than having to click a button.

Cons:
If you have a Button AND the associated operation is checked as Default then the operation will execute twice , once for selecting the row and a second time for clicking the button

You can set a flag to select the first row as soon as the form opens. ( I would rather have the option to just park on the first row rather than select as I doubt anyone would want to immediate execute the operation associated with the first row as soon as the form opens)

So, the best bet is to either....

a) Leave Default operation unchecked and force the user to click an Edit button, or
b) Hide the Edit button (NoText and No Icon) and then check the operation as Default. It will then execute as soon as the User clicks the row. You will want to turn Select First Row off I suspect.

I can assure you, you can not develop some seriously cool dynamic forms with this functionality. Check out the Customer form in the new CRM

Hope that helps.

robleer

Hi Mark,

Thanks for your help and advice. I appreciate that of course.

But thats not my point at the moment. I understand how it works, I can implement it and I can live with it. No problem.

My questions was: why can I choose in the query menu the Edit and View action if it is not working there? Is it not better to remove those options there?

customaware

Ah... I understand.

I had the wrong end of the stick.

Yes, I get your point and agree that if they are non functional from there then they should be removed.

Apologies for my previous ramblings. :oops:

robleer

Ok, no problem.

I only try to understand things and now I know I can ignore those actions.

Thanks,

Rob