Share this page

# Scenario 6: Deploy a fix forward solution using a request

This scenario demonstrates how to prepare a fix and deploy if forward over the part of the application that is not working.

Note: To run this scenario, first set up the environment, as described in Prerequisites.

In this topic:

## Scenario overview

A defect at the QA stage is preventing testing on the Qlarius web application.

- The QA manager raises a Dimensions CM change request to track the defect.

- The development team lead primes a task from the request.

- A developer fixes the defect, delivers the fix and relates it to the task, builds the task, and captures the build outputs in Dimensions CM.

- The team lead promotes and deploys the request and task to the SIT stage and deployment area, and then promotes them to the QA stage.

- The QA manager deploys the request and task to the QA deployment area.

Back to top

## Scenario information

- The following stream is used: QLARIUS:JAVA_BRANCHA_STR.

- There is a division of responsibilities between the employees at the following stage transitions:

  - SIT to QA

  - QA to PRE-PROD

- A build is required at the DEV stage.

- This scenario uses the following deployment areas:

  Stage | Deployment area | Deploy by Default enabled on area?
  --- | --- | ---
  DEV | LCL_DEV_JBRNCHA_AREA03 | Yes
  SIT | LCL_SIT_JBRNCHA_AREA03 | Yes
  QA | LCL_QA_JBRNCHA_AREA03 | No

For a list of the promotion and deployment privileges required by the users, see Scenario privileges.

Back to top

## Scenario prerequisites

To run this scenario, you must complete Scenario 3: Deploy requests to multiple deployment areas.

Before you start this scenario, complete the following steps:

1. Log in to the web client as any user.

2. Switch to the following stream: QLARIUS:JAVA_BRANCHA_STR.

3. Browse the QA web application deployment area: In the My Current Project view, expand Deployment Areas > QA Stage > LCL_QA_JBRNCHA_AREA03 > Qlarius Underwriter.

4. In the content pane, make a note of the revision of AutoQuote.jar that is currently deployed in the QA deployment area.

5. Log out of the web client.

Back to top

## Run this scenario

The following table describes the tasks performed in this scenario.

