How to: Add Contacts to Release Control

To add "Contacts" to Release Control (or the former Release Manager), follow these instructions. Though written specific to RLC, the procedure described here could be used to reference any item with any other item.

Optionally, download and extract images in attached "" archive to view "img#" references in this article.

The default "Contacts" auxiliary table is in "Global" application. If you intend to use a different contacts table located in another app, simply reference your app instead of "Global" as you follow the instructions.

  1. Open Composer
  2. Start "Open" choosing "Look in: Repository"
  3. If "Global" is missing (img1), then...
    1. Go to Application Repository in browser
      1. Select Environments section
      2. Highlight intended environment if more than one
        1. Select "Deployments" tab and find "Global" application in list
        2. "Get" the application (img2). In prompt, ensure 'Create snapshot' is unchecked/deselected
        3. Status of "Get" can be viewed in Activities section
    2. Return to composer, refresh repository list, and continue with step 4.a
  4. If "Global" has red icon (not blue & yellow, img3), then...
    1. Open "Global" process application
    2. Check-in Global (okay to 'save changes' if prompted)
    3. Continue with step 5.a
  5. If "Global" has blue & yellow icon (not red), then...
    1. Open process application where you want to use/see contact such as "RLC - Release Train" or "RLC - Release Package" (formerly, "RLC - Application Releases")
    2. Check-out entire process application
    3. Make the following changes
      1. In References section
        1. Right-click "References" and select "Add Application Reference"
        2. Choose "Look in: Repository" and select "Global" app (img4)
      2. In Data Design section
        1. Select the application's primary data table
        2. Add "Contact" field via method described below:

          Attention - Decision must be made here. Please review this section carefully.

          There is a system Contact field which is single-relational which ONLY works with Global contacts table (option α). If using a different table and/or app, you can also create your own single-relational field (option β). In either case, you can create your own multi-relational field (option γ).

          If you think or know you want to present data from the contact, it is recommended to use α or β. You will be limited to one contact per item, but can add Sub-Relational fields for any column of the Contacts table.

          If you think or know you need to allow multiple contacts per item, you will need to use γ. You will not be able to add Sub-Relational fields for presenting the data.

          To cover both cases, consider doing α or β as "Primary Contact" and γ as "Secondary Contacts" - this allows you to present extra primary contact information on forms via Sub-Relational fields but doesn't limit each item to a single contact.

          1. Option α
            (*ONLY if using built-in "Contacts" table from "Global" app)
            1. Right click in the list of fields and choose "Add New > System Fields > Contact" (img5), OR drag the "Contact" field from the Table Palette into list
            2. Field is pre-configured. Go To 'γ' for adding multi-relational field or skip to step 5.c.iii.
          2. Option β
            1. Right click in the list of fields and choose "Add New > Single Relational", OR drag field type from Table Palette into list
            2. Name the field as you wish
            3. In the options section (img6), choose Application = "Name of your app" and Table = "Name of your table"
            4. Go To 'γ' for adding multi-relational field or skip to step 5.c.iii.
          3. Option γ
            1. Right click in the list of fields and choose "Add New > Multi-Relational", OR drag field type from Table Palette into list
            2. Name the field as you wish
            3. In the options section (img6), choose Application = "Global Application" and Table = "Contacts" (or your custom app/table)
            4. Continue to step 5.c.iii
      3. In Visual Design section
          For each form where you would like to see/edit value:
        1. Open form
        2. Drag your new field from the "Form Palette" to any location on form, except any container called "Hidden Fields" or "Hidden Section" (img7)
    4. Save changes locally
    5. Validate changes
      (Note: first validation may show a few "Very High" warnings regarding missing transitions. Validate once again and these should disappear).
    6. Deploy changes
    7. Verify changes
      1. Transition form (img8/8b)
      2. State form (img9/9b)
Continue reading
1377 Hits

Release Control 6.2 Bonus Feature: Creating and Managing Custom Timelines

Release Control 6.2 Bonus Feature: Creating and Managing Custom Timelines

If you've installed or upgraded to Release Control version 6.2, you now have access to a handy bonus feature that makes it easy to create and manage custom timelines. This has its own separate user interface.

Although you can define timelines directly in SBM, it's nice to have a separate UI that is designed just for this purpose. It simplifies things. 

Here are just a few details to get you started, so you can get in there and explore on your own.

How do I get to the UI?

To get started, enter the following URL (changing the server name to your SBM server, of course):



What report should I choose?

You must choose a report that has all the data needed to display as a Gantt chart, such as the "All Release Trains" report. You can use that report as an example to create others of your own.

See this related blog that tells how to create various reports that can be used for timelines, such as All Environments, All Scheduled Maintenance, and All Scheduled Release Packages. 

Although this blog was written for RLC 6.0, most of it still applies to RLC 6.2. 

What can I define for my timeline?

There are several selections you can define for each timeline, such as:

  • Ranges

    Ranges are the colored bars that render horizontally across the timeline. Ranges must have a start date and an end date and may also have actual start and end dates, so that you can visually compare planned versus actual.

  • Events

    Events are single points in time represented on the timeline with icons. Like ranges, events can optionally have actual dates and icons configured for comparison.

  • Overlays

    Overlays have both ranges and events. They come from a different report than the primary items and are linked with a relational field. You can configure as many overlay items as you need. This powerful feature enables you to plot ranges and events from different items directly on the timeline of the primary item. In the default configuration, we use this to plot milestones on the release train.

  • Child Items

    In addition to overlays you can add child items, which can have their own ranges, events, and even overlays. If you expand the primary items you will see all of its child items plotted on the timeline underneath it. 

