UDC security...

I'm curious as to how other people have handled UDC security. I need to
allow certain people Add access
to certain UDCs only. I was thinking about handling this with row security,
but row security is not
turned on by default on data item RT. Has anyone turned this on? Did it
work?

Thanks,
--Scotti Whitmire
DeRoyal Industries
Xe Update 2, SP16 (011, 016, 018), AIX4.3.3, Oracle 8.1.6

We secured the UDC table using row security and as you stated, did have
to turn on row security for the DD item. We have not had any issues at
all with securing the UDCs by this method, although we were slightly
burned more from a business process perspective...more employees needed
to be able to change/add UDCs than we initially believed, so we had to
teak our access list from what we initially deployed. Other than that,
no issues.

John

----------------------------------------------------------
OneWorld Xe (B733.3)
Update 2, SP 16
Oneoffs: SP16_011, _018, _019
Running on: NT4/SP6a, SQL7/SP3
Windows TS/Metaframe 1.8
----------------------------------------------------------






Xe, Update2, SP16
NT/SP6a, SQL7/SP3, WTS/Metaframe 1.8

You have to set row security on F0005 on Data Item "UserDefinedCode"
(combines the two keys as one). You have to define the from and thru values
as if you're doing the whole key.... it does indeed work, remember to
include necessary spacing, etc.

Lori
OW Xe SP16 Update 2
AS400 V4R5
NT
Citrix
email: [email protected]

OHHH, the Alias is KY, that's what you set it on in the Data Dictionary.....

Lori
OW Xe SP16 Update 2
AS400 V4R5
NT
Citrix
email: [email protected]

Just a few comments regarding UDC security on the F0004 and F0005......don't
do it.

UDC security is really really awefull in OneWorld. Picture this, I've got
two UDC's one is 00/ST the other is 98/ST.

If I put security on the F0004/F0005 for 'ST' then I've not only locked out
00/ST and 98/ST but all instances of ST.

Obviously row security on the F0004/F0005 will only really wotk if you never
duplicate any code values.

As an alternative I just use table security, ie.F0101, F0301, F0401, F0911,
F0902, F0901.

By the way, JDE does suggest using the 'bad' method in one of their
Knowlegde Garden articles. However, they forget to mention the fact that
you're caueing yourself hugh problems for the future.

Colin

Colin Dawes, MSc
City of Guelph
B733.2 SP 16.0_006, Oracle 8.1.6.3.4/NT, FAT & TSE

This may be simplistic for your needs; however, this is how we've started out. We've set application security on the UDC revisions program P0004A. We've allowed access for our implementation team and administration members only. All other users are denied access to this program.

Any new codes or code changes must come through a team member.

Walt Sellers
Heil Environmental Industries, Ltd.
OW B733.2 SP10, Citrix, Windows NT TS2000, Oracle 8.1.6