Creating and Using Widgets › Embedding Widgets for Requesting Services and Managing Requests › Decide How to Implement the Widgets

Decide How to Implement the Widgets

Decide how to implement the widgets before you begin embedding them on portal page or other pages.

Follow these steps:

1. Typically, use widgets to let users perform the request life cycle within the context of two pages in your portal or other application:
   • On the first page (the Service Catalog page), embed the Browse and Request widgets. These widgets work together to let catalog users browse the catalog and request services.
   • On the second page (the Service Request page), embed the Status, Edit Request, and Request List widgets. These widgets work together to let catalog users do the following tasks: Review the status of their submitted requests and make minor updates to submitted requests that have not yet been approved or rejected.

     These widgets also work together to let request managers manage their requests pending action by approving or rejecting them.

   This scenario follows this design, using a continuous example on two portal pages.

2. (Optional) Review the widgets on the CA Service Catalog Dashboard Builder, as follows.

   The Dashboard Builder contains sample implementations of each widget. You can use them as a reference while performing the steps in the scenario. These samples are especially helpful when you write the source code for the widgets yourself.

   1. Click Administration, Dashboard Builder.

      The Dashboard Library folders appear. They display the dashboards that you can access.

   2. On the library tree, select CA Components - Template, Service Catalog, Widgets.
   3. Expand the Widgets folder and review the widgets.

   Note: Install ActiveX components, if you are prompted to do so. Some dashboard items require ActiveX. When you first access a Dashboard Builder item, it prompts you to install ActiveX components in your browser, if necessary. In such cases, follow the prompts to install the ActiveX components.