Note: This topic applies to the Groove 2.5 version of the Groove Forms tool.
The Groove Forms Tool provides a suite of application templates you can use as a starting point for designing your own Forms tool applications. Each template comes with preset forms, fields, and views. You can use the templates as is, or modify any of the application elements.
Some of the templates are very simple in design, and include standard fields, forms, and views, with no additional script code included to add features. These include:
The other templates are somewhat more complex in layout and features, and include script code that adds additional features. These include:
Finally, the template "Hiring Requisition - Customized" is essentially the same as "Hiring Requisition" except that it contains forms that were customized in an external HTML editor. If you want to use this template and update its design, you must also do so by exporting and editing in an HTML Editor.
This is a basic asset inventory application, in which contributors can record information about computer-related equipment and software. It includes a single "Hardware Profile" form and five views for viewing records by Asset Name, Asset#, Date, Location, and PO#.
This template is intended to let members record weekly status information. It includes a single "Weekly Status Report" form and two views for viewing records by Author or Week-ending date.
This template is intended for use as a "process" document library. It contains the following forms:
New Process
Members enter a subject for the process, select a category, and add
a content description. The form includes an attachment field for cases
in which there might be other supporting information from other files
or in which the entire process might be described in another file.
Response
Members can add a response to the selected process document, perhaps
to ask for clarifying information, or to add other ideas. The Response
form and the New Issue form both include a required "Subject"
field so that members can always see subject information for either the
new process or the response. To learn more about how the hierarchical
effect between the New Process and Response form is set up, see the explanation
below for the Issues
Tracker template.
The template includes two views: Category and Subject.
This template is intended for use as a "corporate policy" document library. It includes a single "Policy" form and three views for viewing records by Author, Category, or Policy#.
This template allows workspace members to track and analyze issues related to a project or organization. It contains the following forms:
New Issue
Members enter a summary and description of the issue, and specify other information, such as category, priority, and status.
The form includes a script that produces the following effect. When the "Done" option is selected in the Status field, two new fields display: Resolution and Date Resolved. These allow users to report on how the issue was resolved, and the resolution date.
Response
Members can add a response to the selected issue, perhaps to ask for clarifying information, or to add more explanation about an issue. The Response form and the New Issue form both include a required "Summary" field so that members can always see summary information for either the issue or the response.
To achieve the hierarchical relationship between New Issue and Response records, the setting "Use this form to create responses to the selected record" is checked in the Modify Form window for the Response form. In addition, the setting "Show "twistie" in this column when necessary" is checked in the Column Properties dialog box for the Issue field for the Issue, Priority, and Status views.
The template contains four views: Author, Issue, Priority, and Status. All views except for Author display hierarchical response topics. The Author view is a flat view that simply shows all documents (regardless of the record used to create it) by author.
The Customer Support template is intended to allow a support organization to record and track customer support requests. It contains a single "Support Request" form, and five views for viewing the recorded support requests: Author, Contact, Customer, Priority, and Status.
The Support Request form includes a script that produces the following effect: When the "Resolved" option is selected in the Status field, the Solution field appears so that users can report on how the problem was solved.
The Hiring Requisition template is intended to allow a Human Resources organization to manage the hiring process. It includes fields that describe specific job details, such as title, level, hiring manager, salary range, and department. An attachment field allows users to add files such as resumes.
The form contains a script that interacts with a set of "approval" fields as follows: The contents of Approval Status field automatically changes to reflect current approvals. For example, when only the Hiring Manager and Human Resources Manager of checked their approval, the Approval Status field looks like this:
When all required approvers have approved the requisition, the Approval Status changes to "Approved":
The data view can then allow viewers to quickly determine or sort the Approval Status of hiring requisitions. For example:
The application contains five preset views: Approval Status, Date, Requisition#, Salary Range, and Title.
Copyright ©2000-2005 Groove Networks, Inc. All Rights Reserved.