| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 1032.1 | Take off /SUPER. It's OK to read the APR now :-) | IOSG::ALLAN | Derek, DTN 830-3669 | Mon Jul 13 1992 19:29 | 35 |
| Strangely, the answer to your problem is to take off the /SUPER form
qualifier. However, leave the FMS Supervisor-only attribute on the
FMS field. You will find that /SUPER is only needed when you wish to
nominate a user as the only supervisor e.g. /SUPER = LOG$THE_MANAGER.
If you miss off /SUPER then the Supervisor-only field will be enterable
by those with PRVSUP. The field will appear as a display-only field to
those without PRVSUP.
In 2.4 the behaviour of /SUPER is at odds with the documentation.
As /SUPER was fairly unusable in 2.4 we decided to fix the code
rather than fix the documentation. In version 3.0 /SUPER works as
the APR says it does.
In 3.0 /SUPER=username nominates the only user who is allowed to
enter FMS fields on the current form which have the SUPERVISOR-ONLY
attribute. Additionally, if there is no /SUPER form qualifier, but
the user has the PRVSUP profile flag set, then the user is allowed
to enter SUPERVISOR-ONLY fields.
The 2.4 problems were:
1. When a non-supervisor TABbed to a supervisor-only field, the
non-supervisor was thrown off the form.
2. Once supervisor capabilities were turned on by /SUPER they would
not be turned off again!
These are fixed in 3.0. If you use /SUPER without giving the
qualifier a value, it means /SUPER = nobody. That is, no one
can enter the supervisor-only fields. If you miss off
/SUPER altogether then everyone who is a supervisor can enter the
supervisor-only fields.
Cheers,
Derek
|
| 1032.2 | Does supervisor only really work in V3.0 with ENTRY? | SHALOT::WARFORD | Richard Warford @OPA DTN 393-7495 | Tue Jul 14 1992 00:42 | 8 |
| Does this mean the use of supervisor only fields now works on ENTRY
forms in V3.0? In the past this wouldn't work as at some point during
processing, the field would be made display only (Either key field
entry setting non-keyfields to display only, or non-key field entry
setting key fields not enterable). You would then get an error about
supervisor only not allowed on display only fields from FMS.
Rick
|
| 1032.3 | | IOSG::ALLAN | Derek, DTN 830-3669 | Tue Jul 14 1992 10:17 | 13 |
|
No, that problem still seems to exist. The error message I get is
-FDV-E-DSP, Get-type call is illegal for Display Only field
when the key field of an Entry form is given Supervisor only. You
get the error whether or not your a supervisor.
Was this problem introduced during 3.0? I don't see how the
form described in .0 would work if this bug was in 2.4.
Cheers,
Derek
|
| 1032.4 | more clearly ... | MLN08::COLOMBO | | Tue Jul 14 1992 15:23 | 8 |
| With ALL-IN-1 2.4 ITALIAN, a user with PRVSUP=N doesn't work with an
entry form with the "Supervisor only" attribute to the key field
(without using /SUPER form qualifier).
How can we obtain the same with ALL-IN-1 3.0 ?
Roberto AGIP Colombo
SW - Milan, Italy
|
| 1032.5 | | IOSG::ALLAN | Derek, DTN 830-3669 | Tue Jul 14 1992 16:57 | 27 |
|
re .4
The reason a problem has appeared with Entry form processing is
that Supervisor-only fields are enabled for supervisors during
form pre-processing. Pre-processing for Entry forms doesn't happen
until after the key fields have been processed.
The bottom line is that putting the FMS supervisor-only attribute
on the key field of an Entry form makes the field unenterable by
anyone.
The sort of work-around you might be able to use is the one which
we use for profile, that is, create a menu option of form DEFAULT
which goes
;;MYENTRYFORM;;
.IF OA$PROFIL_PRVSUP == 0
THEN
GET OA$DISPLAY = "You are not a supervisor"
ELSE
FORM MYENTRYFORM
Cheers,
Derek
|
| 1032.6 | Old bug... | SHALOT::WARFORD | Richard Warford @OPA DTN 393-7495 | Tue Jul 14 1992 18:41 | 5 |
| re: .3 No Derick, the problem with ENTRY forms was noted and I thought
release noted in V2.0 days. I don't think ANY version of ALL-IN-1 has
allowed this since then.
RIck
|