Form Linking and Parent Child – Detail about Parent – Child

Home Forum Behaviors Form Linking and Parent Child – Detail about Parent – Child

This topic contains 0 replies, has 1 voice, and was last updated by  ehuezo 3 years, 3 months ago.

Viewing 1 post (of 1 total)
  • Author
    Posts
  • #9895

    ehuezo
    Keymaster

    Hello PerfectForms Users,
    Today I will be expanding on a “Parent – Child” relationship. The info provided in this and the next post will allow you to make the best decision for your process. When it comes to form linking and parent child relationships there are many similarities; however the differences can make a huge difference.

    A Parent form can be any form. This form is typically the form that will be a form in your process that is used to spawn other forms involved in your process. A parent forms role is to create a child instance. These instances can be access from a parent form, can be created by a parent form, and can pass information easily to a child form.

    A parent form should be used if you have smaller process workflows that operate within a greater process. Most if not every business workflow is part of a greater goal, yet not all processes are dependent on one another for completion. For the scenarios that do require process dependencies we offer the parent form.

    A Child form is exactly as it sounds. This form requires a parent to create it, it can receive information from the parent, and they are linked behind the scenes with meta data. This link can function both ways and cannot be broken without an instance being deleted. A child form can be any form as well; however should only be used when their workflow is a “sub” workflow of a larger process.

    The benefit of a parent child relationship is that the forms have an expanded set of options without any additional configuration. You can retrieve data from a Parent form, or a child form without building out extra fields, behaviors or connection.

    The downside to this process is, If a parent is created it must be submitted before a child form can be created. This makes the relationship not possible in the first stage of your workflow. Another potential issue is, if a “To Be” parent instance creates a creates a child instance and is not submitted, that relational link will be broken, and the child form can no longer be part of a parent child relationship. This can cause an issue if you wish to shift a child over to another instance.

    Our next post we will be providing additional detail on form linking to allow you to choose which configuration is best for you. Please feel free to respond below if you have any questions. Thank you for your time, and as always.
    Happy form building!

Viewing 1 post (of 1 total)

You must be logged in to reply to this topic.