Need More Protection

vinsnash

I'm using the following rule:

If NOT(LoggedInRegularUser.LoginName=NSCPers.UnitCode) Then
READ PROTECT NSCPers FROM Unit

On an initial query the results are as expected. Only instances where NSCPers.UnitCode = LoginName are presented.

However, when the user clicks on the filter icon and selects "Extend" the rule no longer applies and all instances regardless of UnitCode are presented.

Can that filter function be disabled. We really have no use for it at this point and it is a major security problem for us as is.

Thanks

Vins Nash

tford

On the query in the config tool, uncheck the "Show 'Reduce/Extend Search' button"

vinsnash

Thank you again!

Vins Nash

vinsnash

Sorry, I spoke too soon. I unchecked that box and saved every query. The filter icon continues to appear and work in all queries. I've double checked each one. Box is blank but the filter icon still shows.

I really need to disable this if it is negating the rules I'm using.

Vins Nash

tford

You must not have published the bsv or something. Try changing the title of a query & make sure the new title also shows up in your tests.

vinsnash

Evidently if you have an unpublished version in the tree in addition to a new version you are working on some confusion reigns when you put the version you are working on in test mode.

V.1 Obsolete
V.2 Obsolete
V.3 Current
V.4 New
V.5 New

I'm making changes to V.5 and was keeping V.4 as a reference for some new features I might incorporate later. To make V.5 the object being tested I had to delete V.4. It seems as I was getting some of 4 and some of 5 in test mode or something like that. I renamed the query in V.5 and set V.5 to test.

When I logged into test mode the new name was not evident and no inconsistency was reported. After I deleted V.4 and set V.5 to test mode again the new name was apparent and the filter icon was gone.

Vins Nash