Naming Form Elements in a Work Item Viewer - EnterWorks_Process_Exchange_(EPX) - 10.5

EnterWorks EPX Process Modeling

Product type
Software
Portfolio
Verify
Product family
EnterWorks
Product
Precisely EnterWorks > EnterWorks Process Exchange (EPX)
Version
10.5
Language
English
Product name
Precisely EnterWorks
Title
EnterWorks EPX Process Modeling
Topic type
Administration
Configuration
First publish date
2007
ft:lastEdition
2023-07-28
ft:lastPublication
2023-09-20T03:37:01.911821

Programming clarity is enhanced if you use form element names that tie together the elements on a specific form, because a work item properties hash table uses the form element names you assign as keys.

Note: Do not use a reserved key name. These begin with sys_. Any key name preceded with sys_ will not be saved because sys_ indicates that this is a reserved system key.

This will be very useful if you have programming needs later that require you to deal directly with the hash table (via JavaScript, or a custom BIC), because you can access entire nested hash tables easily.

Note: Form element names are case-sensitive.

For example, in your Java template file, you might have the following form elements:

biodata_name

biodata_age

biodata_address_street

biodata_address_city

The hash table extracts these elements and organizes them as:

biodata

name

age

address

street

city

Important: Within a given template file, every form element should have a unique name. If two or more elements have the same name in a work item viewer file, the results can be different depending on which Web server is being used.

You should not use a form element named simply biodata if there are other elements using biodata as a prefix, such as biodata_name. This could result in only the single element or only some of the hierarchical named elements being stored. Errors will probably occur when the work item is reopened.