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
12 Hits

Urgent: SBM 10.x default certificates expire on 16th September. Your system will fail if you have not updated them.

ALERT: SBM 10.x default sample certificates expire 16th September and SBM will fail if they have not been updated. For more details please check the KB article here -

If you need any help or advise please contact Support.

Continue reading
202 Hits
1 Comment

Embedded Reports in Print View

I have frequently come across customers that are looking to replace paper or MS Word forms with SBM.   This is a fantastic idea and SBM is a good fit.  The challenge we encountered in the past was that there was the occasion when the contents of the SBM record needed to be printed that included an embedded listing of related records.  

As you know we offer the print form that provides you the ability to configure the print view.  If you desire a pdf format, then you can choose to print to pdf.  However, not until SBM 11.2 did you have the embedded report widget available in the print form.

So, now as of SBM 11.2, you can add an embedded report widget, which now allows you to include that related list in your print form.  

Still trying to think of a use case?

How about invoicing?  If you read my blog on inserting line items, I used the invoice as an example.  Now you have the ability to print that invoice with the embedded list of items included on the invoice.  Check out the SBM_Invoice.pdf.

Configuration is not different from adding an embedded form to a state or transition form, but now adds a new benefit!

RECOMMENDED:  Use a report created in the User Workspace and ensure that you set the Optional HTML Template to "urlrpt.htm" in the Additional Options of your report.  This way you will not end up with a bunch of hyperlink text in your print view report.  This also hides the report title, number of items and other extraneous characters at the top of other report templates.

Continue reading
264 Hits

Advanced Reports Group & Roles || Users & Roles

Included in this post is the configuration and report queries so that you can create a list of users and their assigned roles by project and a list of groups and their assigned roles by project.

Continue reading
352 Hits

Introducing ModScript - the next evolution in SBM scripting


Beginning in version 11.3, SBM supports a scripting language called SBM ModScript, which offers a degree of power and flexibility beyond that available through the standard administration interfaces. SBM ModScript is accessible from the same contexts as SBM AppScript—you can associate scripts that implement custom features with transitions, notifications, and the self-registration form. You can also set up scripts that run when a user visits a special SBM URL. SBM ModScript is modeled after ChaiScript and contains extensions to support SBM. Programmers can use SBM ModScript to implement custom features in an SBM system.

Now that ModScript is available, questions have come up about the future of AppScript. To help understand what this all means, please review some of the frequently asked questions below.  And feel free to ask additional questions in the comments section. 

So what happens to AppScript?

We here at Micro Focus want to ensure that the transition from AppScript to ModScript is a smooth one, so the two will co-exist in SBM releases for some time.  We want to be sure that ModScript exceeds the capabilities of AppScript before we deprecate AppScript.  AppScript will eventually reach its sunset, but we will give customers advanced notification before that happens.

Do I have to re-write all my App Scripts?

If you want to update your current library of SBM AppScripts, you can use the SBM ModScript conversion utility. Note that this utility is provided on an experimental basis.  It is important to note that the utility provides a way to convert existing SBM AppScripts to SBM ModScript; however, the resultant script does not represent what is considered SBM ModScript that was written with best practices in mind. The utility converts the script into a usable SBM ModScript, but when you begin writing new SBM ModScripts, you do not need to follow the same conventions that resulted in the converted script.

Does this mean support for AppScript is ending in SBM 11.3?

No.  While support for AppScript will eventually end, this would be a future event. AppScript will continue to be supported in releases of SBM that include AppScript until those releases are no longer themselves supported.  By the way, you can see the Product Support Lifecycle Matrix on Micro Focus SupportLine for information on expected end-of-support dates. 

Can I continue to use AppScript in SBM 11.3?

Yes.  While Micro Focus / Serena recommends using ModScript for any new scripts to obtain the most modern and premium experience, organizations may enable and continue to utilize AppScript until such time that it is no longer included in SBM.

Will legacy process apps calling AppScript be affected by this change?

Legacy process apps are expected to continue using AppScript and should function as designed with no modifications required.  There will be no conversion of calls to AppScript to ModScript automatically.  Any changes must be done consciously by a designer.

Will defects in AppScript continue to be addressed?

It is expected that development against AppScript will end with the release of 11.3.  Any non-critical issues encountered with AppScript are not expected to be addressed in patches or to future releases of SBM.

When you say that non-critical issues will not be patched, what defines the difference between a non-critical issue and a critical issue?

A non-critical issue is an issue where business functions are still accessible but may be cosmetically affected or require an inconvenient workaround to operate properly.  Critical issues are those where no workaround is available for a required business function and the business function is not accessible or usable.  While Micro Focus / Serena will work with customers on a case-by-case basis to define the severity of any discovered issue, final characterization is at the discretion of Micro Focus / Serena.

When will AppScript be removed from the product?

At this time, Micro Focus / Serena has not identified a specific release for the removal of AppScript.  When such a release is identified, a Statement of Direction will be issued with more information.  

What resources are available to assist users in transitioning to ModScript?

The best resource is the ModScript Transition Guide in the Documentation Center. You can also ask questions here on Serena Central.


Continue reading
601 Hits

Recent Tweets