PeopleTools and Lifecycle Management - PSFT (MOSC)

MOSC Banner

Why reduce size of a Component Interface?

edited Mar 20, 2013 10:43AM in PeopleTools and Lifecycle Management - PSFT (MOSC) 3 commentsAnswered
We created a large CI based off a large component (Job Data in HR).  However we are only updating specific fields within.   What would be any real advantage of removing unused properties (records/fields) from the CI?  Are there performance gains? Not sure why that would be.   Is security a legit reason? But in our shop if you have the wherewithall to write peoplecode/ae process to access a CI, you can change the CI if needed.

Anybody cut down a CI to the minimum fields and regret it afterwards.  Did you find any advantages?

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