E-FTP: PeopleTools Add Attachment test utilities functionality does not handle the %Attachment_Rejected aka return code 21
Last updated on OCTOBER 05, 2016
Applies to:PeopleSoft Enterprise PT PeopleTools - Version 8.54 and later
Information in this document applies to any platform.
As background, the test utilities page and the code behind is advertised in PeopleBooks as a demonstration application.
But customer admins and Oracle support are using this as a testing component for file attachments functionality mainly due the registration of this component under PeopleTools, Utilities, Debug, PeopleTools Test Utilities folder, which tells this is a debugging tools component..
The code stored in FILE_ATTACH_WRK.ATTACHADD.FieldChange does not reflect all the changes in file attachment core technology
Note that in fact currently this outdated coding sample is used as a coding "template" by customers and by Oracle product developers, and in that case this should at the very least, reflect the recent functionality changes and should handle all of the possible return codes from the internal function.
The Test utilities page and the suppressed error messages inside this component are of no use for files that fails to reach the storage location because not all return codes are handled or due to the fact the error messages during add attach operations are suppressed
E.g. Security admins wants to test attaching files and are using currently the Test utilities for testing all attachments new features, while the new file attachment file extension restrictions and the return code 21 is not handled.
Anyhow due to the suppressed error reporting this component is not giving directly any feedback to the security admins implementing as well other new features like virus scanner while new return codes are handled but feedback to user (error) is absent in the Test utilities component.
Everything spins around the call that happens in the test utilities (with suppressed errors reporting) and due to the fact that FILE_ATTACH_WRK.ATTACHADD.FieldChange sample code is rather obsolete, and it currently handles wrongly some old return codes that are not published anymore in our recent PeopleBooks while oppositely the new #21 return code is not handled at all.
That’s confusing to both customers admins and PeopleSoft developers.
e.g. Return codes 4 & 5 are still handled in PT 5.55 code used by Tools test utilities, while these seems to be rather obsolete due to the new streaming implemented in 8.52.
Note that documentation wise, starting with PeopleBooks 8.52, Oracle removed any references to these #4 & #5 return codes while additionally added return codes for virus scanner and file extension restrictions (new return codes #13 up to #21) and these changes are not reflected consistently in the tools delivered code sample under FILE_ATTACH_WRK.ATTACHADD.FieldChange, used as reference in Test utilities and by PeopleBooks notes
Ref to 8.49 PeopleBooks (search for AddAttachment)
vs. 8.52 PeopleBooks
File attachment functions were modified between 8.49 and latest tools releases 8.5x and new return codes were added
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