Element Properties are settings and attributes that allow the element to meet specific data collection needs and diverse input requirements. Each element has a number of properties that allow it to be configured for the needs of your form. While many have properties unique to that specific element, below are the properties that are available for almost all elements.
This text appears as a bold font label above the element. This identifies what data is to be collected. When adding elements as columns to a response report, this is the value that will be used to identify which element to add.
The text appears in a lighter font just below the Title. The description can be used to add more detail than the Title, can provide examples, or can give formatting hints.
Custom Class (CSS)
If you created a CSS class and placed it in your form’s Custom Styling box, you can apply that class to this element by typing the name here.
See the CSS Documentation for more detail on using CSS on an Ecollect form.
Selecting this option requires the user to enter a value into the element in order to submit the form. A will be placed at the end of the Title to indicate to the end user which fields on a form are required. If the end user does not fill out a required field, their form will not be submitted and the element will be highlighted red.
Admin Portal Only
This options links the element to a core, custom, or extended PowerSchool field. For forms of type ‘Collaborative – Student’ or ‘Individual Response – Student’, the fields must be within the Student table or one-to-one extensions of the Student table. For forms of type ‘Collaborative – Teacher’ or ‘Individual Response – Teacher’, the fields must be within the User table or one-to-one extensions of the User table. Elements cannot be linked to PowerSchool fields on a General Survey form.
To set the PowerSchool field property, check the option and press theicon to bring up the PowerSchool Field List dialog to choose the appropriate PowerSchool field.
When a form loads on a student/user record, data within PowerSchool fields linked to elements on the form will automatically populate the elements. When a form is submitted, the data in the PowerSchool fields will be updated with the data entered into the form elements. If you would like to have an administrator be able to approve changes being made to PowerSchool fields, please see the Approval Process Documentation
Workflow mapping allows you to create rules that decide when an element appears on the form.
In the above example, the element highlighted in blue is dependent on the element highlighted in orange and is only viable if the choice ‘Yes’ is selected for the element highlighted in orange.
Similar to Share Permissions at the form level, Element Permission allows you to set the level of access users of each portal have to an element. This can be used for forms that need to be submitted by users across portals but for which some elements are only relevant to particular portals. For instance, there can be an Office Use Only section of the form that is hidden from the parent portal. Or a form that needs to be signed off by both the parent and the student can have the parent signature line set to be read-only on the student portal and vice versa.
Global access. Access to the element matches the form level access given to the portal. This is the default setting.
No access. The element does not appear on the form on this portal.
View Access. The element is visible but is not editable.
Full Access. Users on this portal can edit the element.
Elements that are not input fields, such as Text Block or Section Break elements, only have global and no access options.
Required fields will only be enforced if the user has permission to edit the field.
Permissions on a Container Element
Any permissions set on a container element, such as a Side-By-Side Container, will be applied to the elements within the container.
Between the form permission for the portal, the permission set on a container, and an individual element’s permissions, there may be many levels of permissions that could apply to a given element. The most restrictive permission is always the one that takes affect. For instance, the form gives the parent portal edit permissions. A Side-By-Side Container that is part of an Office Use Only section of the form is not visible to the parent portal. A Single Line Text element within the Side-By-Side Container is set to view-only on the parent portal. When the form is viewed from the parent portal, the Single Line Text element is not visible because the most restrictive permission that could be applied to the element was the no access permission on the Side-By-Side Container.