View source for Trigger Document Submissions for Non-Contact Related Objects

== Intro ==
3B for Salesforce automatically creates a Document Submission record for each qualified Document Trace/Form Response/ Candidate Scorecard / Submitter record. Sometimes, however, admins need Forms and Documents with a different context than the Contact, and in those cases, a document submission might not be created. Follow this guide to fix this behaviour.

== Steps ==
3B for Salesforce delivers automations (Apex Triggers) on the Document Trace/Form Response/ Candidate Scorecard / Submitter objects, and it relies on the "Contact" field in order to identify the person who would need a Document Submission. If that field is empty, no document submission will be created.

If for example you need to submit a form/document against an ATS Application/Placement, simply create a Before trigger flow on create/update which executes if the Contact field is empty/null and the Application/Placement field is populated. In that case, traverse to the App/Placement, grab the Contact and update the Trace/Response/Scorecard/ Submitter Contact field. This will automatically trigger the engine to create a document submission.

Please note, that you may not have a Placement/Application/Other lookup on these "trace" objects, so you might need to create it.

[[Category:3B Onboarding]]
[[Category:3B Docs]]
[[Category:3B Forms]]