Attention: To align with new corporate security policies, and to match policies adopted by other communities within Oracle, the My Oracle Support Community access requirements will change beginning September 18, 2025. MOSC will now require that member accounts in our community be associated to a *corporate* email address. This means that users with generic domains (such as gmail.com, yahoo.com, and others) will no longer be granted access to the discussion forums and ideas labs. If this policy affects you, act now to change the email address that is associated with your Oracle (and community) account. Alternatively, you can opt to create a new Oracle account that uses your corporate email domain.

PeopleTools and Lifecycle Management - PSFT (MOSC)

Call to CI from Another Component "Wipes" Calling Component's Pending Changes

Oct 27, 2020 7:57PM in PeopleTools and Lifecycle Management - PSFT (MOSC) 2 commentsAnswered

PeopleTools: 8.53

Behavior:

User does something that triggers Save Processing (DoSave())
User has made or is making some changes to component buffer
Component calls (indirectly via application package) Component Interface to a 2nd component, saves changes. CI call is succesfull. Call is made in FieldChange or Component SavePreChange.
Component processor sets all of the fields from 2 to null / default value. Unchanged fields arent' affected.

So for example prior to CI call, STEP_NUM = 5. After CI call (which is a success) STEP_NUM = 0.00 (default value).

When I do a trace I don't see any rollbacks or anything setting (in the above example) the changed fields to their defaults.

Tagged:

component

0

Howdy, Stranger!

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

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

Category Leaderboard

Top contributors this month