Note: This feature is available for users who are using v9.0.1218 and onwards.
Just like views, Form structures can also be inherited across an Enterprise Solution, making it easy for a form to be created in one place but applied to many stories across the solution.
When using inherited forms, it is simply the form structure that is inherited across the enterprise structure. If an inherited form is used, it will not create an item in the story the form is local to, but will create an item in the story the user accessed the form in.
In this article, there will be references to the below Enterprise Solution, so it is easier to understand the requirements and features of inherited forms.
If a form is created in either templates (View Template or Meta Data Template), this form will inherit down to the stories below them in the Enterprise Structure.
If the form was created in the Meta Data template, all stories will have access to the inherited form structure to be used in the individual stories.
The requirement for an inherited form structure to be created is the story must contain at least 1 category, either inherited or local.
When using a pop-out form in a story or on mobile, it informs you of the story that the form will be creating or editing items in.
Focusing on Risk 1 story, the “Manage Forms” dialog will appear as so:
As above, users with admin/owner access that enter the Manage Forms dialog will be able to see what Forms are inherited to the story, but also be able to duplicate a form by clicking on Save as new.
The forms that are inherited are a read-only version, showing the users what constitutes the form, but not being able to make any amendments. Any amendments will have to be made in the story that the form is local to.
The padlock symbol on the left of the form informs that the form is located in a template story within the Enterprise Solution. To go to the story that the form resides in, simply click the padlock and it will open the form's local story.