Separate forms for access levels

vinsnash

I've created two forms for an object and specified which access levels use which form. All well and good except when I divide the access levels between the "Use" and "Don't Use" blocks I have to indicate Create and Edit for both groups or I can't save. In the form were I don't want any changes to be possible I have moved those access levels to the "USE" side when I try to save I get a "Edit" not specified error message for each of those access levels. So I specify Create and Edit for both groups and save. When I run the application it still uses the same original "main" form for all access levels regardless of being in the "Use" or "Don't Use" group..

I've tried following the user guide but can't decipher the forms editing.

This is meant to be a work around for the problem that placing a condition on a delete operation for a reference has no effect in the version I'm using.

Any help greatly appreciated.

pbrad

Hi,
The forms will default to the assigned access level unless the form to be used is specifically defined in your rule or process. Have you checked them to make sure that you have not specified the 'main' form?

Cheers,
Pete

vinsnash

Hi Pete,

I copied the 'main' form for the object. Gave it a new name and title. Removed unnecessary attributes from the display and all operations on references. I then moved the access levels for the form to the "Use" block and moved the others to the "Don't use" block.

I went back to the main form and did the reverse. Move the "view only" access levels to the "Don't use" block and the "admin" levels to the "Use" block.

No matter what access level I log on as the "main" form with all the attributes and operations on the references is display.

Other than that there are no business rules specified for the BO and the objects to select for viewing are presented in a query result.

I don't know what else to do. What appears odd to me is that I can't specify access levels without also selecting either the 'Use to create' or 'Use to edit'.

Also, I'm still waiting for a management decision. The new boss is not ready to move on it yet.

pbrad

Hi,
If you would like to shoot me the bsv and let me know the BO/forms involved I can take a quick look at it for you if you like.

Cheers,
Pete

vinsnash

I solved the problem. Its the query that determines what form to use for the "show" operation making all access level selections in the actual form irrelevant. You need a separate query for each form.

Something else for the AwareIM for Dummies book!

Vins

pbrad

Hi,
Actually, you don't need separate queries. If you use 'Use default editing form' when defining the query operation it will use the default form for the logged in users access level. You must have something incorrectly configured somewhere if this doesn't work for you.

Even if this wasn't the case, you still wouldn't need separate queries. You could have multiple operations and hide them conditionally based on the logged in users access level but you don't need to do this in this case.

Cheers,
Pete

vinsnash

Actually, I don't see a "default edit form option" anywhere in the query configuration forms. On the main query tab there is a form selection that allows one or the two forms defined for the object. In the query details section each operation "Edit", "Delete", "Show" etc also allows only selection of one or the other of the two defined forms and then shows that form name in the "Operand" field of the operation.

What I have works the way I want it. "Admin" level can add/change/delete and the "view only" levels only get to look.

Vins