Problem with Conditions on Query Result operations

wings

On RegularUser I have created 2 attributes:

CanViewNames as Yes/No
CanEditNames as Yes/No

Which is set by the administrator of the system when the RegularUser is created.

I have then set up a Query and have created 2 operations:

VIEW which has an operation type of 'View Object' and a condition on this LoggedInRegularUser.CanViewNames='Yes'
EDIT which has an operation type of 'Edit Object' and a condition on this LoggedInRegularUser.CanEditNames='Yes'

The problem is that when a LoggedInRegularUser has CanEditNames='No' runs the query the Edit button is hidden but the attributes displayed still allow the user to click on the attribute that will then put them into edit mode.

This is a huge issue for us. Is this a bug where the list of results is ignoring the Edit condition??

aware_support

We'll investigate

technopak

Hi,

One option is to force the query results Edit and View operations to use a process rather than the object's default.

This will remove the ability of a user to click on the object and be automatically presented with the object's Edit form.

It's a nuisance if you want the entire line in the query results to link to the operation, but Editing or Viewing via a process gives you much better control. The user simply clicks on the button at the end of each line in the query results instead.

Hope I've understood your issue correctly.

Peter

wings

Thanks Pete that's a good workaround for the moment until the issue is resolved.

aware_support

This should be fixed in build 1238