You’ve created all your requirements classes and their respective attributes but the layout of the attributes on the form is not very user friendly. You may want to group related attributes or position required attributes towards the top of the form.
So how do you change the layout so that it is easy to use, efficient, and facilitates good requirements authoring?
With custom form templates. Each database and project can have its own set of template files. A template file represents the custom layout for a single requirements class type, an entire project, or all projects.
Setting up the templates is easy as 1-2-3.
So let’s get started.
On the Dimensions RM application server go to the default template directory under Tomcat. If you accepted the default installation directory, the path is “C:Program Files (x86)\Serena\Dimensions 12.2.1\Common Tools 188.8.131.52\tomcat\7.0\webapps\rtmBrowser\forms”.
Create a new directory and name it the same as your database name. In my example, my database name is “RM12”.
Under this directory, create a new folder and name it the same as your RM project. In my example, my project name is “QLARIUS”.
This is no doubt the tedious part of the process. You will create an XML file for each of your requirements classes that you wish to customize. Note that if a class does not have user-defined template (i.e. XML file), it will simply use the default template under “common”. In other words, it’s not all or nothing. You can create/custom as needed or over time.
I’ve included my examples at the end of this blog for you. Again refer to the online help that specifies the things you can do and what all the tags mean.
But I encourage you to keep a few simple rules in mind when it comes to the design.
Keep it simple. The best forms avoid unnecessary elements and are clear in the language they use on labels and in the layout.
Be consistent. By using common elements in your form, users feel more comfortable and are able to get things done more quickly. This will also facilitate efficiency.
Be purposeful in the layout. Careful placement of attributes can help draw attention to the most important pieces of information and can aid scanning and readability. Especially the placement of required attributes. Don’t bury them at the end of the form.
That’s it. Easy as 1-2-3. You now have nice readable forms that will enable your users to be more efficient with their requirements authoring and management.
For detailed information refer to the online help under Customizing Web Forms.
Do you have an example template you would like to share with others? If so, please contribute to Serena Central or drop me an email and I will share it for you.