Outbound FERPA Service

The outbound FERPA service publishes to or notifies external systems of changes to Campus Solutions FERPA data for constituents.

This example illustrates the fields and controls on the General page: outbound service (FERPA).

General page: outbound service (FERPA)

Description

   

Service

SCC_FERPA_SYNC

Operation

SCC_FERPA_SYNC

Direction/Type

Outbound/Asynchronous

Summary

Updates a constituents FERPA data restrictions in an external system based on the restrictions set in the PeopleSoft Campus Solutions system.

Request Message

SCC _FERPA_DATA_MSG.V1

Queue Name

PERSON_DATA

Description

This service is configured to be published to an external system when a constituent's FERPA data restrictions are created or updated. This process is designed to keep a system like a hub, in sync with the Campus Solutions system. This is an asynchronous call, so there is no return.

Pre-Conditions

Valid constituent FERPA restriction data. Triggers are set up on FERPA administrative pages and self service pages.

Processing

This service operation performs the following processing steps:

  1. A change or creation of constituent FERPA restriction data triggers an event.

  2. The event sends out a message to an external system with the related constituent FERPA restriction data.

Post-Conditions

N/A Asynchronous

Create the Subscription by adding a new Routing to the SCC_FERPA_SYNC Service operation to consume the published messages in to third party integration system.

  1. Navigate to People Tools, and then Integration Broker, and then Integration Setup, and then Service Operations.

  2. Search for the SCC_FERPA_SYNC Service Operation and navigate to Routings Tab.

    1. Provide the Routing Name and click Add button.

    2. Enter Description.

    3. Sender Node: Local Node name of Campus Solutions.

    4. Receiver Node: any External Node name.

    5. Navigate to Connector Properties tab.

     

Gateway ID

Select Integration Gateway

  

Connector ID

HTTPTARGET

  

Connector Properties:

   

HTTPPROPERTY

Method

POST

HTTPPROPERTY

SOAPUpContent

Y

HEADER

Content-Type

text/xml

HEADER

SOAPAction

<soapactionstring>

PRIMARYURL

URL

<endpoint url of the service provided in third party system> ex: http://hostname:port/ServiceName

This example illustrates the fields and controls on the Routings page (FERPA).

Routings page (FERPA -Family Educational Rights and Privacy Act)

This example illustrates the fields and controls on the Connector Properties page (FERPA).

Connector Properties (FERPA) page