WebDocs provides for the listed WebDocs iSeries commands to call exit point processes. Customers can also program their own special logic into WebDocs as needed.
Listed below are the current built-in exit points.
DOCCHKIN command - Adding a new document to WebDocs
Pre Check-in Exit
Before the document gets checked in to WebDocs, the Pre Check-In Exit program is called. The Pre Check-In Exit program can validate document keywords and send back an error response message to the user. If the Pre Check-In Exit fails, the DOCCHKIN command will not complete the document check-in without the user first fixing the error.
By default the program DOCEXITPC in the user's library list is called. The template CL program for DOCEXITPC can be found in file: SOURCE in library RJSIMAGE.
Note: The compiled program object should always be compiled into library RJSIMAGE although a copy of the source should be made to a user library.
Post Check-in Exit
After a new document gets checked in to WebDocs, the Post Check-In Exit program is called. The Post Check-In Exit program can backfill index values into a new document from a user database or can perform pretty much anything that an RPG or CL program can accomplish. You should always make sure the Post Check-In Exit program exits normally because the document has already been saved to WebDocs. If there is some user logic (such as customer# does not exist) where you want to notify someone of the error, you can do so through your RPG or CL logic, but always make sure DOCEXITC ends normally.
Recommendation: When calling the post exit process, submit the post process logic to batch to prevent holdups if your custom CL or RPG program fails.
By default the program DOCEXITC in the user's library list is called. The template CL program for DOCEXITC can be found in file SOURCE in library RJSIMAGE.
Note: The compiled program object should always be compiled into library RJSIMAGE although a copy of the source should be made to a user library.
DOCINFOUPD command - Updating document keyword information
Pre Update Exit
Before the document keywords get updated, the Pre Update Exit program is called. The Pre Update Exit program can validate document keywords and send back an error response message to the user. If the Pre Update Exit fails, the DOCINFOUPD command will not complete the document keyword updates without the user first fixing the error.
By default the program DOCEXITUPC in the user's library list is called. The template CL program for DOCEXITUPC can be found in file SOURCE in library RJSIMAGE.
Note: The compiled program object should always be compiled into library RJSIMAGE although a copy of the source should be made to a user library.
Post Update Exit
After a document's keywords have been updated, the Post Update Exit program is called. The Post Update Exit program can backfill index values into an updated document from a user database or can perform pretty much anything that an RPG or CL program can accomplish. You should always make sure the Post Update Exit program exits normally because the document details have already been saved to WebDocs. if there is some user logic (such as customer# does not exist) where you want to notify someone of the error, you can do so through your RPG or CL logic, but always make sure DOCEXITUC ends normally.
Recommendation: When calling the post exit process, submit the post process logic to batch to prevent holdups if your custom CL or RPG program fails.
By default the program DOCEXITUC in the user's library list is called. The template CL program for DOCEXITPUC can be found in file SOURCE in library RJSIMAGE.
Note: The compiled program object should always be compiled into library RJSIMAGE although a copy of the source should be made to a user library.
