The current Online Application system at UCT is outdated, difficult to maintain and to troubleshoot. It has too many interconnected dependencies i.e., one change triggers unexpected consequences. The system does not accommodate mobile devices.
UCT is developing a fluid version that uses activity guide to take applicants through all the stet of configurable steps allowing users to complete the tasks of capture and submitting an application. The presentation will show how UCT is using Activity Guides and Constituent Transaction Management (CTM) to build the new Fluid Online Application.

The CTM framework is used for performing Campus Solutions transactions that require staging of the data prior to posting to production tables. CTM validates the constituent data entered as well as the data entered for the transaction itself. The system stores the constituent and the transaction-specific data in staging tables. If there are validation errors or if Search/Match determines that the incoming constituent record should be suspended or ignored, use the Constituent Staging and the transaction staging components to correct the data. When the staged data passes all validations, CTM posts both the constituent and the transaction-specific staged data to the predefined production tables. The posting is done based on rules that you define through the Data Update Rule functionality. You can post transactions individually or by batch to the Campus Solutions database.