Entity Registry and Admission Transactions

You can add new entities or extend existing entities. For example, an academic institution has a requirement to add one or more new entities into the application process. The new entity could represent entirely new data or it could represent an extension to one of the existing delivered entity data types. This may involve either or both application and constituent data. You can use the Entity Registry feature for all these situations.

The web service operations that are part of the AAWS feature are constructed based on entities.

The entities for all core data records within the constituent and application areas needed for admission transactions are delivered with the system within the Entity Registry component. You can extend any of these entities or create new ones. Register new institution-specific extension entities as children to any entity in the registry. If you need to create new entities, because AAWS and File Parser admission transactions are CTM transactions and therefore use stage and production records, the entity you create must be set with an entity type that allows for stage records and production records. For instance, use entity type called Staged Entity. The stage and production records need to exist prior to creating the new entity.

All Recruiting and Admissions entities are represented by the IEntity interface SAD_ADM_APPL:Accessors:IEntity. The IEntity interface defines the core behavior that any participating entity needs to support in order to be managed by Recruiting and Admissions. For each new distinct entity that you want to create for Recruiting and Admissions, an application class implementing the IEntity interface needs to be created and registered. For instructions on creating and extending entities:

See Creating a New Entity

Example of a scenario of when you can use the Entity Registry feature for Recruiting and Admissions: Suppose an online application has a list of questions. The Campus Solutions data structure does not support capturing the answers to these questions. In such a case, you can create a Questions and Answers entity.

The Questions and Answers application extension entity is registered as a child entity to the Application entity on the Entity Registry page: