Viewing a form allows tab lines to be edited

ask180

I have executed a query that returns a list of items. Each item in the list is configured with an Edit option, and a View option.

I choose the View option for an item in the list.

The appropriate form options in View mode, but its tabs show Edit and View options.

I would have expected opening a form in View mode would disabled the Edit option on its subordinate tabs.

Since it doesn't appear to, is there somewhere to configure a condition on the Edit option on tabs to not display if the form was opened by a View operation?

Gabbitas

If I understand what your trying to do and if memory serves me correctly, try creating a process that you can use to view your form that includes NOEDIT

Somthing like:

VIEW YourBO USING 'YourForm' NOEDIT

Then call this process from your View operation on query results.

rocketman

From the user guide. The difference between edit and view is that edit will stop the process and wait for the user to click save, whereas view will present the form but carry on processing further actions.

Gabbitas is tight - use the NOEDIT switch

ask180

Thanks for the responses, but they don't solve the problem.

I have an object, say Name, and it has multiple addresses, stored in an Address object.
I list all Name, and have Edit and View options next to each Name in the list.
I choose the View option for one of the listed Names. When the Name-main form opens, it has Addresses as a tab item. These addresses have Edit and View options. Because I opened the form in View, I would have expected the tabs to NOT show an Edit option.

The question is, how do I hide an Edit option in a tab when the main form has been opened by a View operation?

tford

You might have to configure two different forms for Addresses BO .. one that is called by the Edit operation of Names BO and one that is called by the VIEW operation.

One other option is like other posters are telling you. In the operations on the Names BO that call the Addresses, you can use a process to show the addresses and be sure the NOEDIT option.

rocketman

Another option would be - if this class of user should NEVER have edit rights on certain attributes, you can set their Access level so that they only ever have Read Only" access

ask180

Guys, thanks for the tips, but they still don't seem right. Maybe it's me, but the issue seems like a bug in AwareIM to me.

If you open a form via a View operation, the Save option is not there. However, open the same form via an Edit operation, and the Save option is there. Perfect behaviour, so the form knows whether it was opened by a View or Edit operation.

Given that, why then isn't that same approach carried through to the tabs on the same form. If AwareIM knows that the form was opened by a View operation, why not hide the Edit option on the tabs (or at least be able to configure that behaviour)? It hides the Add New option on the tab, so it must be possible.

I accept that, through having multiple forms etc, I can do what I want. I just think that I should be able to achieve what I want through default configuration.

ask180

Giving it further thought, another option would be if AwareIM exposed a function that stored how the form opened (ie: by a View or Edit operation). That way, I could put a condition on the Edit operations in the tabs to be invisible if the form opened via a View operation.

rocketman

Not sure where the "Add New" comes in. Are we talking Tab or a table of referenced items in the tab area?

ask180

A table of items in the tab area of a form.