CTM and Delegated Access

Constituent Transaction Management (CTM) framework allows the assignment of an EMPLID while a user is performing a transaction set for CTM. CTM uses the personal data information entered by the user as search data to trigger Search/Match and associate an EMPLID. The process is invisible to the user.

The Delegated Access framework triggers CTM for creating or assigning an EMPLID to the proxy if a delegation transaction requires an EMPLID to be associated with the proxy. This setup decision is made on the Delegation Transaction Setup page. Delegated Access triggers CTM from the Proxy Terms and Conditions page after the proxy accepts or declines the terms and conditions, enters some personal information, and clicks the Submit button. At that time the SCC_DA_SUBMIT web service operation is triggered and if at least one transaction delegated to the proxy is set up to assign an EMPLID, then CTM triggers Search/Match. The constituent data entered by the proxy is stored in the CTM constituent staging tables.

Assigning an EMPLID to a proxy is an optional setup because within your institution you may have some delegation transactions that require an EMPLID to be assigned to the proxy, whereas some don't. For example, if you configure a delegation transaction to allow a proxy to donate money on behalf of the delegator, you may want to capture as much information as possible from the proxy and create an EMPLID to send further communications. Whereas if you create a delegation transaction to delegate access to the View My Class Schedule component, you may not care about gathering personal information from the proxy or assigning an EMPLID to the proxy.

On the Delegation Transaction Setup page for a specific transaction, if you elect to assign an EMPLID to the proxy you are required to enter a CTM Transaction Code. On the Proxy Terms and Conditions page, the proxy enters personal information. If that transaction was delegated, at submit time CTM triggers and uses the CTM Transaction Code to call Search/Match and assign an EMPLID to the proxy.

Note:

CTM is always consumed as part of a transaction and handles constituent and, optionally, transaction data. When CTM is consumed by Delegated Access, only constituent data is involved. Delegated Access framework doesn't involve any transaction data. Once the proxy and delegator relationship is confirmed, any updates made on behalf of a delegator are saved directly in the production tables.

The personal information you capture from proxies at the time they accept or decline the terms and conditions should be sufficient for Search/Match to use as search data. The Search/Match Parameters to use are defined in the CTM Transaction Code that you enter on the Delegation Transaction Setup page.