Performance Tuning Guide - EMC Community Network

Designing the Application
• Text Fields: For a form with 100 text fields, the template and layout file sizes are 34 KB and 52 KB,
respectively. During runtime, the corresponding forms processor size is 1 MB.
• Adaptors: Processor requirements spike for forms using adaptors that generate large amounts
of data. One adaptor can generate data that translates into 300 XML nodes. This results in the
form processor generating about 10,000 new objects to represent the read/write, hide/show, and
valid/invalid properties for the XML nodes.
Designing search forms
TaskSpace component templates (created in Forms Builder) define the set of objects, stored in the
repository, that get searched for (queried) in TaskSpace forms. To maximize system performance,
avoid unnecessary functions (querying) in your templates and consolidate your queries so that the
fewest number of queries provide required data for a TaskSpace form. Design your object model to
use SDTs instead of simple process variables (Designing the process object model (using structured
datatypes), page 37). Only use search criteria that is necessary for users to complete their jobs. The
following sections provide specific performance tips related to search-related functions configured
for TaskSpace forms.
• Using searchable attributes, page 42
• Using search criteria, page 43
• Using search restrictions, page 45
• Using advanced searches, page 45
Using searchable attributes
The search template, task list template, folder contents template, and process instance list template
include a screen, like the one shown in Figure 15, page 43 for the search template, to specify attributes
to be searched and the columns in which to display the results of the search.
42 EMC Documentum xCP 1.0 Performance Tuning Guide