Includes information from the Form creation and the ability to add a Submission Label. See more about Submission Label below.
Name, Slug, Status, and Type are set when you Create the form. They can be altered here, but be cautious if you are changing the slug as this is the unique identifier for this Datastore Form. If you change the slug here, make sure references to the old slug in other parts of the application (Bridge Mappings / Trees / Bundles) are updated as well.
The Submission Label is an important option here. When viewing a list of submissions, this calculated value can be helpful in identifying the one you are looking for. If not set here, the Submission Label is defaulted to the Submission's ID.
You add the variables with whatever string characters between to make the label. If these questions do not have answers you will have blanks. Consider making them required.
This panel also allows you to Delete Datastore Forms. When you delete a form it also deletes all submissions, so delete with caution.
Attribute Definitions are created in the Space|Attribute Definitions console, and then applied to the form here.
Only Attribute Definitions with a type of "Datastore Form" are available here for selection.
When adding an Attribute, you must select the attribute, add the desired value, and click Add Attribute. Then, once all attributes have been added or updated, you must click Save Attributes.
Security Definitions are created on the Space|Security console. This console allows you to apply those settings (Datastore Form and Datastore Submission) to a specific Datastore Form. If no policy is applied (blank), only space admin's are granted access for that option.
Datastore Form Indexes define the different patterns that can be used to search for submissions. Because it’s common to only need to search by a single field/property, the system will automatically create an index for each field on the form as well as for all of the form submission properties (createdBy, updatedBy, handle...etc). These default indexes cannot be removed. As fields are added to the form or new indexes are defined, the administrator will need to click the Build Indexes button before that index can be leveraged in a query.
Administrators can define compound (or multi-field/property) indexes on Datastore forms. Each field/property defined in an index is referred to as an index part. A query for “All people with the first name Tony living in Maine between age 50 and 60” would be possible by creating a compound index with parts First Name, State and Age.
Datastore Forms allow administrators to set uniqueness restrictions on submissions via aunique index. An example would be a datastore representing Countries. You would want to ensure that the Country Name field would be unique, so that no two submissions could have the same Country. When defining or editing an index, you can specify the “Unique” flag.
As administrators identify new search patterns, they may want to define a new index definition, or modify an existing one. To do so, clicke either the "Add Definition" button or the Pencil/Edit button.
This pop-up allows you to define the index parts (these are a combination of Form Fields or Submission Properties like createdAt, createdBy...etc). Further, you can specify if the index should be unique here as well. If a unique index is specified, no two submissions in the system can have the same parts identified in the index.
The Submissions Panel allows you to view all submissions for this form in most recently updated at order.
If no Submission Label is set (see above) on the General tab, the unique id of the request is used.
When a submission is selected, details of that specific submission are displayed, including the fields with entered responses.
Submissions can also (with caution) be deleted from here.