Configuring Online Application Settings

PDF Snapshot settings

The PDF Snapshot Settings enable a trigger on the Application object:

• To generate a PDF that excludes attachments: choose "Generate PDF Snapshot without attachments on Application Stage Submitted". The PDF of the snapshot without attachments will be generated when:

• The application.json snapshot file exists on the Application record.
• The Application Stage equals "Submitted" and
• A PDF of the snapshot has not already attached to the record.

• To generate a PDF that includes attachments when the Application Status changes: choose "Generate PDF Snapshot with attachments on Application Status change​" and select the status that will trigger the PDF creation on "Application Status to trigger PDF Snapshot with attachments​"

• Select the PDF Processing Region:
  This option determines which server is used when processing PDFs. Select the appropriate region for your institution.

• US-Production - for U.S. clients
• EU-Production - for EU client

• Maximum Snapshot Requests defines the maximum number of times to request the generation of an Application Snapshot PDF. If this is left blank, or set to 0, there will be no limit to the number of requests. Default Value = 5. *DO NOT UPDATE this value unless instructed by TargetX Support.*

• Minimum Snapshot Request Interval (Hours) defines the time to wait (in hours) before sending another request for an Application Snapshot PDF. If left blank, or set to 0, a request will be sent every time the job runs if no Snapshot PDF exists. Default Value = 2. *DO NOT UPDATE this value unless instructed by TargetX Support.*

Online Application Settings

• For Community Attachment Mode choose one of the following:

• API requires the API Enabled System Permission for the Community User profile and has a file size limit of 25MB.
• Remoting does not require the API Enabled System Permission for the Community User Profile and has a file size limit of 3MB.

Update Applications with Snapshot Data

This option will restore misplaced data that may have occurred due to defect CL-2258. 

1. After you’ve logged into your Org, add /apex/TargetX_App__Settings to the URL: https://mysalesforceorg.com/apex/TargetX_App__Settings
2. Specify the following:

• Define a Submission Range Start and Submission Range End for the applications to be evaluated. The system will use these dates to capture applications with a Submit Date within the specified range.
• Set an Application Limit for the number of applications to be updated or leave it blank to update all applications within the date range.
• If a limit is selected, Set the Application Offset for Applications to be updated. This will typically be 0. If you are using an Application Limit, the offset ensures the correct next set of applications are updated. The maximum offset is 2000.
  • For example, if you specify an Application Limit of 500 and then run the process, the next time you run the process you will want to specify an offset of 500, so the same 500 applications are not updated.
• The Run Audit button will run the script without updates and will display a prompt that it may take several hours to complete and that you will receive an email when finished.
• The Run Updates button prompts you that it may take several hours to complete and that you will receive an email when finished. You can then decide whether to proceed.

3. You can check the job status under Apex jobs as SnapshotDataRecoveryBatch. 

What does the script do?

The script will identify applications that may need updates and the specific impacted objects/fields. An impacted field is a conditionally visible question on a non-application/contact object on a card with a max count of two or more.

For the impacted fields, the script will update the Salesforce fields with the data from the application snapshot file. It will not evaluate whether a field is blank or what the data in the field is currently.

At the completion of the script an email will be sent to the email address for the running user. This email includes the Application ID, Child Object ID, Child Object Name, Update Success/Failure, and Failure Error Message.