E-FLUID: FLUID Page Ownerid Defaults to People Tools. (Doc ID 2110250.1)

Last updated on FEBRUARY 24, 2016

Applies to:

PeopleSoft Enterprise PT PeopleTools - Version 8.54 and later
Information in this document applies to any platform.


On : 8.54 version, Application Designer

When creating a Fluid Page in Application Designer, we are having to change our Definition Security.

When we create a Fluid Page in Application Designer, we have to change our Definition Security to allow update access to PeopleTools objects. We have always used the definition security in order to prevent accidental update of PeopleTools objects by making those read-only, and only unlocking them if we had a strong need to update a PeopleTools object (as has always been recommended in the past). We are finding that unless you have read-write access to PeopleTools object definitions, you cannot create Fluid Pages because the templates are all PeopleTools owned, and the page saves defaulted as owned by PeopleTools.

The owner of the new page should be blank.

The issue has the following business impact:
The Owner ID helps identify which applications team last made a change to a definition. It sets the owner to PeopleTools. This is causing the confusion


Sign In with your My Oracle Support account

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

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms