TREx ESC Coordinator Training April 2013

Agenda Version 4.0 Enhancements Questions? Tx-Student-Unique-ID TC07 - Disciplinary Action Reason Code changes. Remove the limitation on how many Advanced Measures can be included on the Transcript. Ability to Forward Requests Questions?

Required for 2013-2014 School Year 4.0 Data Standards have been TREx 4.0 Planned Release July 2013 Required for 2013-2014 School Year 4.0 Data Standards have been published to the TREx website at; http://www.tea.state.tx.us/index4.aspx?id=3190 Fully backwardly compatible with v 3.9. We are expecting to release 4.0 on July 14,2013 before the beginning of the new school year.

TREx v 4.0 – Tx-Student-Unique-ID Required if available. Cannot make it a true required element in the XML because the local SIS databases are only being populated with Unique-IDs for students active in the current school year.

TREx v 4.0 - Disciplinary Action Reason Codes Disciplinary Action Reason Codes 51-54 have been virtually removed to synch with the removal of these coded from PEIMS last year. By virtually removed, I mean their definitions have been struck through in the Data Standards documentation (page 3.28). They are still valid in the XML upload for student records prior to 2012-2013.

TREx v4.0 – Remove Limitation on Advanced Measures Currently the Transcript only support 4 advanced measures to be reported. That limitation is being removed.

TREx v4.0 – Ability to Forward Requests Currently if a request is sent to the wrong campus, the only option is to reject the request with a comment that the wrong Campus was selected. Now if the receiver knows where it should be sent, they can simply forward the request on to the correct campus. This will be helpful for those campuses that have consolidated or a new campus opens and all students transferred, but a request comes in addressed to the old campus.

TREx v4. 0 – Ability to Forward Requests 1 TREx v4.0 – Ability to Forward Requests 1. Inbound request arrives as an item requiring attention (no change)

TREx v4. 0 – Ability to Forward Requests 2 TREx v4.0 – Ability to Forward Requests 2. Clicking on 'inbound requests' shows 'manage requests' page with new ‘Forward' button. The forwarding capability will introduce a new workflow, launched from the “Inbound Requests” link on the TREx home page. As shown a new button will be present, enabled when a single request is selected on the list.

TREx v4. 0 – Ability to Forward Requests 3 TREx v4.0 – Ability to Forward Requests 3. Clicking ‘Forward' allows the user to specify the target school for forwarding of the request. When the 'Forward” button is clicked, the new work-flow will allow the user to select the new recipient of the request (via any of the 3 tabs) during the “Select Institution” step, as Shown. Selection of an institution will allow the user to proceed by clicking the “Next” button.

TREx v4. 0 – Ability to Forward Requests 4 TREx v4.0 – Ability to Forward Requests 4. Confirm/review page allows user to provide a message indicating why the request is being forwarded. The user is shown a summary of the action to be performed, and provided with an opportunity to enter a message indicating why the request is being forwarded. The user clicks the “Send” button to complete the “Forward” action. Note: tracking number will be same as original, and tracking history will be updated to indicate “forwarded by” the current user/institution.

TREx v4.0 – Ability to Forward Requests 5. Summary of completed Action. At this point, the current institution no longer has access to the request, as it is owned by the new recipient. It will no longer appear in the inbound requests queue, and they will not be able to view the tracking history.

TREx v4. 0 – Ability to Forward Requests 6 TREx v4.0 – Ability to Forward Requests 6. Detail view of Forwarded Request’s Tracking History at new recipient location. At this point, the request will appear in the recipient's “Inbound Requests” work queue, along with any other requests. The recipient may view the tracking history, which will contain an entry indicating that the request was received via forwarding.

TREx v 4.0 – Questions ?