Understanding Admission Transactions

Admission transactions use the delivered Admission Applications Web Services (AAWS) and the File Parser bulk loading of admission applications features. The features are fully integrated with the Constituent Transaction Management (CTM) framework (admission transactions are consumers of the CTM framework). Each admission transaction you set up is considered a CTM transaction. CTM generates an admission transaction when:

An applicant or administrator uses an online admission application to create, save or submit an application through AAWS (online transaction).
You use the File Parser utility to load applications from an external file (offline transaction).

An admissions online or offline transaction includes both the constituent and application data.

Constituent data may include person data or data that is considered as not associated with the application. Examples of constituent data include Name, Gender, Address, and Email. Examples of application data include Academic Program, Admit Term, and Academic History.

When a transaction is generated, the system uses Search/Match to look for constituent data in your production environment (based on the Search/Match parameters) that matches the constituent data in the transaction. Each defined transaction can have its own Search/Match setup. You can therefore determine the rules for creating a new ID, updating an existing ID, suspending or ignoring a record. The system stores the constituent and application data in staging tables. If there are errors or if Search/Match determines that the incoming constituent record should be suspended or ignored, use the Constituent Staging and Application Transactions components to correct the admissions transaction data. You can post transactions individually or by batch to the Campus Solutions database.

This diagram shows the admission transactions flow: