If you are unsure of what is meant by the title references to 'Child' and 'Parent' Records then please refer to the link below:
For the remainder of this post however, it will be assumed there is a solid basis of understanding for Parent and Child Application structures. In particular those where Child Record creation is only wanted via the Parent path. You will require at least a few basic elements:
- Parent Reference Field
- Record Archive Workflow (On Record Creation)
- Email Notification Workflow (Not mandatory but strongly recommended)
- Explanatory Template (Again not mandatory but recommended)
The Parent Reference Field will provide the trigger for the Workflows, naturally whatever value it takes when a Child record isn't created through a Parent will be the one used for the Workflow Trigger. When triggered you will want it to carry out two actions - Archive the Record and Send a Notification Email explaining to the User why the Record they just created has been Archived. As an extra you may wish to use Form and Template visibility rules to display a Template in Workspace giving additional reinforcement of why the record has been archived.
For more info on Workflows please see below:
Please sign in to leave a comment.