How to Update XML T-Pass File

Anthony Westover Updated by Anthony Westover

The rules for student T-Pass transportation eligibility are managed in an XML file that is routinely updated and uploaded to the database. This is how new rules are considered in the transportation eligibility logic. The process is fairly straightforward if you have the complete file available and ready.

Prerequisites

  1. Credentials/access to STAGDATA-03 and BPSDATA-03.
  2. Permissions to INSERT and UPDATE on BPSInterface, specifically BPSInterface.Transportation.xmlTPassRules.
  3. The full XML file that needs to be uploaded.

Steps to Insert the XML File

  1. Connect to STAGDATA-03.
  2. Query the Database for the Current XML T-Pass file rule file ID by executing the following SELECT statement: SELECT RuleID FROM BPSInterface.Transportation.xmlTPassRules WHERE isCurrent = 1;
  3. Paste this SQL statement template into a query window for later execution: INSERT INTO BPSInterface.Transportation.xmlTPassRules
    (isCurrent, xmlRule)
    VALUES
    (1, '[PASTE XML FILE CONTENT HERE]');

    UPDATE BPSInterface.Transportation.xmlTPassRules
    SET isCurrent = 0
    WHERE RuleID = [PASTE LAST CURRENT RULE ID HERE];
  4. Replace [PASTE LAST CURRENT RULE ID HERE] with the number returned from the query in step 2 into the template.
  5. Open the XML file in your appropriate editor of choice and copy the entire contents of the XML file to the clipboard.
  6. Replace [PASTE XML FILE CONTENT HERE] by pasting the contents of the XML file into the template. This will be multiline which is fine, just make sure everything is within the two quote marks.
  7. Execute both SQL statements. Each should affect just one row.
  8. Test this in Staging using an appropriate student, usually best to select a student in high school, using a workflow which calculates transportation logic. For example, any logic which calculates school choice also calculates transportation eligibility.
  9. Verify the results.
  10. Upon successful verification, repeat these same steps in BPSDATA-03.
  11. Perform the same testing verification in Production.
  12. Upon successful verification, notify all requestors and stakeholders of successful rule deployment.

How did we do?

Editing Ticket Fields in Kace via email

Report Address Issue to Google

Contact