Welcome to Scribd, the world's digital library. Read, publish, and share books and documents. See more
Download
Standard view
Full view
of .
Look up keyword
Like this
5Activity
0 of .
Results for:
No results containing your search query
P. 1
People Soft Secrets

People Soft Secrets

Ratings: (0)|Views: 615|Likes:
Published by mymithraa

More info:

Categories:Types, Research
Published by: mymithraa on Sep 04, 2010
Copyright:Attribution Non-commercial

Availability:

Read on Scribd mobile: iPhone, iPad and Android.
download as DOC, PDF, TXT or read online from Scribd
See more
See less

07/29/2012

pdf

text

original

 
Dynamic Roles:
Why Dynamic roles ?1) The assignment of roles to User Profiles based on your business rules.2) These business rules run against system(s) to assign PeopleSoft access.3) PeopleSoft security changes in an automatically.4) The dynamic role rule process removes and grants access to User ProfilesPeopleTools > Security > Permissions & Roles >Roles (Dynamic Member Tab/Page).There are three ways can use to execute your rules to find the dynamic role users.o PS/Queryo LDAP Plug-ino PeopleCodePS/Query1) Access is removed or granted based on the User Profile IDs retrieved by the query.2) Logic to select the dynamic role users will be present in the SQL of the Query.
Note: - 
 
a) Use PSOPRALIAS_VW or PSOPRALIAS record to create the dynamic role queries.PSOPRALIAS - Used to store ID values corresponding to various ID types. For example, stores EMPLIDfor Employee type, CUST_ID for customer ID. It will be easy to join the tables based on the type of theUserid.b) Don't use any Bind variables in the role queries. They are not designed for resloving the bind variables.c) Use Disntict caluse in the SQL to make you always retrive uniques id only. Any duplicate will the thedynamic role asssignement.
PeopleCode
 1) Access is removed or granted based on the User Profile IDs pushed in to the system array variable%RoleDynamicMembers.2) This is used when logic is complicated and cannot be retried from the Query.3) Logic to select the dynamic role users will be present in the Peoplecode event (Record name, Field name, Event name , Function name.) should be provided in the dynamic members tab. 4)
fetch the value using create sql fetch the oprid values and push in to the system variable.Eg:- %RoleDynamicMembers.Push(&Userid);LDAP Plug-in
With a directory-based rule, you must assign directory groups. The PeopleCode Rule group box appearsbecause directory rules are implemented using the DynRoleMembers PeopleCode program. This programuses the Directory business interlink to retrieve user and group information from the directory. To view theprogram, open the FUNCLIB_LDAP record in PeopleSoft Application Designer. Click Assign DirectoryGroups to select a particular directory group that exists in your LDAP server hierarchy. For example, if youhave your LDAP server grouped by geographic region, your rule could assign a new self-service role to allusers in the North America group. Use the Directory Group drop-down list box to select the appropriatedirectory group value. The values are derived from the LDAP data that you import using the Directory GroupImport process.
Note :- 
When you click the button execute Dynamic rules button DYNROLE_PUBL Application engine is exequted.This app engine program reads Dynamic Role Rules, executes the rules, and publishes the results. Themessages are then subscribed to and the users are assigned to the appropriate roles. This program is
 
designed to run in an asynchronous mode, via the process scheduler.The DYNROLE_PUBL Application Engine does not update the database directly.Integration broker must be configured to handle Application Messaging.DYNROLE_PUBL application engine publishes messages to ROLESYNCH_MSG.
Access Peoplebooks from Applicaiton Desinger.Context Help for Application designer.
Follow the setps to configure F1 - context help for the application designer.Press F1 in the application designer to get the help based on the URL configuration below.It can take to the peoplebooks based on the context.Navigate to PeopleTools > Utilities > Administration > PeopleTools OptionsUnder the help option you can set the URL to the People books.URL needs to be in the following format.
%CONTEXT_ID% is the object name or context ID of the currently displaying page or dialog box.%LANG_CD% is the three-letter language code for the user's preferred language.Cntrl+F1 - can be used as alternative help URL to the website on the internet or the company's internalwebsite.
Invoking the Remote call from AE/CI Process
In PT 8.4x you need to follow a certain sequence prior to invoking the PushButton field. The basics oncalling COBOL from AE/CI PeopleCode is as follows. Note that "tweaking" may be necessary to get it towork.1. AE (Application Engine) needs to have restart disabled in order to use CommitWork() to force a commit tothe DB of the CI data.2. Set the CI's properties, except for the "Pushbutton" field (usually Y/N) used to kick off COBOL.3. Save the CI (call Save()).4. If Save is successful, call CommitWork().5. Set the CI pushbutton property (toggle it) to trigger the COBOL process.6. COBOL will run asynchronously. So you usually need to put a dummy loop to wait until it's doneprocessing to avoid having the next CI record "bump" into COBOL or in case you need to perform some postCOBOL processing of the record.
 
PeopleTools > Portal > Node Definitions The Base URI (e.g.
) is only available automaticallyin the context of a web server. If a process is not signed in via the web (e.g. ApplicationEngine), the Node definition specified in the function is checked for that Base URI. <!--[if !supportLineBreakNewLine]--> <!--[endif]-->
 
Open the Node Definition (PeopleTools > Portal >Node Definitions) and enter the Content URI (.../psc/...) and Portal URI (.../psp/...) on the Portalpage. These are used by the GenerateComponentContentURL andGenerateComponentPortalURL functions, respectively. By default these fields are empty. <!--[if !supportLineBreakNewLine]--> <!--[endif]-->
 
PeopleSoft Application Engine replaces this meta-SQL construct with a platform-dependent SQL statementthat updates the system catalog tables used by the database optimizer in choosing optimal query plans.Peoplesoft intends that you use this construct after your program has inserted large amounts of data into a temporary table that will be deleted before the end of theprogram run.For databases that either execute an implicit commit for %UpdateStats or require a commit before and/or after this meta-SQL, PeopleSoft Application Engine skips %UpdateStats in the following circumstances:• A commit is not allowed, as in within an Application Engine program called fromPeopleCode.• The program issues a non-select SQL statement since the last commit occurred. In such a situation, datais likely to have changed.• You are deferring commits in a select/fetch loop in a restartable program. PeopleSoft Application Engineskips %UpdateStats even if the previous condition is false.

Activity (5)

You've already reviewed this. Edit your review.
1 thousand reads
1 hundred reads
madhukandakatla liked this
nareshkumar09 liked this
Urban Hill liked this

You're Reading a Free Preview

Download
scribd
/*********** DO NOT ALTER ANYTHING BELOW THIS LINE ! ************/ var s_code=s.t();if(s_code)document.write(s_code)//-->