Oracle PeopleSoft Grades Product Integration:
We request that the Grades PI for Oracle PeopleSoft is enhanced as follows:
1. In App Manager > Product Integrations > Grades Instance configuration page, under API Configuration:
- Below the URL to retrieve the information field, add two additional fields for the entering the two query names (allowing institutions to apply their standard naming conventions for their two queries) and then use/declare these institutional query names as variables in the solution code to replace the default names.
2. Provide an additional Test API Connection facility, or extend the existing test facility, to enable us to test the second API from the configuration page so that one can test whether it is working and provide a way to troubleshoot it if it is not.
3. Consider creating a Grades PI that uses one query with two or more variables which are declared as was done with timetables API.

4. If none of the above are feasible, improve the Grades PI guide to be more explicit in its instructions, making it clear that one has to use the default naming convention for the two query names (which is contrary to best practice), and clarifying how the second query associates the terms called in the first query against a specific user ID to the second query calling grades against terms (if only the term parameter is used, as it stands in the documentation, then it will call all grades, not those associated only to a user ID).

Motivation/justification for these requested changes:
• Change request 1: This change will allow a broader number of institutions using PeopleSoft to adopt this Grades PI without contravening their PeopleSoft API naming policy.

• Change request 2: This would provide a facility to fully test the Grades PI queries, as is provided in the other product integrations.

• Change request 3: This is more of a request to investigate simplifying the grades PI, if there was one query to test, then change request 1 and 2 additional fields and test facility would not be required, as the query name could be referenced in the URL to retrieve the information).

• Change request 4: We wasted a lot of time trying unsuccessfully to get this query to work (using our own unique query names, which is the standard practice), when we were told one has to use the exact query names specified in the examples. If the documentation is more explicit, it would save organisations a lot of time in getting this query to work. Also indicating what needs to be entered in what fields would also be useful. Since this works differently to other PeopleSoft queries we have used as it is more hard coded and locked down.