For more details on each of these, see this related blogAlthough this blog was written for RLC 6.0, most of it still applies to RLC 6.2.   

Share with the Community 

Please share your experiences with this new feature with the Community. We look forward to hearing from you!



Continue reading
4349 Hits
1 Comment

How To: Adjust RLC Deployment Log so that 'QA Result Time' outputs as date/time

In Serena Release Control (RLC), users can view information about task executions from the RLC Deployment Log and associated reports. The RLC Deployment Log is a special auxiliary table created as a "solution view." One of the default pieces of information for any task execution is the QA Result Time. This value is stored and displayed as a string, which unfortunately means it will not be adjusted to the user's local time. These instructions explain how to fix the solution view so that the value is output as date/time.

You must know if you're using Microsoft SQL or Oracle SQL for your databases. There are two provided files; one for each type. Download one of the provided ZIP archives and extract the included XML file. Alternatively, you may make the file edits manually as detailed in step 7.

Download: or

Warning!: This process will involve removing and reimporting the RLC Solution Views. Privileges to the RLC Deployment Log and RLC DU Execution Log will have to be reapplied. Additionally, reports associated with these tables will have to be recreated. Parameters for recreating the 3 default reports - "RLC Deployment Log for Release Packages", "RLC Deployment Units for Environment", and "RLC DU Execution Log for Deployment Path" are included.

For each application engine server:

  1. Navigate to the following location:
    ..\installation directory\SBM\Application Engine\ViewDefinitions\
  2. Remove RLCViews.xml file from directory and backup in another location.
  3. Open command prompt to the Application Engine bin directory. The prompt should look like:
    ..\installation directory\SBM\Application Engine\bin>
  4. Enter command:
    ttadmin.exe /GenerateViewsAllowDelete
    A dialog will appear and then close. You may leave command prompt open.
  5. Return to the ViewDefinitions directory.
  6. Move provided RLCViews_Microsoft.xml or RLCViews_Oracle.xml (extracted from ZIP) into directory, or move a copy of the original RLCViews.xml file back in and open for editing.
  7. If you're using a provided file, continue to next step. If you're modifying RLCViews.xml file then replace the following line (26):
    NULLIF(qaResultTime_property.VALUE,'') TS_QA_RESULT_TIME,
    with one of the following:
    • Microsoft:
      CONVERT(datetime2,NULLIF(qaResultTime_property.VALUE,'NONE'),121) TS_QA_RESULT_TIME,
    • Oracle:
    Save the file changes.
  8. Return to the command prompt and enter command:
    ttadmin.exe /GenerateViews
  9. Open SBM Application Administrator (web admin) and reapply user/group roles for RLC Deployment Log and RLC DU Execution Log tables.
  10. Open SBM Report Center and re-create necessary reports:
    1. RLC Deployment Log for Release Package
      • Report Item Type: RLC Deployment Log
      • Columns: Start Time, End Time, Execution Type, Execution Status, Path Element ID, Environment ID, QA Result, QA Result Time, Parent TC ID, Source TC Execution ID
      • Search Filter: 'Task Collection ID' contains (Query At Runtime)
      • Sort by: Start Time - Ascending
      • Privilege Category: Guest
      • Reference Name: RLC.DeploymentLogByTCID
    2. RLC Deployment Units for Environment
      • Report Item Type: RLC DU Execution Log
      • Columns: Deployment Unit, Release Package, End Time, Task Execution Status, Release Engineer
      • Search Filter: 'Environment TTID' like (Query At Runtime)
      • Sort by: End Time - Descending, Then by: Task Execution Status - Descending
      • Privilege Category: Guest
      • Reference Name: RLC.DUsForEnvironment
    3. RLC DU Execution Log for Deployment Path
      • Report Item Type: RLC DU Execution Log
      • Columns: Deployment Unit, Configuration, Type, Release Package, Task Execution Status, Start Time, End Time
      • Search Filter: 'Task Collection Execution ID' contains (Query At Runtime) and 'Environment TTID' like (Query At Runtime)
      • Privilege Category: Guest
      • Reference Name: DusForDpExecution
  11. Enjoy! Now when users view the data, the QA Result Time value will be adjusted as prescribed by their SBM profile settings.
Continue reading
3423 Hits

Implementing Release Control Across Multiple Product Groups

Serena Release Control comes with multiple predefined projects. Which of these projects do you need to duplicate in order to limit product groups access to only their release packages, environments, deployment paths?


This article explains how you can configure Serena Release Control to work across the multiple product groups. It explains which projects you should create duplicates of and which projects can be left alone as they are only used in the background.

The following approach is designed for easier maintenance and future upgrades. 

Here are the topics covered:

  1. Creating Projects for Each Group
  2. Granting Privileges
  3. Updating Work Center Feeds
  4. Duplicating or Modifying Workflows
  5. Common Problems and Solutions


Continue reading
3844 Hits

Setting a default value for the Task Template in Release Package

RLC 6.0 has implemented a new feature that allows, during the creation of a Release Package (RP), setting a default set of tasks to be implemented during the RP’s deployment. A few steps through Application Administrator and Composer allows for this to be easily handled.

Continue reading
4320 Hits

Recent Tweets