Forms

In BMC Remedy, Forms are a fundamental component used to define the structure, appearance, and behavior of the user interface (UI). Forms serve as the interface where users interact with the system to create, view, modify, and manage data. They are also the basis for workflows, reports, and integrations in Remedy.

Types of Forms in BMC Remedy

1. Regular Forms:

   • Used to store and manage primary data records.
   • Example: Incident form, Change Request form, Problem form.

2. Join Forms:

   • Combine data from two or more forms into a single view based on a common field.
   • Useful for reporting and displaying related information.
   • Example: Linking Incidents to associated Configuration Items (CIs).

3. Display-Only Forms:

   • Do not store data in the database; used to create temporary, dynamic interfaces.
   • Example: A custom form for searching tickets or launching specific workflows.

4. Dialog Forms:

   • Designed for short interactions or pop-up windows, such as confirming an action or entering additional details.

5. View Forms:

   • Used to present external data sources (like databases or web services) within the Remedy system.
   • Example: Displaying data from an external HR system.

6. Vendor Forms:

   • Access external data sources directly through Remedy, acting as a bridge for integrations.
   • Example: Pulling real-time inventory data from an external application.

Components of a Form

1. Fields:

   • The primary building blocks of forms, used to capture and display data.
   • Types of fields include:
     • Character Fields: Store text data.
     • Selection Fields: Provide dropdowns, radio buttons, or checkboxes.
     • Date/Time Fields: Capture date and time values.
     • Attachment Fields: Allow file uploads.
     • Table Fields: Display related records in a tabular format.

2. Menus:

   • Attached to fields to provide predefined or dynamic lists of values.

3. Workflow Triggers:

   • Forms are integrated with workflows like Active Links, Filters, and Escalations to perform automated actions.

4. Permissions:

   • Access to forms, fields, and data is controlled via permissions for roles, groups, and users.

5. Appearance:

   • Forms can be customized with tabs, panels, colors, and labels to improve usability and align with organizational branding.

How Forms Are Used in Remedy

1. Data Capture and Storage:

   • Forms act as containers to store data entered by users.
   • Example: Storing ticket details in the Incident form.

2. Search and Retrieval:

   • Forms are used to search, retrieve, and display data based on specific criteria.
   • Example: Searching for incidents by status or assigned group.

3. Workflow Automation:

   • Workflows like Active Links, Filters, and Escalations are triggered based on user actions or conditions in forms.
   • Example: Automatically assigning an incident to a group when a specific category is selected.

4. User Interaction:

   • Forms provide the interface for users to interact with the system.
   • Example: Approvers using an Approval form to review and approve changes.

Examples of Common Forms in Remedy

1. Incident Form:

   • Used to create, update, and track incidents.
   • Fields: Incident ID, Summary, Description, Priority, Status, Assigned Group, etc.

2. Change Request Form:

   • Captures and manages details related to change requests.
   • Fields: Change ID, Requestor, Description, Risk Level, Approval Status, Implementation Date.

3. Configuration Item (CI) Form:

   • Stores information about assets and configuration items in the CMDB.
   • Fields: CI Name, Type, Status, Location, Relationships.

4. Service Request Form:

   • Allows users to submit service requests via a self-service portal.

5. Approval Form:

   • Used by managers or stakeholders to approve or reject requests.

Best Practices for Form Design in Remedy

1. Keep It Simple:

   • Design forms to be user-friendly and avoid cluttering them with too many fields.

2. Group Related Fields:

   • Use tabs or panels to group related information for better organization.

3. Leverage Workflows:

   • Automate field behaviors, validations, and actions using Active Links and Filters.

4. Use Field Permissions:

   • Restrict sensitive information by applying field-level permissions.

5. Optimize Performance:

   • Avoid creating overly complex forms that may slow down performance.

6. Test Thoroughly:

   • Ensure forms work as expected, especially when integrating workflows or dynamic data sources.

Common Challenges and Solutions

1. Performance Issues:

   • Solution: Use indexed fields for large forms and avoid unnecessary fields.

2. User Confusion:

   • Solution: Provide clear labels, tooltips, and logical field arrangements.

3. Data Integrity Issues:

   • Solution: Enforce field validations and use menus to standardize inputs.

Let me know if you need more details about designing forms, specific form types, or how to implement workflows on forms in BMC Remedy!