I am close to a solution:
I was going to create a 2nd Submit button paired with an automation.
There is an ability to add attachments (child) which triggers the record to be saved.
Some requests do not require an attachment but it is an option.
I will have a summary field for how many attachments there are.
If = 0, then I will have the 2nd submit button show, this will pretend to create a child record which will cause the parent to save, and then it will redirect them to where I want, making them feel like they directly submitted it.
On the back-end, I will have an automation that says when a record is saved, attachments summary = 0, and the request type = x or y or z, check 'Submit Checkbox'. This will trigger my other functions to operate as should.
The issue I discovered with this is that if they do want to add an attachment, it will trigger the 'Submit' function early since the attachments will be at 0 until they save the attachment.
------------------------------
Curtis Middleton
------------------------------