Using Your Process Apps for Requirements and Development

The Default Implementation

Following is a summary of how the Requirements and Development integration is implemented and what must or must not be changed to connect your process app to Release Manager.

Displaying Associated Items:

In Application Release, Turnover, and Release Train process apps, in the Base State Form Requirements/Development tab, REST Grid widgets point to specific queries in the SBM Relationship Service table. You should not change these, or the implementation will no longer work.

Associating Items:

In the Application Release and Turnover process apps, the Associate SBM Bus Request and Associate SBM Dev Tasks forms display the possible items to associate based on performing a title search of the business requests and development tasks. For each, an embedded report populates the multi-relational fields using the result of the filter and the selections made. The reports for these are SBM Composer reports defined in the Sample Business Requests and Sample Development Tasks. You will need to create similar reports in your process apps.

Specific database field names in hidden multi-relational fields point to where information is stored in the SBM Relationship Service table. This information captures the relationships between the application release item and the Sample Business Requests and Sample Development Tasks items. The RLM Business Request field points to CUST_LINKED_BR and the RLM Dev Tasks field points to CUST_LINKED_DT. The database field names are very specific, and if they are not specified correctly in the multi-relational fields, the integration will no longer work.

Connecting Your Process Apps

The following procedure tells how to integrate your own process apps with the default Release Manager Requirements and Development implementation. These changes require knowledge of SBM Composer and SBM process app development. Refer to the SBM documentation if more detail is needed to follow this procedure.

Prerequisite: Release Manager must be installed and configured with all process apps promoted.

Recommended: View the Business Request all Active by Title report definition and Dev Tasks all Active by Title report definition by opening the Sample Development Task and Sample Development Task process apps, respectively. You will be creating new report definitions in your target applications modeled after these.

To update the Requirements and Development integration to point to your own target process apps, in SBM Composer, do the following:

1. Open the target Business Requests process app and add a report definition modeled after Business Request all Active by Title in the Sample Business Requests process app. Publish and deploy your changes.
2. Open the target Development Tasks process app and add a report definition modeled after Dev Tasks all Active by Title in the Sample Development Tasks process app. Publish and deploy your changes.
3. Open the Application Release process app.
   1. Create an application reference to your target application.
   2. Add a multi-relational field with the database name CUST_LINKED_BR. The database name must be exactly as shown here. Display name can be any valid name. Point the field to the target Business Requests application. Use the RLM Business Request field as an example.
   3. Add a multi-relational field with database name CUST_LINKED_DT. The database name must be exactly as shown here. Display name can be any valid name. Point the field to the target Development Tasks application. Use the RLM Dev Tasks field as an example.
   4. On the Base State form, History tab, Hidden Fields section: Replace the RLM Business Request and the RLM Dev Tasks fields with your newly-created fields from steps (3b) and (3c).
   5. On the Associate SBM Bus Request form, configure the report to point to the report definition you created in step (1).
   6. On the Associate SBM Dev Tasks form, configure the report to point to the report definition you created in step (2).
   7. Publish and deploy your changes.