Adding the Request Widget to Any App

0 Likes

RequestWidget_20151001-195645_1.png

Serena Release Control 6.0 introduces us to request providers and request collections. These features give much more flexibility in being able to relate requests, especially 3rd party requests, to SBM items. You are able to relate requests from multiple sources - SBM requests, Dimensions Requests, ServiceNow tickets, and JIRA issues - and view this list of items in one place.

To view the related requests, you must add the Request Collection widget to your application. By default, only the Release Package application has the Request Collection widget, but you can easily add the widget to other of your SBM applications, such as Release Trains or Application Releases. The only requirement is that you have Release Control 6.0 installed.

 

Important: It is required that you have Release Control installed in order to use the request collection widget. 

To implement the request widget in your application:

  1. Open the application in Serena Composer.
  2. Under Extensions/Web Services, import scriptRunnerService.wsdl file found in the zip.
  3. Under Extensions/Form Extensions, import Request Collection Widget.cfx.
  4. In the primary table, add a numeric field to store the request collection id. This field will be referred to as RequestCollectionId field in these instructions.
  5. Create a custom state form to display the widget:
    1. Add the RequestCollectionId  field to the form.
    2. Drag on widget.
    3. On the parameters tab:
      • Map the request collection id parameter to your RequestCollectionId  field.
      • Set the mode as view.
        mapping.png
    4. Add a form action to load the widget. This can occur when the form loads. Here is an example: 
      loadformaction.png
  6. Create a custom transition form which will be used to modify the request collection:
    1. Add the RequestCollectionId  field to the form.
    2. Drag on the widget.
    3. On the parameters tab:
      1. Map the request collection id parameter to your RequestCollectionId  field
      2. Set the mode as edit.
    4.  Add a form action to load the widget. 
    5. Optional: You can use a form action to check to see if the request collection has been edited (requests deleted or added) using the "RequestWidget has been edited" condition. For example, the following form action will add a note to the System Log field when the request widget has been modified. If the collection was not modified, the transition will simply be canceled.
  7. On a transition, add an action to call the webservice to create the request collection. Map it to the createRequestCollection.groovy script. 
    1. Select the transition and choose to Call a Webservice after the transition occurs. 
    2. On data mapping, enter the following for inputs:input.png

      Important: If you are creating the request collection on submit, you cannot map stringParam0 to the item id or Context:Item ID values since they do not yet exist. 
    3. Enter the following for outputs. 
      output.png
  8. Deploy the app, ensuring that the correct endpoint is set for your server, for example: http://servername:8085/rlc/scriptRunnerService.

If you have configured request providers, such as the SBM Provider or Dimensions Provider included with Serena Release Control 6.0, you will be able to relate requests to this item.

Labels:

How To-Best Practice
Comment List
Anonymous
Parents Comment Children
No Data
Related Discussions
Recommended