HP Exstream and PeopleSoft Application Engine

In PeopleSoft Application Engine, a step can contain multiple actions of different types (SQL, PeopleCode, Do While, Do When, Do Select, Do Until, Call Section, etc.). The maximum number of actions that can be defined within a single step is 8. Actions are executed sequentially within the step according to their order and type-specific behavior.

In PeopleSoft Application Engine, while a step can define multiple actions, only a limited number can be actively executed at runtime. The maximum of 7 actions can be used concurrently within a single step during execution. This is a runtime constraint distinct from the definition limit.

Data between steps in a PeopleSoft Application Engine program can be passed using multiple mechanisms: State records (to persist values across executions), temporary records (for intermediate storage within a program run), and Component/Global PeopleCode variables (for sharing data in the same session). All three methods are valid depending on the use case.

In PeopleSoft Application Engine, SQL and Call Section actions are mutually exclusive and cannot be defined within the same step to prevent database lock contention and execution ambiguity. All other listed action combinations, such as conditional do loops (Do While, Do Until, Do When), can co-exist within steps.

In PeopleSoft Application Engine, Do Select actions can be configured as Select/Fetch (to loop through a rowset), Reselect (to re-evaluate the query on each loop), or Restartable (to keep track of checkpoint state). Since all three are valid, 'All of the above' is the correct option.

PeopleSoft Application Engine has a limitation of 99 temporary table instances that can be defined and used within a single AE program. This is a hard limit in the system architecture. Temporary tables are crucial for parallel processing and managing multi-user execution scenarios.

In PeopleSoft Application Engine (AE) programs, the core components are Actions, Steps, and Sections which form the hierarchical structure. Events are not part of the AE program structure itself - events are triggers that can invoke AE programs, but they exist outside the program definition.

When an Application Engine program is loaded into memory in PeopleSoft, the physical tables that the program will operate on are locked to prevent concurrent modifications. This ensures data integrity during program execution and prevents conflicts from other processes.

HP Exstream (now OpenText Exstream) is a document automation tool used for enterprise document creation across multiple channels. Option A correctly identifies it as a Document Automation Tool. Option C correctly describes it as a single platform for designing documents across an enterprise. Option B is too vague ('Software tool for Communication' could describe many tools). Option D is partially correct but not the primary definition - it does combine these elements but this description is less accurate than A and C.

HP Exstream 7.0 introduced enhanced support for barcodes and table of contents (Option A) and added the Dialogue line module (Option B), which improved interactive document capabilities. These were significant feature additions in version 7.0. Options C and D ('Support for inclusion of components/images') are too generic - basic support for these existed in earlier versions and is not the distinguishing feature of 7.0. The question tests specific knowledge of version 7.0 enhancements.

When configuring table properties in HP Exstream, the option 'Repeating header, except for the first page' ensures the table header appears on all continuation pages but not redundantly on the first page where the table starts. This is the standard behavior expected in multi-page tables. Option A would repeat the header on every page including the first (appearing twice). Option C is not a standard HP Exstream option. Option D appears to be a typo ('Headrer') and is not a valid option.

The question asks when a table should be composed if it needs to be created when the page is created. The matching event is logically when the page is created. Other events like end of page or end of customer occur at different stages of the document lifecycle.

Table-based approaches provide structured layouts ideal for letters and statements where content needs consistent positioning across rows and columns. This approach maintains alignment better than free-form textboxes or frames, making it the standard for document generation systems.

Leaving empty pages blank preserves them in the document structure, ensuring page numbering remains accurate and continuous. This option counts blank pages in the total page count, unlike replacing them which would remove pages entirely and disrupt pagination.

Locked components cannot have their properties modified - that is the purpose of the lock mechanism. The lock prevents accidental or unauthorized changes to component configurations, maintaining stability in the application design.

Dialogue supports multiple input file formats including columnar files (structured data in columns), XML files (structured markup data), and live files (real-time data sources). PDF is not a supported input format as it's primarily an output format.

Warnings and errors during packaging indicate potential issues with the application deployment. Fixing these ensures the application package is complete and functional, preventing runtime failures or deployment problems.

Variables declared in one application folder can be used in another folder if the development environment supports global or shared variable scope. This depends on the specific application architecture and variable declaration mechanism.

In ETL/data mapping, every mapping requires source data to read from, targets to write to, transformations to process data, and links/connections to connect these components. Options B and C are incorrect because they mix execution components (session, workflow) with mapping components. Option D omits the essential source and target components.