Return to Navigation

Understanding AAWS

Admission Applications Web Services (AAWS) can be used by end user devices (such as a browser or a PDA), enterprise applications or any other third party software that can interface through standards based means.

AAWS can be used by:

Different academic institutions have different needs for capturing admission application data. Also, application data can vary within the same academic institution between various campuses, departments, careers, and types of applicants. For example, application data for international and domestic applicants can vary within the same institution. This creates the need for institutions to develop their own online application user interface that can interact with the Campus Solutions system. With AAWS, institutions can connect their online application with the Campus Solutions system.

AAWS provides the SAD_ADMISSIONS service that enables access to the Campus Solutions Recruiting and Admissions functionality. The SAD_ADMISSIONS service provides the following service operations:

Service Operation

Description

SAD_CREATEAPP

Create admission application

SAD_SAVEAPPL

Save admission application

SAD_SUBMITAPPL

Submit admission application

SAD_GETAPPLS

Get admission applications

SAD_GETAPPL

Get admission application

SAD_GETATTACH

Get admission attachments.

With these service operations, AAWS offers functionality in the following areas:

Note that when an online application invokes SAD_SAVEAPPL or SAD_SUBMITAPPL service operation, the system generates an admission transaction. This admission transaction contains the admission application data that the user has saved or submitted. An admission transaction is defined and configured using the CTM pages and Application Configuration component. You can use the delivered Application Transactions and CTM Constituent Staging components to review, edit, and post the application and applicant data in an admission transaction. Additionally, you can choose to post the transactions in batch.

Constituent Transaction Management (CTM), which is a Campus Community feature, provides the following two service operations related to New User Registration (NUR):

Service Operation

Description

SCC_USERREG_CREATEACCT

Create user account

SCC_USERREG_AUTHENTICATE

Authenticate user

You can use these NUR service operations to:

The List of Values framework is also a Campus Community feature. The framework provides the SCC_GET_LOV service operation. An online application can use this service operation to retrieve the list of values from the Campus Solutions system for data entry fields on the online application. This is useful only if the online application user interface is built outside of your Campus Solutions system.

Service Operation

Description

SCC_GET_LOV

Get List of values

AAWS uses the following Student Financials payment integration service operations to enable application fees calculation and payment:

Service Operation

Description

SSF_INITIATE_EPAYMENT

Initiate an ePayment.

SSF_COMPLETE_EPAYMENT

Complete an ePayment.

All of these service operations use PeopleTools Integration Broker for interacting with the online application. Any online application user interface that is web-service enabled and SOAP compliant can access these service operations. AAWS adheres to open web service standards currently supported in the latest release of PeopleTools.

Before developing your online application user interface, we recommend that you use a SOAP service tester to become familiar with how the web services processes the admission application data and user information. One way to use a service tester could be by first passing the input parameters to a service operation and then viewing the service operation output.

Developers working on the implementation of AAWS should have strong skills in:

  • A tool or technology to build and deploy an online application user interface.

  • PeopleSoft Integration Broker.

  • PeopleCode.

  • Web services concepts mainly XML, SOAP, and WSDL.

  • Campus Community Entity Registry functionality.

  • Recruiting and Admissions functionality.

  • Campus Community Constituent Transaction Management functionality.

The key setup areas that apply to AAWS are:

  • PeopleTools Integration Broker.

  • Campus Community Constituent Transaction Management (CTM).

  • Campus Community Entity Registry.

  • Application Configuration (Configuring admission transactions).

  • Campus Community List of Values.

  • Attachments URL.

  • Hosted Payment.

The following documentation should be reviewed as part of your AAWS implementation