Creating and Updating Services in the Catalog › Service Options and Service Option Elements › Service Option Details Tab › Fields for Form Elements

Fields for Form Elements

Complete the following fields for a Form service option element. You use a Form element to attach a Form Designer form to this service option.

Note: Form Designer forms are preferred over CA Workflow forms.

Display Text

Specifies the descriptive text to display for this form to administrators browsing the list of forms.

Form Name

Specifies the name of the Form Designer form that you want to define as a service option element for this service. Use the Search icon to view the list of forms and select one.

Hidden and Disabled fields

If you do not want to hide or disable the entire form under any conditions, leave the Hidden and Disabled fields empty.

If you do want to hide or disable the entire form, enter the corresponding JavaScript expression in the Hidden or Disabled field. You can hide or disable the form according to the request status, the user role or business unit, or other criteria. Use the following format: $(_.object.property). The expression must return a value of true or false.

You can specify JavaScript expressions in the Hidden field, the Disabled field, or both. Examples follow:

• To hide or disable the form when the request status is Pending Approval, enter the following JavaScript expression in the Hidden or Disabled field: $(_.request.status == 400).
• To hide or disable the form for the end user roles only, enter $(_.user.role == ‘enduser’).
• To hide or disable the form from all business units except ca.com, enter $(_.bu.id != ‘ca.com’).
• To disable the form when the request status is Fulfilled, enter $(_.request.status == 2000).

Note: When an entire form is disabled, it is disabled but visible during all stages of the request lifecycle except checkout. During checkout, a disabled form is both disabled and hidden.

Note: Unlike CA Workflow forms, Form Designer forms do not get stored in the filestore, a single location for shared files. We recommend using a filestore if you are using multiple Catalog Component servers. Form Designer forms are automatically available to all authorized users specified by the administrator, as explained in the chapter "Using the Form Designer." However, as a best practice, store other shared files except Form Designer forms in the filestore, as explained in the Implementation Guide.