--- title: "Swift Mode Technical Information" slug: "swift-mode-technical-information" tags: ["Mobile Check-in App"] updated: 2025-10-16T21:29:52Z published: 2025-10-16T21:29:52Z canonical: "docs.blackthorn.io/swift-mode-technical-information" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.blackthorn.io/llms.txt > Use this file to discover all available pages before exploring further. # Swift Mode Technical Information ## “Mobile Check In Submission” Object and Fields The Swift Mode feature includes the Salesforce object called “Mobile Check In Submission,” which stores JSON received from the Mobile Check-in app. ### Object: Mobile Check In Submission - Object Label: Mobile Check In Submission - API Name: conference360__Mobile_Check_In_Submission__c - Description: Captures and tracks Attendee check-in submissions from the Mobile Check-in app, including payload data, sync status, and error handling information. The Mobile Check In Submission record also includes a **Reprocess Submission** button that allows users to reprocess failed Mobile Check-In submissions that failed to sync between the Mobile Check-in app and Salesforce org. #### Permissions To access this object/record, users must have the same permissions as those required to access the Event Registration Submission (ERS) object/fields. - Read, Create, Edit, Delete - Blackthorn | Events (Admin) - Blackthorn | Events (Organizer) - Blackthorn | Events (Community/Platform User) - Read Only - Blackthorn | Events (Limited Access) - Blackthorn | Events (Lite User) - Blackthorn | Events (Read Only) - No Access - Blackthorn | Events (Community Guest User) #### Fields - Field Label: **Attendees JSON** - API Name: conference360__Attendees_JSON__c - Data Type: Long Text Area (131072) - Description: Stores the attendee payload sent by the Mobile Check-in app - Help Text: Full JSON payload containing attendee information sent from the Mobile Check-in app. Used for processing and verification. - Field Label: **Status** - API Name: conference360__Status__c - Data Type: Picklist - To Process - Completed - Partially Failed - Failed - Description: Represent the submission status at the given moment - Help Text: Indicates the current processing state of the submission: To Process, Completed, Partially Failed, or Failed. - Field Label: **Request Id** - API Name: conference360__Attendees_JSON__c - Data Type: Long Text Area (131072) - Description: Stores the attendee payload sent by the Mobile Check-in app - Help Text: Unique ID generated by the Mobile Check-in app to associate the check-in request with a batch submission. - Field Label: **Chunk Key** - API Name: conference360__Chunk_Key__c - Data Type: Text (255) (Unique Case Sensitive) - Description: Stores a unique identifier representing a small chunk of a sync request - Help Text: Unique identifier for a specific chunk of data during a batch sync. Reserved for system and internal use. - Field Label: **Errors** - API Name: conference360__Errors__c - Data Type: Long Text Area (131072) - Description: Stores detailed error messages if the sync or processing fails. - Help Text: Captures error details when a sync or attendee data processing attempt fails. Used for troubleshooting and support purposes. ### Scheduled and Batch Jobs #### ProcessCheckInSubmissionsBatch Batch Job The ProcessCheckInSubmissionsBatch batch job retrieves any Mobile Check In Submission records related to a **Request Id** that has not yet been processed and processes the information sent during the Mobile Check-in app sync. Before completing the process, the job will update the Mobile Check In Submission’s **Status** field as follows: - If all Mobile Check In Submission records in the group are processed correctly, the **Status** field will be set to “Completed,” and the related Attendee records will be created or updated as expected. - If some of the Mobile Check In Submission records in the group are processed correctly but others fail, the **Status** field will be set to “Partially Failed,” and the Errors field will include an error message. Only the successful Attendee records will be created or updated. - If all Mobile Check In Submission records in the group fail to process correctly, the **Status** field will be set to “Failed,” and the Errors field will include an error message. NOTE: To avoid hitting Salesforce Governor Limits, a “soft” limit of 100 Attendee records per single Mobile Check In Submission record is in place. #### “Blackthorn | Mobile Check-In Submissions Clean Up” Scheduled Job - Scheduled Job: Blackthorn | Mobile Check-In Submissions Clean Up - Apex Job: CheckInSubmissionCleanUpBatch - Frequency: The batch job runs on the first day of each month. - Click the **Schedule Recommended Event Jobs** button under Scheduled Jobs on the Blackthorn | Events Admin tab to schedule the Blackthorn | Mobile Check-In Submissions Clean Up job. After the Swift Mode sync occurs, the “Blackthorn | Mobile Check-In Submissions Clean Up” scheduled job will run to remove irrelevant records created during check-in. The job queries the Mobile Check In Submission records, looking for records that meet the following criteria, and deletes them. - The Mobile Check In Submission record’s **Status** is set to “Completed,” “Partially Failed,” or “Failed.” - The record’s creation date is more than 365 days ago. NOTE: Records with the **Status** set to “To Process,” and the creation date within the last 365 days will not be deleted. ## Related - [Swift Mode Overview](/swift-mode-checkin-overview.md) - [Using Swift Mode](/using-swift-mode.md) - [References and Troubleshooting](/swift-mode-references-troubleshooting.md)