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 "images_HowToContacts.zip" archive to view "img#" references in this article.

Attention
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
125 Hits
0 Comments
Featured

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):

http://<SBM_SERVER>/workcenter/tmtrack.dll?StdPage&Template=rlm/customGanttManager

 

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
878 Hits
7 Comments
Featured

Why I Love This Product Essay Contest

We know you love using Micro Focus products, so now’s your chance to tell us about it. The ‘Why I Love This Product Essay Contest’ is a chance for you to tell us how Micro Focus products make your life—and your users’ lives—easier. Whether you’re using ZENworks to manage your endpoint devices or Silk to accelerate the delivery of your applications, we want to hear how much you love Micro Focus products. ONE-T-shirt_smPlus, by entering the contest, you’ll receive a free Micro Focus Community t-shirt.

To participate in the contest, simply send your finished essay to cool.guys@microfocus.com with the subject line that includes the title of your essay as well as the solution group your product falls under. For example: Why Visual COBOL Rocks my World—COBOL Development All entries must be submitted by 10 July 2017 to be eligible.

Continue reading
1030 Hits
2 Comments

SSL Primer - Day 4 - Self-Signed Certificate

Self-Signed Certificate

Self-signed can be a contentious term.  Many would say a certificate is self-signed because it is not issued by a well-known certificate authority.  Well-known can mean VeriSign, Go Daddy or your company's certificate authority.  Using this definition does us a disservice because it complicates SSL/TLS language by using a practical definition instead of a technical definition. 

Continue reading
1673 Hits
0 Comments

New Dimensions CM Webcasts coming in November, December and January

 

 

I invite all Dimensions CM customers to join us for our new Monthly Webcast Series. It would be great to hear back from those who attend, and to solicit your feedback and thoughts on additional Webcasts we can deliver that would be of value to you and your organizations.

 

'Sneak' src=http://info.serena.com/rs/564-DHN-940/images/Email-Banner-DimCM-Launch-Series-Dec2016toJan2017.jpg

 

 

 

We look forward to seeing you,

 

Kind Regards

 

Ash

Continue reading
1406 Hits
0 Comments

Recent Tweets

Twitter response: "Invalid or expired token."