No Attribute Level access in Access Dropdown

kklosson

I think this started when I updated to Version 5 which I did at build 1412, and I'm still on that build. I looked at the change log and I hope I didn't miss something, but when I work in Access Levels, the Access drop list no longer has the "Attribute Level' selection in the list. Many BOs are still listed as Attribute Level, but the selection is not available in the list.

It appears that I can assign Full access and still assign attribute level permissions, but it's not so intuitive.

Did I miss something?

Also, in general, many of these settings seem to have been wiped to Full Access. Is this just me?

Support, I could use some help here just to know how to proceed without too much re-work.

Thanks.

aware_support

We haven't changed anything in this area for quite some time. Are you sure you are having a problem? If you are, please send us your BSV with the detailed description of the problem.

kklosson

Now I see that what my problem is is that all radio button controls seem to be ignoring the access rights when set to read only. Can anyone else confirm or deny this under version 5 build 1412?

RocketRod

I can state that attributes shown as radio buttons are not greyed out as per other attributes when using the PROTECT rule. The user can move between the selected radio options , they are all in dark type as well but they cannot save the change they make so its not really a problem for me.

I WOULD LIKE ALL ATTRIBUTES TO BE NOT GREYED OUT WHEN PROTECTED! Please please support.

Cheers Rod

aware_support

Sounds like there is a bug with protection of radio buttons, but what do you mean "I would like protected attributes to not be greyed out". Are you referring to the issue that greyed out attributes are hard to see in IE? If this is the case, I believed it can be changed in the CSS style.

RocketRod

Yes thats right. How do I do it?

aware_support

You can experiment yourself using the IE developer tool. In this tool you can click on the element on the screen and see its CSS style properties. You can then change these properties on the fly and see the results immediately. If you manage to achieve something that you like, let us know and we'll do the rest.

kklosson

Let's not get too off track. The issue is that there seems to be a bug that radio buttons are not adhering to the protection policy. This is kind of a big deal to me and I hope for a resolution soon.

I can say for sure that in previous versions this was not a problem. Previously, you could not select a radio button that was set to Read Only for the current access level.

Forget the term "greyed out" - it doesn't mean anything. The issue is the property of the control, which in this case should be disabled.

RocketRod

I agree there are two issues here. My apologies kklosson I wasn't trying to hijack your issue.

The radio button issue should be fixed and I'm on the latest build 1420.
The lightness issue for browsers for read only attributes also needs to be fixed. It occurs in Safari as well as IE. Not sure what to tell you except my users need it darker in both browsers as they cant read them. Not sure how to use the IE developer tool and I'm not a CSS person. Maybe someone else can supply you with what we need as there have been many posts on this issue over time.

Cheers Rod

aware_support

The radio button issue will be fixed in the next release.

Regarding visibility of read-only items. Please try this:

Open the file AwareIM/Tomcat/webapps/AwareIM/aware_ext/resources/css/blue.css
Find the following line:
.x-item-disabled {
color:black;cursor:default;opacity:.8;-moz-opacity:.8;filter:alpha(opacity=80);
}
Change opacity=80 to opacity=100
Refresh the browser

This should make fields more visible. Let us know if this is better.

RocketRod

Made the change but I can see no real difference in both Safari and IE. Still far too light for users to read. Let me know if there is anything else you would like me to test.

Cheers Rod

Bryan

After making the above change I cleared the cache and did not see any difference.

rocketman

Just to add my voice - I flagged this up two years ago. I think it is a problem for sufficient numbers of us that AwareIM should do something as standard within the app - if for no other reason when we update the versions, we have to remember to do it all over again.

If this means putting some pressure on the EXT people then please - support, please do so because frankly - trying to read protected attributes is (not to put too fine a point on it) a real pain in the arse (thats ass for US based developers)

aware_support

Radio buttons protection issue has been fixed in 5.1

RocketRod

Thanks support for this fix.

However can you give an answer to all of us to when the other issue which to me is THE major issue which Rocketman and others also agree with, will be addressed?

This to me is the one and only major drawback to using this wonderful awareIM and has been around for a long time. Protect rules are a major feature of AwareIM but its impossible to use them. I for one would forgo any more enhancements to AwareIm until this one issue was addressed. Hoping you will have a fix soon.

Cheers Rod

aware_support

The problem is in IE - this is just how it displays read-only fields. The CSS setting that we pointed out is the only control mechanism that we have. We don't know what else we can do here.