S3. Scheduling Utility Usage
S.3.1 Scheduling a Single Container for Bundling To schedule a single container for bundle execution, simply use either of the container based stored procedures: xdoc_xutil_bundle_contSchedule, xdoc_xutil_bundle_contScheduleByRef
S.3.2 Staging Sets of Containers for Processing Scheduling Bundle Execution for a set of containers involves the following logical steps:
- Determine the set of containers for bundle execution. The set of containers is specific to the business purpose or use case that is trying to be accomplished. For example:
- All containers that have not been previously executed the particular Bundle Profile.
- All containers that have not executed the Bundle Profile within the last 30 days.
- Containers matching some set of conditions in the Integrated Application. E.g.: all closed Loans originating on or after January 1.
- Truncate and populate the axtdoc_xutil_bundle_proc staging table accordingly, adding 1 row in the table for each container / bundle profile combination that needs to be executed. Note:
- See the examples in the “bundleScheduleUtilSamples” directory for sample queries and database statements for populating the table.
- The staging table includes columns for both the Container Key (EG: Loan Id) and Container Ref (Eg: Loan Number) values from the Integrated Application.
- Since XDOC correlates documents based on the Container Key in the Integrated Application, using Container Ref values requires the TrustContainer parameter flag to be set on (1), so that the scheduling procedure will skip the validation check for existence of the corresponding container key in the XDOC database.
- Use the xdoc_xutil_bundle_procAll procedure to process all the rows in the axtdoc_xutil_bundle_proc table.