Page Comparison

1. Student PIDSPIDs: Testers should be prepared with at least 10-20 student PID numbers from their own department.

2. Funding information: Testers should be prepared with at least 5 PTF (project, task, funding source) or full CCOA strings.

   1. Need to work backwards from an AIDID you used in AY2324? Use the same OFC : ISIS : ProSAM Funding Code Map (Graduate FSU) Google Sheet to do a “reverse lookup”.

   2. Alternatively, double check with your fund manager or fiscal contact - they may have new funding strings that you can use for tests!

3. Scenarios: Testers should be prepared to recreate scenarios that have happened in real life. We’re looking to confirm that FSPT can handle single transactions, retroactive changes, funding changes, multi-month stipends, and more!

FSU will provide a test script scripts to help you document your test scenarios and report back to us the results.

More information on the timeline and schedule of testing coming soonThe below timeline is estimated, and subject to change based on the deployment of fixes for any additional issues uncovered in testing.

June 13 - June 14 (tentative): FSU will reach out to testers with instructions for the first test (see Testing Activities below)

June 17 - June 24: FSU will add new tests, testers will record results in test scripts, and ITS will deploy fixes

June 24 - June 28: additional information coming soon - UAT will help us solidify this timeline!

You can learn more about the project by visiting the ESR website or the Campus Partners Financial Support Payments Request Tool (FSPT) collab space.

• UAT FAQs (coming soon)

In addition to the specific user tests, we need your help to write the FSPT User Manual!

Please use the “suggesting edits” mode within the DRAFT: FSPT Manual document so that the FSPT team can track changes as bug fixes are deployed and new functionality

Note: this document is intended to be for all users; please suggest edits with that in mind. To prepare for training and hypercare, FSU will use this as the source document for creating training videos, knowledge base articles (KBAs), and other reference materials.

We want to hear from you! Please send your feedback to us using

For feedback on the testing process itself, please use this ⁠FSPT Tester Feedback Form Google Form.

To submit an enhancement request, please complete the FSPT Enhancement Request Form, which will open a service ticket.

Do not use either of these forms to report issues or testing outcomes from the test scrips – the script will include space for you to report specific notes on unexpected or failing results, so that issues can be tracked and resolved. More on that below!

Make a copy of this template (see instructions) and save it in this folder.

Use this link to log into Log in to the QA environment (URL provided in the test script sheet) and log the results of your test.