Secure the UserID box on the Submitted Job Search screen?

Hi all,
Can anybody please advise me how to secure the UserID field in the
Submitted Job Search screen so that a user cannot change the User ID?
(This is Program P986110B, form W986110BA. I can access two versions of
the form ZJDE0001 and ZJDE0002.)

What I really want to achieve is to allow users to access their own
reports, but not the reports of other users, which may contain financial
information confidential to individual divisions within the company.

I have thought of one way to achieve this, by applying row security on
F986110. But this needs to be configured separately for each user,
specifying their individual user ID by name.

A second question: Even though there are the two versions of this
program, when I search for them in the Interactive Versions program, no
versions are displayed. Why is that? (You can access one of the versions
by typing WSJ in the fast path, and the other from the Form exit in
Batch Versions.)

Thanks,
Mark Suters
ERP 8, Update 1, SP21G1, W2K, SQL Server 2000, Citrix
#####################################################################################
Note:
This message is for the named person's use only. It may contain confidential,
proprietary or legally privileged information. No confidentiality or privilege
is waived or lost by any mistransmission. If you receive this message in error,
please immediately delete it and all copies of it from your system, destroy any
hard copies of it and notify the sender. You must not, directly or indirectly,
use, disclose, distribute, print, or copy any part of this message if you are not
the intended recipient. Stockland and any of its subsidiaries each reserve
the right to monitor all e-mail communications through its networks.

Any views expressed in this message are those of the individual sender, except where
the message states otherwise and the sender is authorized to state them to be the
views of any such entity.

Thank You.
#####################################################################################

Hi Mark

I am not sure about security, but an alternative solution (a minor mod) is to conditionally disable the User ID field in the form design for P986110B. The conditions themselves you could either hard code or maybe set up in a custom UDC table.
As far as the two versions are concerned, there really is only one version (or more precise there really is no version) of submitted job search. The fastpath 'WSJ' first calls P986116 and then calls P986110B, whilst the row exit calls P986110B directly.

Hope this helps,

Mark,
Set up column security for the user/group as follows:-

form name data item view add change alias
W986110BA UserId Y N N USER

Regards

Darren


DISCLAIMER:
The information contained in this email is intended for the named recipient only. It may contain confidential information. If you are not the intended recipient, you must not copy, distribute or take any action in reliance on it. Please note that neither Petroplus UK nor the sender accept any responsibility for viruses and it is your responsibility to scan attachments (if any).



Regards

Darren Evans
CNC Administrator
Win2k SP3, Oneworld Xe U5, SP21_F1, SQL Server 2k SP3, Citrix Xpa FR2

Hi Mark,

You can achieve this with column security (Form exit within security workbench), it's relatively straight forward but if have problems let us know and I will post more detailed instructions.

HTH

You can do this by creating a new interactive version (IV in fastpath),
and just modify the processing options. There is an option for whether you
wish to run the program secured or not. Then just modify the version that is
being called from the menu the user is running.

-John

-------------------------------------
OneWorld B733.3 (XE)
SP 19.1_B1, Update 6
Win2k Server SP3
SQL 2000, SP2
Metaframe XPa v1.0/SP3
-------------------------------------





Xe, Update2, SP16
SQL2k, Win2k
Metaframe 1.8a

Hi Mark,
Why not just use the processing option ? It allows you to have no security, security by group or security by user.
Regards,
Dave

Mark,

As mentioned already, have your users run P986116 instead of P986110B, and you can use the P986116's processing option to restrict which submitted jobs can be viewed. Values for the processing option are: blank - see all jobs; 1 - see group's jobs; 2 - see only user's own jobs (which we use). In addition, I found that sometimes people got into P986116 from other places in JDE which I didn't know about, and used the ZJDE0001 version, which has the processing option set to blank. This defeated our security efforts, so what we did was change both ZJDE0001 and ZJDE0002 versions to security setting 2. Then we created a new version (in our case WAG0001) which only was given to our IT staff, which has the security setting of blank (view all jobs).

Use column security on P986110B

we used column security for *PUBLIC then granted security back to the individual group/users that are allowed to view all jobs, i.e. group ITADMIN, and HRPAYROLL, and ACCTPAYROLL.