Successful implementation of the Super PDF Extension requires careful planning, detailed requirements gathering, and active participation in testing. Bonterra follows a defined methodology to ensure each CyberGrants extension meets customer expectations and functions reliably within the system. 

The following steps will guide you through the implementation process for this extension, from initial planning through post-implementation management best practices. 

Pre-implementation planning 

Step 1: Define requirements 

Identify which proposal types will utilize the Super PDF functionality and determine the specific data fields and attachments to be included.  

Consider any optional data from organization records you would like to include (e.g., approvals, impact reports). 

Step 2: Coordinate with your Business Analyst 

Engage with your assigned Business Analyst to review your desired functionality, data mapping needs, and governance processes.  

• This discussion ensures alignment with platform capabilities and scope. 

Step 3: Evaluate resource availability 

Determine the internal team members responsible for reviewing and testing the Super PDF functionality, including timelines for User Acceptance Testing (UAT). 

Step 4: Understand customization boundaries 

Familiarize yourself with the constraints of the standard extension. Custom logic or post-implementation changes may incur additional cost and require separate scoping. 

Implementation process 

Step 5: Configuration and field setup 

CyberGrants will add a designated internal field (e.g., “GENERATE PDF ALL”) to the request view.  

• This field serves as the trigger for PDF generation. 

Step 6: Data mapping and logic development 

Work with your Business Analyst to finalize the criteria and logic used to gather and display data in the PDF.  

• This includes both request and optional organization data. 

Step 7: Functional Requirements approval 

Review and sign off on the Functional Requirements document before development begins.  

• Modifications after this point may impact project scope or schedule. 

Step 8: Conduct User Acceptance Testing (UAT) 

Thoroughly test the Super PDF functionality in a non-production environment.  

• Confirm the accuracy of the included data, formatting, and output files. 

Step 9: Provide sign-off for deployment 

No deployment to the production environment will occur until the customer formally approves UAT results and the extension meets all agreed-upon requirements. 

Post-implementation management 

Step 10: Establish internal usage protocols 

Ensure internal users are trained on where the Super PDF trigger is located and how to generate the files. 

Step 11: Download and store files externally 

Because CyberGrants does not store generated PDFs, plan to download and store documents on your organization’s systems as needed. 

Step 12: Plan for change requests annually 

Remember that only one update to this extension is permitted per calendar year, and all changes must fall within the original extension scope. 

Step 13: Monitor output as data evolves 

Regenerate Super PDFs when request or organizational data changes to ensure up-to-date documentation. 

What else do you need help with? 

• What is the Super PDF Extension?

Not what you’re looking for? Navigate to Super PDF Extension Overview 

Looking for training?

Explore this feature at your own pace - access training video content or watch a recorded webinar by clicking the link below.