As the task requirement specifies that the information about inconsistent data has to be passed to the BusinessWorks Process, you need to drag the table BAD_DATA from the Project View to the list of Output Tables:
The transaction creates the text file with each team’s statistics, and the content of the output table BAD_DATA is displayed in XML format inside the Console area of the UI:
As the transaction is now tested and ready for use, it is important to change the table type for TEAM_STATS back to type TEM. This table is designed to hold temporary information only kept for the duration of the database transaction and we switched its type to SES (kept for the life span of the session) so that we could inspect its content during the development cycle.
In production, the assumption is that we always start the transaction with no data in the TEAM_STATS table, and if it was left as SES type, it would accumulate the information from every invocation within the same session.
Session (SES) tables are used in TIBCO Object Service Broker applications mainly to transfer data across the database transaction boundaries. It is extremely important to use SES tables with caution and delete their content immediately when it is not required by the business logic.