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!



Recent comment in this post
Domenic Lasker
Your post is exceptionally elegantly composed and quickly clarified. It is exceptionally useful for me in dealing with my work wit... Read More
Tuesday, 07 August 2018 12:12 PM
Continue reading
4357 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
3427 Hits

Release Control 6.0 Timeline: Part 2

In Release Control 6.0 Timeline: Part 1 we learned the basic anatomy of the timeline view and how to access and use the timeline editor. The first post focused on customizing the out of the box Release Train timeline. In this post I will show you how to create a new timeline and add it to work center. The end result of this tutorial will be a new timeline which you can access by URL that is added to a dashboard in work center.

Recent Comments
David Berner
sounds great. So when will we be able to play with this (meaning when will you unleash RLM 6 on us)?
Friday, 21 August 2015 12:12 PM
Ryan Cook
It will be unleashed very, very soon
Friday, 21 August 2015 4:04 PM
mnoj verma
Thanks for sharing you have a very nice post kodi for windows 8 update kodi on android box complete guide to Kodi and Streaming Mo... Read More
Saturday, 25 November 2017 10:10 AM
Continue reading
9003 Hits

Release Control 6.0 Timeline: Part 1

Serena Release Control 6.0 comes with a new and powerful gantt report that we call the timeline. Starting with RLC 6.0 it is decoupled from the processes that we ship with and fully configurable. In order to be successful in customizing the timeline or even creating new ones from scratch (details coming in part 2) it is important to understand the anatomy of the timeline and the terminology we use in the editor.

Recent comment in this post
Julian Fish
Great post Ryan. This post really shows the power of the timeline view in Release Control. The best part is that it's not just re... Read More
Wednesday, 19 August 2015 11:11 PM
Continue reading
8603 Hits
1 Comment

Recent Tweets