We mount a scenario with a molecules structure to facilitate.
3) Users can create views of these forms (like in Zoho Creator). For each view, user define :
This last option makes it easy to create forms for visitors or polls in a group :
4) When writing "articles", users can choose to insert one of the
"views" of their created forms
taken from #21
The user will be free to write articles in your ePortfolio.
The "article" term is intended to be used to referr many item types, like:
- images on the album
- "pre-molded" forms
- custom forms
- pages on the eP
This article is intended to be linked to the ActionItem76
. Where we describe the final objective of the creation of articles and creation of new types of articles.
Use case: Implement article type "Form"
A module that allow users the capacities of to create, edit, delete bulletins/articles. With the feature like revisions control, input images and video URL's, and write bulletins collaborating with other authors.
"Article" is the name of what users can write, modify and manage; but there are several kinds of articles, for instance:
- image galleries
- book/film/place/exhibition/website/webpage review
The common points of all articles are:
Fields are of these types:
- text (1 line)
- multiline text
- radio button
- select (single)
- date (with calendar selector)
There could be other (not pure HTML) widgets, like:
- cursor (to select a value in a range)
- color picker
- auto-completed text fields
- tags selection fields (with suggestions)
Creating "article types" (form management)
Users can create new article types to:
- allow the writing of a new kind of content
- insert a form in an article (comment for an article, subscription form, contact form, survey…)
An example of form management is Zoho Creator
The user can choose one of the basic types of fields and then add a field of this type in the current form.
It is possible to order the fields easily.
One can insert explanatory fields.
Each field has several compulsory data:
- a name
- a type (see Field types above)
Other possible data:
- a short label
- a long label
- a field length (when appropriate)
Displaying the form
Once the form is created the user can manage the form's statuses.
In each state, the user chooses for each field:
- a visibility status (visible/invisible)
- a verification system (range for dates and numbers, regular expression pattern for text fields…)
For a state:
All the items below must be "Yes" or "N/A" in order to consider this
requirement as done.