Abstract: Embodiments described in the application provide for reports that are generated in many different formats using an Approval Workflow Engine (AWE) and an XML Publisher (XMLP) component. The AWE can accept user parameters to extract data from at least one data source, transform the data, and generate a structured XML data file appropriate for the report. The AWE can pass this XML file, along with at least one report template and other necessary information to the XMLP, which is able to generate reports in any of a number of specified formats. Such an approach keeps the data separate from the formats and components, and allows for multiple reports to be generated without accessing an application for each format. The AWE also can store an audit history record for each transaction passing through the AWE in order to provide a concise location from which to retrieve the information.

Abstract: Embodiments described in the application provide for reports that are generated in many different formats using an Approval Workflow Engine (AWE) and an XML Publisher (XMLP) component. The AWE can accept user parameters to extract data from at least one data source, transform the data, and generate a structured XML data file appropriate for the report. The AWE can pass this XML file, along with at least one report template and other necessary information to the XMLP, which is able to generate reports in any of a number of specified formats. Such an approach keeps the data separate from the formats and components, and allows for multiple reports to be generated without accessing an application for each format. The AWE also can store an audit history record for each transaction passing through the AWE in order to provide a concise location from which to retrieve the information.

Abstract: Approval routing and processing is provided in a multiple job environment by providing the ability to pass job information through a universal class, along with information for the employee submitting a transaction for a approval, to an Approval Framework. An engine of the Approval Framework determines whether a routing is necessary, and a user list object of the Approval Framework contains the logic necessary to determine the appropriate person to which to route the transaction, using the employee and job information for the transaction. The Approval Framework also writes the job and employee information to a database such that the logic can be reconstructed outside transaction processing or for subsequent processing, such as to determine a status or path of the approval process or to determine a subsequent person or department to approve the transaction.