This service permits an institution/organization to make a PESC Transcript Request for a particular student. The service will provide a PESC Transcript Response for every request.

This service implements support for v1.4.0 of the PESC Transcript Request and Response messages. Refer to this page (http://www.pesc.org/pesc-approved-standards.html) on the PESC website for full details on the PESC standard for this request.

An Alberta Education Transcript Request and Response PESC XML Specification document has been created that provides a detailed specification on the transcript request and response PESC messages that PASI will support. This document lays out the full details on what is expected in the request and how this service will build the response.

The APAS (ApplyAlberta) page provides the current implementation of how PASI handles incoming transcript requests from PSI through the APAS Proxy. It is being referenced here as a FYI.

See Electronic Transcript Integration (PESC Services) for an overview of how this service should be used. The following diagram shows a high level overview of how the service works:

request_transcript_overview_diagram.vsdx

The service can be accessed by systems with the PESC Transcript User role.

Note: This service only appears on the IPESCService201604 endpoint.

The following information must be provided when using this service:

• Request Transcript

This will be a single Transcript Request PESC xml message based on the v1.4.0 specification. Refer to this page (http://www.pesc.org/interior.php?page_id=174) on the PESC website for full details on the PESC standard for this request.

The following rules are used to validate the information provided in the request:

• Rule 70000 - Failed PESC Schema Validation
• Rule 70001 - Duplicate RequestTrackingID
• Rule 70010 - Unsupported ElectronicFormat
• Rule 70012 - Unsupported AgencyIdentifier
• Rule 70020 - Incomplete Institution Information
• Rule 70021 - Missing RequestTrackingID

Note: Failures from these validations will be returned as rejections in the PASI Core service response.

Note: Any validation errors returned from the Construct Document Order (System Service) service could be returned as well.

These validations will only occur if the PASI Core Service level validations have all passed.

The following rules are used to validate the information provided in the request:

• Rule 60002 - Secondary ASN
• Rule 70022 - Invalid ASN
• Rule 70023 - Deactivated ASN
• Rule 70002 - ASN and Birthdate do not match
• Rule 70003 - Duplicate of an Existing Request
• Rule 70004 - Unsupported HoldType
• Rule 70005 - Empty Transcript
• Rule 70007 - Unsupported SessionDesignator
• Rule 70008 - Transcript Request Cancelled
• Rule 70009 - Transcript Not Available for the ASN in Environment
• Rule 70010 - Unsupported ElectronicFormat
• Rule 70011 - Unsupported ElectronicMethod
• Rule 70012 - Unsupported AgencyIdentifier

Note: Failures from these validations will be returned in the payload of a Transcript Response xml message that is cancelling the request.

At a high level the service does the following:

If the HoldType has been supplied and is not “Now” then the SessionDesignator will be in the form (YYYY-MM) and will be used to determine the Control Schedule that the new Document Order will be created against.

Only control schedules that have a TranscriptReleaseDate (Schedule Category) will be considered. Those control schedules are linked to specific exam periods. The session designator will be converted into a specific school year and exam period to determine a matching control schedule.

The following logic will be used to determine the date to use when looking for a matching control schedule:

• If the HoldType is “Now” or has not been provided then the transcript document order item will be considered as having a HoldType of “Now”. Essentially it will be processed as “ASAP”.
• If the HoldType is “AfterSpecifiedTerm” then the <SessionDesignator> will be converted into a specific school year and exam period to determine a matching control schedule.
  If the month of the session designator is 09, 10, 11, or 12 then the school year will be +1 of the year in the session designator. If the month of the session designator is 01, 02, 03, 04, 05 06, 07 or 08 then the school year will be the year in the session designator.
  As an example a SessionDesignator of “2013-11” would map to a control schedule with a school year of 2014 and an exam period of November, “2014-06” would map to a control schedule with a school year of 2014 and an exam period of June.
• If the HoldType is “AfterGradesPosted” then the <SessionDesignator> from the PESC message will be converted into a date as the 1st day of the month and year of the <SessionDesignator>. For example, a <SessionDesignator> of “2013-11” would convert to a date of “2013-11-01”.
  Once a date has been determined, the control schedule with a category of TranscriptReleaseDate (Schedule Category) and the closest Actual Date that is not prior to the date being matched will be the matching control schedule.

If there is no match found, essentially the date is so far in the future that there are no control schedules that match, then Rule 70007 - Unsupported SessionDesignator fails.

Note: If the SessionDesignator is in the past, then the transcript document order item will be considered as having no SessionDesignator and a HoldType of “Now”. Essentially it will be processed as “ASAP”.

This section provides detail on where the various attributes that the service consumes from the transcript request pesc xml that is passed in to the service.

Note: only the “Requesting PSI” OR “Requesting Organization” will appear in a given request.

This section provides detail on the inputs for the Construct Document Order service.

The usage of this service is audited using Service Auditing including the auditing of Caller Information.

The following information is returned after a request has been processed:

• PESC Transcript Response XML

This will be a single Transcript Response PESC xml message based on the v1.4.0 specification. Refer to this page (http://www.pesc.org/interior.php?page_id=174) on the PESC website for full details on the PESC standard for this xml message.

This section provides detail on where the various attributes and sources for the generated transcript response.

<LocalOrganizationID>
  <LocalOrganizationIDCode>AB00000000</LocalOrganizationIDCode>
  <LocalOrganizationIDQualifier>AB</LocalOrganizationIDQualifier>
</LocalOrganizationID>

<LocalOrganizationID>
  <LocalOrganizationIDCode>*1*</LocalOrganizationIDCode>
  <LocalOrganizationIDQualifier>AB</LocalOrganizationIDQualifier>
</LocalOrganizationID>