Action | Procedure
--- | ---
Tao, the QA manager, does some research and finds that the problem is in a single file, AutoQuote.jar, in the LCL_QA_JBRNCHA_AREA03 web application deployment area. Tao decides that the quickest solution is to prepare a fix and deploy it forward over the file that is causing the problem.
The QA manager raises a change request to track the defect. | Tao raises a change request to fix and track the defect. Log in to the web client as Tao. Switch to the following stream: QLARIUS:JAVA_BRANCHA_STR. In the Requests view, on the toolbar, click New and select CR. The New Request dialog box opens. In the Title field, enter a title for the request, for example, Fix Autoquote.java. In the Detailed Description field, enter a description. On the Attributes tab, from the Severity/Priority list, select a priority. Click Submit and then Close. The new request is added to Rita’s request inbox with the following ID: QLARIUS_CR_n. By default the request is at the DEV stage when it is raised.
The QA manager delegates the request to the team lead. | Tao delegates the request to the development team lead, Ted, whose team is responsible for maintaining Qlarius. Select the request, and on the toolbar click Delegate. The Delegate wizard opens. Check that the Capability option is set to Secondary. From the Role to Delegate list, select IMPLEMENTOR, and click Next. In the Candidate Users Authorized for Role Assignment list, select Ted, and click Add. The wizard closes automatically. Dimensions CM sends an email to Ted notifying him that a request has been added to his Request inbox.
The QA manager actions the request to its next state. | Tao actions the request to its next state, UNDER WORK: Select the request, and on the toolbar select Action. The Action wizard opens. Check that the To Next State field is set to UNDER WORK. Click Finish and then click OK. The request is removed from Tao’s request inbox. Log out of the web client.
The development team lead primes a child task from the request. | Ted reads the email, views the request in his Request inbox, and primes a child task from the request. Log in to the web client as Ted. Switch to the following stream: QLARIUS:JAVA_BRANCHA_STR. In the Requests view, select the Request inbox and then the request raised by Tao. On the toolbar, click Prime, and select Task. The Prime Request dialog box opens. (Optional) Update the detailed description. Click Submit and then click Close. The new child task is added to Ted’s request inbox with the following ID: QLARIUS_TASK_n. By default, the child task is at the DEV stage when it is raised.
The development team lead delegates the task to a developer. | Ted delegates the child task to a developer, Dinesh. Select the child task, and on the toolbar click Delegate. The Delegate wizard opens. Check that the Capability option is set to Secondary. From the Role to Delegate list, select IMPLEMENTOR, and click Next. In the Candidate Users Authorized for Role Assignment list, select Dinesh, and click Add. The wizard closes automatically. Dimensions CM sends an email to Dinesh notifying him that a task has been added to his Request inbox.
The development team lead actions the task to its next state. | Ted actions the task to its next state, UNDER WORK: Select the child task, and on the toolbar select Action. The Action wizard opens. Check that the To Next State field is set to UNDER WORK. Click Finish and click OK. The child task is removed from Ted’s request inbox. Log out of the web client.
The developer updates their work area from the stream. | Dinesh reads the email, checks his Request inbox, and updates his work area: Log in to the web client as Dinesh. Switch to the following stream: QLARIUS:JAVA_BRANCHA_STR. Change Dinesh’s work area to the one that you created earlier (see the prerequisites at the start of Scenario 3). In the Items view, in the navigation pane, select the folder that contains Autoquote.java: Qlarius Underwriter > qlarius > interfaces. On the toolbar, click Update. The Update From Stream wizard opens. Click Next. Click Finish and then Close. Dinesh’s work area is updated.
The developer fixes the defect. | In Dinesh’s local work area, edit Autoquote.java. For the purpose of this scenario, make a minor edit, for example, add a comment to the top of the item.
The developer delivers the item and relates it to the task. | Dinesh delivers the fixed item to Dimensions CM and relates it to the task: In the Items view, on the toolbar, click Deliver. The Deliver to Stream wizard opens. Check that the Modifications option is selected. Click Next. Verify that AutoQuote.java is selected and click Next. In the Relate to Request(s) field, click Select. The Select Request dialog box opens. From the Product Name list, select QLARIUS. From the Type Name list, select TASK. Click Next. Select the task that is delegated to Dinesh, and click Finish. In the Deliver to Stream wizard click Finish and then Close.
The developer verifies that the item was automatically deployed to the DEV area. | The Deploy by Default option is enabled for the DEV area, so when Dinesh delivered the item, it was automatically deployed. He checks that the item was successfully deployed. Select the Deployment view . To view information only for the current stream, click the filter button at the top right of the navigation pane, and select Show Current Stream. Select the History tab, and in the navigation pane, select the DEV stage node. In the content pane, verify that the AutoQuote.java was successfully deployed to the LCL_DEV_JBRNCHA_AREA03 deployment area.
The developer builds the task and captures the outputs. | Dinesh builds the task in the DEV web application deployment area and captures the build outputs in Dimensions CM against the task. In the Requests view, select the Request inbox. Select the task, on the toolbar click Build, and select Build. The Run Build wizard opens. In the Build Configuration field, accept the default configuration. From the Build Stage list, select DEV. From the Build Area list, select LCL_DEV_JBRNCHA_AREA03. Click Next. Select the option Check In Build Outputs Automatically. This checks the build outputs in to Dimensions CM. To relate the build outputs to specific requests when the outputs are checked in to Dimensions CM, in the Specify the request(s) field click Select. The Select Request wizard opens. Do the following: From the Product Name list, select QLARIUS. From the Type Name list, select TASK. Click Next. Select the task that is delegated to Dinesh, and click Finish. In the Run Build wizard, click Next. Accept the default build option selections (none) and click Next. Accept the default target selection options. In the target list, select Jar Files. Click Next. Review the summary of the build command, and click Finish. (Optional) To monitor the progress of the build, click the Job <ID number> link. Click Close.
The developer verifies that the build was successful. | Dinesh verifies that the build was successful and that the outputs were deployed to the DEV web application deployment area. To verify that the build was successful, select the History tab in the Deployment view. In the navigation pane, expand the DEV stage node and select LCL_DEV_JBRNCHA_AREA03. In the content pane, verify that the Event Result column displays Succeeded for the following objects: Autoquote.jar (the event type is Collect) QLARIUS:JAVA_BRANCHA_STR (the event type is Build) Open Autoquote.jar, make a note of the item revision, and click Cancel. To browse the DEV web application deployment area, in the My Current Project view expand Deployment Areas > DEV Stage > LCL_DEV_JBRNCHA_AREA03. Select the Qlarius Underwriter folder. In the content pane, verify that the latest revision of AutoQuote.jar is deployed. This should be later than the revision that you made a note of at the start of this scenario.
The developer delegates the task to the team lead for peer review. | Dinesh delegates the task to Ted for peer review. In the Requests view, select the Request inbox. Select the task, and on the toolbar click Delegate. The Delegate wizard opens. Check that the Capability option is set to Secondary. From the Role to Delegate list, select REVIEWER, and click Next. In the Candidate Users Authorized for Role Assignment list, select Ted, and click Add. The wizard closes automatically. Dimensions CM sends an email to Ted notifying him that a task has been added to his Request inbox.
The developer actions the task to its next state. | Dinesh actions the task to its next state, PEER REVIEW. Select the child task, and on the toolbar select Action. The Action wizard opens. In the New State section, check that the To Next State field is set to PEER REVIEW. Click Next. In the Actual Completed Date field, enter a date. In the Actual Development Effort (hours) field, enter a number. Click Finish. The task is removed from Dinesh’s request inbox. Log out of the web client.
The team lead does a peer review and actions the task to its final state. | Ted has read his email, seen the task in his Request inbox, done a peer review of the defect that Dinesh fixed, and is satisfied with the changes that he made. He actions the task to its final state, CLOSED. Log in to the web client as Ted. In the Requests view, select the Request inbox, select the task, and on the toolbar click Action. The Action wizard opens. Check that the To Next State field is set to CLOSED. Click Finish and click OK. The task is removed from Ted’s Request inbox.
The team lead promotes and deploys the request and the task to the SIT stage and area. | To perform system integration testing, Ted promotes and deploys the request and task to the SIT stage and web application deployment area. In the Requests view, in the Request inbox, select the request. On the toolbar, click Promote. The Promote wizard opens. Check that the Promote Child Requests option is selected. In the Next stage field, check that SIT is selected. Click Next. To deploy immediately, check that the Perform Deployments option is set to As Soon As Possible. In the Areas for Deployment field, select the SIT LCL_SIT_JBRNCHA_AREA03 deployment area. If selected, clear LCL_SIT_JBRNCHA_AREA01. Click Next. Review the summary and click Finish.
The team lead verifies that promotion and deployment operations were successful. | Ted verifies that promotion and deployment operations were successful and that the modified file was deployed to the SIT web application deployment area. Select the Deployment view, and check that only the current stream is displayed. Select the History tab, and in the navigation pane select the SIT stage node. In the content pane, verify that the request was promoted successfully from DEV to SIT. In the navigation pane, expand the SIT stage node and select the LCL_SIT_JBRNCHA_AREA03 deployment area. In the content pane, verify that the request and task were deployed successfully to the SIT web application deployment area. To browse the SIT web application deployment area, in the My Current Project view expand Deployment Areas > SIT Stage > LCL_SIT_JBRNCHA_AREA03. Select the Qlarius Underwriter folder. In the content pane, verify that latest revision of AutoQuote.jar is deployed.
Ted performs system integration testing.
The team lead promotes the request and task to the QA stage. | System integration testing has been completed successfully, so Ted promotes the request and task to the QA stage. Deploy by Default is not enabled, so the request and task cannot be automatically deployed to the QA deployment area. In the Requests view, in the Request inbox, select the request, and on the toolbar click Promote. The Promote wizard opens. Check that the Promote Child Requests option is selected. In the Next stage field, check that QA is selected. Click Next. Because Deploy by Default is not enabled, no deploy options are available. Click Next. Review the summary and click Finish. Dimensions CM sends an email to the QA manager, Tao, notifying her that a promotion has been performed. In the Deployment view, select the History tab, and in the navigation pane select the QA stage node. In the content pane, verify that the request was promoted successfully from SIT to QA.
The team lead actions the request to its next state. | Ted actions the request to its next lifecycle state, IN TEST, so that QA can test the application. On the History tab, select the request, and on the toolbar, click Action. The Action wizard opens. In the New State section, check that the To Next State field is set to IN TEST. Click Next. In the Details of Solution Given field, enter a solution. Click Finish. The task is removed from Ted’s request inbox. Log out of the web client.
The QA manager deploys the request and task to the QA deployment area. | Tao reads the email, checks her Request inbox, and deploys the request and task to the QA web application deployment area. Log in to the web client as Tao. Select the Deployment view, and check that only the current stream is displayed. Select the Pending tab. In the navigation pane, expand the QA stage node and select the LCL_QA_JBRNCHA_AREA03 deployment area. In the content pane, from the Show list, select Requests. Select the request, and on the toolbar click Deploy. The Deploy wizard opens. Check that the Deploy Child Requests option is selected. Check that the Deploy Stage is set to QA. Click Next. To deploy the request and child tasks immediately, check that the Perform Deployments option is set to As Soon As Possible. In the Areas for Deployment field, check that the LCL_QA_JBRNCHA_AREA03 deployment area is selected. Click Next. Review the summary and click Finish.
The QA manager verifies that promotion and deployment operations were successful. | Tao verifies that promotion and deployment operations were successful and that the modified file was deployed to the QA web application deployment area. Select the History tab. In the content pane, verify that the request and task were deployed successfully. To browse the QA web application deployment area, in the My Current Project view expand Deployment Areas > QA Stage > LCL_QA_JBRNCHA_AREA03. Select the Qlarius Underwriter folder. In the content pane, verify that latest revision of AutoQuote.jar is deployed.
The QA team performs their tests.
The QA manager actions the request to its final lifecycle state. | QA testing has been completed successfully, so Tao closes the enhancement request that she raised against the defect. In the Requests view, select the request, and on the toolbar click Action. The Action wizard opens. Check that the To Next State field is set to CLOSED. Click Finish and click OK. The request is removed from Tao’s request inbox.
End of scenario

Back to top

## Scenario privileges

The following tables list the promotion and deployment privileges required by each user in the scenario.

Promotion privilege | Privilege owner | Required at these stages
--- | --- | ---
REQUEST_PROMOTE_NEXTSTAGE ITEM_PROMOTE_NEXTSTAGE | Team lead | DEV SIT

Deployment privilege | Privilege owner | Required for these areas
--- | --- | ---
The DEV and SIT areas are Deploy by Default areas, and no deployment privileges are required.
REQUEST_DEPLOY ITEM_DEPLOY | QA Manager | LCL_QA_JBRNCHA_AREA02

Back to top

https://admhelp.microfocus.com Dimensions CM 8942
Tips to improve your search results... Dimensions CM Help Center CM Help 14.7 All View Local Help Center View Online Help Center Version: