The Assembly functionality is available on the SO, PO, and MA Transaction Types. This process assembles specific transaction tabs, all of the attached Terms and Conditions, and all of the Supporting Transactions attached to the transaction within a single formatted PDF transaction. Before the Assembly functionality can be initiated, all CGI Advantage transactions that support the Assembly Process must first be defined and configured on the Assembly Configuration table. Please refer to the ”Assembly Configuration” topic for more information.
The Assembly functionality allows you to generate an Adobe Acrobat version of the transaction on-demand when the Assembly Request link on the Header of the transaction is selected or when a transaction is processed with a Phase of Final, the system automatically generates a PDF transaction. Please refer to the ”On Demand Assembly Process” topic and the ”Automatic Assembly Process” topic for more information.
The Assembly process supports the fonts provided with Adobe. When a font within the source transaction differs from those supported by the Adobe infrastructure, the system will select a format as similar to the source transaction as possible. A list of supported fonts is:
Helvetica (normal, bold, italic, bold italic)
Times (normal, bold, italic, bold italic)
Courier (normal, bold, italic, bold italic)
Symbol
Zapf Dingbats
A site, at no additional cost can add to the fonts provided by Adobe by installing the fonts they require on site. This process is described in the CGI Advantage Assembled Transaction: Formatting Objects Processor User Guide.
The Assembly Request page allows you to view the current and previous status of the Assembly Process submitted by the current user for the source transaction associated with the Assembly Request action. Refer to the "Assembly Request" topic for more information.
Once the Assembly Process job has completed and the PDF transaction is generated, if there is a previous version of a PDF attachment for the same version of the transaction, the system deletes the prior version of the PDF attachment and attaches the most current version of the PDF for that version of the transaction. For example, if a transaction is in a phase of Draft (Version 1) and you have selected the Assemble Transaction action, the assembly process generates the PDF Version 1 based upon the information entered in Draft Version 1 of the transaction. If you make changes to the Draft (Version 1) of the transaction, submit the transaction to Final and then again select the Assemble Transaction action, the system deletes the prior PDF version and generates a new PDF attachment.
If a finalized transaction is modified (Version 2) and you select the Assemble Transaction action, the assembly process generates a PDF for Version 2 of the transaction. In this example, when Version 2 of the transaction is submitted, the generated PDFs for both Version 1 and Version 2 are attached to the transaction and available for you to view.
The PDF file is available on the Header as an attachment with the Attachment Type of Assembled Form. The generated transaction can then be downloaded from the transaction Attachment page. If the transaction is a Solicitation, then the PDF will also be available to vendors in Vendor Self Service by clicking on the PDF button on the Solicitation Details View page.