Understanding 'At Future'

How does the trigger work? 

When an application record is created, a formula field evaluates the available data points on the record and determines an application type assignment. This value is then compared against your Application Requirement Rules and, if a match is found, the corresponding Application Requirements are created as individual Checklist Item records. 

Should I run this trigger @future? 

For most institutions, there is no need to run the Application Requirements Manager trigger using future calls. However, there are two reasons why you may choose to enable the @future setting for this trigger:

1. You have a high volume of application automation - TargetX supports adding custom automation to support your business processes. This includes, but is not limited to custom flows and custom triggers. If you have added automations beyond those included standard with the TargetX product suite, you may run into governor and execution limits when processing data in the CRM. Switching the trigger to run @future may improve performance.
2. You bulk import a high volume of application records - Some institutions import application data from third-party sources such as Common App. During bulk imports, records are created in batches, and all triggers execute for the entire batch in a single thread. As a result, you may find that the high volume of records being imported causes the system to exceed governor and execution limits. Running the ARM trigger @future may improve processing.  

How do I enable @future processing? 

The Application Requirements Manager checklist item creation trigger can be changed to run @future by way of the RM Preferences Custom Setting. 

1. Navigate to RM Preferences.
2. In the Application Requirements Manager Configuration section, complete the following:
   1. Select the Process Checklist @future box.
   2. Enter a value in the Checklist @future Minimum Batch Size field to specify at which batch (or bulk import) level to use @future. To run the trigger @future for all records, enter 1. Otherwise, TargetX recommends entering a minimum value of 10, decreasing the value as needed should you continue to exceed CRM governor limits.
3. Save your changes

How does the trigger work? 

When data is saved on one of the supported detail or child records (as noted above), the Source to Master trigger is executed. For objects where a roll-up has been configured, the trigger evaluates which data to roll up from which detail record and copies the data to the corresponding field on the contact record.

Should I run this trigger @future? 

When using Source to Master, it is important to consider the fact that record saves are occurring on multiple objects during the same thread, or transaction in the CRM. For example, saving data to the Enrollment History will trigger the roll-up of that data to the Contact record, which will also cause a "save" transaction on the Contact record. When an institution is using Source to Master on multiple objects simultaneously, the risk of hitting governor and/or execution limits is increased. As a result, running the trigger @future may improve performance for institutions with a high level of automation. 

How do I enable @future processing? 

The Source to Master trigger can be changed to run @future using the Base Custom Settings.

1. Navigate to Setup and search for Custom Settings.
2. Click Manage next to TargetX CRM Base Settings.
3. Click Edit next to the Default setting.
4. Check the Field for Update Related Contacts Async.
5. Save your changes.

Access Keys 

The TargetX Access Keys feature provides additional security when external users (e.g., applicants) are viewing data from the CRM on external pages such as the non-Communities based App Tracker. Each Contact is assigned a unique key value which is included in the URL when accessing pages, thereby preventing other users from modifying URL data to access another user's information. 

How does the trigger work? 

When contact records are created through data import or manual entry, a unique key value is generated by the Access Keys trigger and stored on the contact record. 

Should I run this trigger @future? 

For most institutions, there is no need to run the Access Keys trigger using future calls. However, for institutions with a high number of custom automation (e.g. flows, process builder processes, roll-ups, and/or custom triggers), there may be value in running Access Keys @future to reduce the likelihood of hitting governor and execution limits. 

How do I enable @future processing? 

The Access Keys trigger can be changed to run @future through the Base Custom Settings.

1. Navigate to Setup and search for Custom Settings.
2. Click Manage next to TargetX CRM Base Settings.
3. Click Edit next to the Default setting.
4. Check the box for Process Access Keys @future.
5. Save your changes.

How do I enable @future processing? 

The Group Assignment triggers can be changed to run @future by way of the Group Assignment Custom Settings.

1. Navigate to Setup and search for Custom Settings.
2. Click Manage next to Group Assignment Settings.
3. Click Edit next to the Object trigger where you wish to set @future (for example, Contact, Account, etc.).
4. Check the box for Run Group Assignment Async.
5. Save your changes.