PeopleTools and Lifecycle Management - PSFT (MOSC)

MOSC Banner

Workaround for "Corrupt" Data Generating CDATA XML

in PeopleTools and Lifecycle Management - PSFT (MOSC) 3 commentsAnswered

PT 8.58.10, HR/FS 9.2

TLDR: users paste entire word documents into JOBCODE and POSITION DESCRLONG field, which causes the IB to wrap the entire message as CDATA because of all the weird characters. Can't fix this with a TRANSLATE program, since the data is generated AS a giant CDATA blob that can't be manipulated.

We can't modify the default VERSION_2 of this message to exclude the field, since it's already in use.

We could make our OWN message that doesn't include DESCRLONG, but then we'd have to change the default message which seems weird.

We could customize FULLSYNC program and delivered peoplecode to clean this field before generating the message, but that seems like a terrible idea (both are generic).

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