PeopleTools and Lifecycle Management - PSFT (MOSC)

MOSC Banner

XMLP Query Data Source protection

edited Mar 28, 2014 12:00PM in PeopleTools and Lifecycle Management - PSFT (MOSC) 5 commentsAnswered

Just curious what others are doing out there. 

We now have a handful of XMLP processes with PS Query Data Sources in production and are leaning in that direction more and more often.  Typically the process needs to be available to a wide range of users and is either a stand alone process (run control), integrated with an online control (button/hyperlink), or is placed within a Job with other delivered and/or custom processes.  The PS Query Data Source is a public query. 

How are you protecting the PS Query Data Source from changes by users with Query access? 

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

PSFT PeopleTools Tags

Instructions for posting

×

1. Select a discussion category from the picklist.


2. Enter a title that clearly identifies the subject of your question.


3. In the body, insert detailed information, including Oracle product and version.


Please abide by the Oracle Community guidelines and refrain from posting any customer or personally identifiable information (PI/CI).


Cloud / Fusion customers - Our Cloud community has moved! Please go to Cloud Customer Connect .


New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center