Episode V: Figuring out the Form
Through the last four episodes, we have walked through the design and creation of a Teaming workflow. This week we kick off a new topic. Teaming Forms can be as easy as a name and attachment for an article review or as complex as a Help Desk Ticket for problem solving. For our Job Application we've decided to create a relatively simple form. However, before that happens you need to get acquainted with the Form Designer.
Log in to your Teaming workspace, click the Manage tab, then select Form and View Designers. Find the tab titled New and select Entry Definitions. Specify a name for the form; in this example it's called Application and has a data name, of jdemo_application. Don't worry right now about the Family or the Allowed Comment Type; jsut select Ok.
Click to View
This is the Form Designer.
There are three subcategories: Entry Form Definition, Entry View Definition, and Summary View. We'll talk about each of these in detail beginning next week with the Entry Form Definition. For now, what you are looking at is a sample of what you create in the Entry Form Definition.
The form designer enables you to create whatever form you want. Out-of-the-box Teaming has many elements that you can add to the form. Any element that doesn't exist can be created and inserted into a form by using HTML in a .jsp file. We plan on giving more detailed instruction on how this is done in episodes to come.
Let's think about a simple job application form. What would it look like? What information would you need? We recommend drafting the form by hand to begin with. Our draft looks like the image below.
Click to View
Keep in mind that this is a draft. It doesn't need to look polished.
This is a great start for what we'll do next week. We encourage you to experiment with your own forms and workflows. Send us your ideas and we'll find a place for them on the library. Please feel free to contribute feedback, forms, and workflow to email@example.com.
Disclaimer: As with everything else at Cool Solutions, this content is definitely not supported by Novell (so don't even think of calling Support if you try something and it blows up).
It was contributed by a community member and is published "as is." It seems to have worked for at least one person, and might work for you. But please be sure to test, test, test before you do anything drastic with it.