Sub-task Numbering

Use Case:  You are creating a sub-task workflow and you want the numbering to be similar to the parent for ease of identification of the relationship.  For example, if my parent’s number is 000512 then I want my child to be 000512-1, the next child to be 000512-2 and so on. 

Using the field refresh properties and transition actions we can enable this type of numbering, WITHOUT coding. J

Continue reading
118 Hits

How to Embed Submit Forms to Allow Easy Submissions into other Projects and Aux Tables

Let's say you have a relational field on a transition form and you find yourself needing to create multiple new items in the referenced table.  Normally you would need to utilize post transitions or click the little icon beside the relational field (which may not be that obvious to end-users) which would pop-up a new window that displays the submit form for that referenced table.  This may become tedious if you need to submit multiple items which would require you to run multiple post transitions or close the pop-up window after each submission and click the icon again to open a new submit window.

As an alternate solution, which should prove quicker and easier to submit multiple items, you can embed the Submit form directly onto the custom form used by your transition using a Web Page widget.  This will allow the user to directly utilize the submit form of the referenced table/workflow (user privileges permitting) without having to load a pop-up.  Furthermore, you can add a labeled button to your form that will reveal the submit form when clicked and can quickly refresh the widget once a new item has been submitted to reload the submit form again allowing you to quickly create your next item.

In the proceeding example process app, there are a couple relational fields that point to a "Make" and "Model" Aux table designed to store information on various vehicle Makes and Models.  This applied solution will allow us to quickly create additional Make and Model records in the referenced Aux tables and then immediately be able to select them in the relational fields.

The first thing you'll need to do is find the URL that will load the submit form directly.  Please refer to this KB article to find out how:

Once you have found the URL to your submit form (and you have made sure to test it in your browser), you are now ready to add the Web Page widget to a desired place on your your custom form.  You'll also need to add a button to the form which will be programmed to initially load and refresh the widget.

You will need to play with the sizing of the Widget on the form so it will properly accommodate the size of your submit form to your liking.  Auto-sizing may not work well and you may need to define specific pixel heights and widths for the widget.

On the refresh tab of the Property Editor for the Web Page widget, uncheck the "On Page" load checkbox if you don't want to have the submit form load until the button is pressed and then check the "On Click" checkbox and select the button you created in the previous step:

Now we'll need to create proper form actions to hide the Web Page widget(s) when the transition form initially loads, but reveal them when the corresponding button is pressed:


Lastly, if you wish to be able to immediately "refresh" your relational field so you can see your new records after creating them without refreshing the entire transition form, you'll need to make sure your relational field's style setting is set to "Allow searching":

This way, after you are done creating your new records, all you'll need to do to see them in your drop-down is click the search icon in the relational field's search bar:

Once you have configured all this, you are now ready to deploy.  Here is how the transition form looks upon initial load:

Here is how it looks after clicking the buttons that load the Web Page widget:

You can then easily create the new record:

And then immediately select it in my relational field at the top (after refreshing the field with the icon):

Then when you press the "Create New Make" button again, it will immediately reload the submit form which will allow you to create another record.

Should you need to create a massive number of records in any table, please consider using spreadsheets with the Data Import feature in SBM.  You may find out more information in the SBM Application Administrator guide.


Continue reading
94 Hits

Deployment Automation certification is now live

Deployment Automation certification is now live

Do take a look at the new Deployment Automation Certification module and test your knowledge of the building blocks of Deployment Automation.


There are currently five badges, and once these have been earned, you will qualify for the Deployment Automation white belt.


The following is from the DA certification page


Your path to Serena Deployment Automation certification begins by clicking the Get Certified button for the first level, the White Belt. The Each belt is awarded as you achieve the required number of badges, a badge represents a specific area of expertise within the Deployment Automation product or its related eco-systems. To receive a belt you must receive an 80% or higher grade on the related exam to progress. Basically the more badges attained the higher the belt, starting with White Belt, and then moving to Green Belt, and then to Black Belt. Once you have achieved each belt, you will be granted access to a printable certificate. To qualify for certification as SDA Ninja Master, you must have already achieved Black Belt certification and completed a special project that will go through an appraisal process.

Continue reading
89 Hits

"Form action definition is out of date" Simple fix

Recently I decided to modify the SSM - Incident Management workflow in my SBM 11.2 instance. I made the changes I wanted in Composer but when I tried to validate I saw all kinds of issues!

Validation Errors

The error was in several form actions and stated “Form action definition is out of date and needs to be upgraded”. I was unable to deploy the process app! I wanted to fix it but how do you upgrade the form action definition? Luckily it was an easy fix.

Double click the error description and open the form action to edit. Next to the form actions that have issues you will see a refresh icon.

Refresh action

Simply click the refresh icon and click "OK" to close the dialog box. Do this for all the form action errors listed in the Validation Results and you should be able to deploy your process app again.

The errors are due to several new changes in form actions in the latest release 11.2. These changes include a change from ‘rule evaluates to true’ to now ‘rule evaluates to true/false’ as well as a change that consolidates form actions which operated on field and on controls into a single one which operates for both.

Continue reading
217 Hits

How to test GSOAP webservice call

We have all had that issue with the Repository or the Orchestration Engine being unable to get to the gsoap web service URL.  And, this is with all SBM components installed on the same server.  Why can't it get to itself?  Or in the case orchestrations, maybe we cannot figure out why the OE is unable to reach a third party web service.

Continue reading
392 Hits

Dimensions Make

Where to find Dimensions Make downloads? 

Please use this link to access:





Recent comment in this post
Paul Caruana
Great, just what I needed to build a trigger
Tuesday, 23 May 2017 2:02 PM
Continue reading
301 Hits
1 Comment

How to get json listing from SBM JSON Report in SBM 11.1 and above



SBM Aurora (11.1) had introduced authentication with both javascript and json.  The old method of using the embedded report reference link (tmtrack.dll?ReportPage&template=reports%2Fjsonlist.htm&ReportRef=TRM_DEPLOYMENT_PATHS.Deployment.Paths.By.ReleaseType.and.Applications&HasRuntimeParams=1&") does not work.




The current documentation (json_api_guide.pdf) example is not clear on the usage.  Use the new json api




JSON_P1 refers to the display name of the database table

JSON_P2 refers to the Reference Name of the Report (Not Reference Link)

Parameters such as F_TS_RLM_APPLICATIONS are located behind

Recent comment in this post
Linna Landau
Wednesday, 22 March 2017 9:09 AM
Continue reading
497 Hits
1 Comment

Achieving a Continuous Delivery Pipeline


Continuous Delivery (CD) is a software engineering approach in which teams produce software in short cycles, ensuring that the software can be readily released at any time. Continuous Delivery is enabled through a deployment pipeline that breaks down the software delivery process into stages, with each stage verifying the quality of new features from multiple perspectives including the prevention of errors, findings and security vulnerabilities from impacting end users. The pipeline should provide rapid feedback to the team and visibility into the flow of changes to everyone involved in delivering the new features. 


There is typically no such thing as a standard pipeline, in part as applications are very different in terms of architecture, technologies and complexity, but a typical CD pipeline will include the following: build automation and continuous inspection, test automation, and deployment automation.


Build automation and Continuous Inspection

The pipeline starts by automating the building of binaries to create the release deliverables that will be passed to the subsequent stages. New features implemented by the developers are integrated into the central code stream on a continuous basis, built and continuously inspected. This provides the most direct feedback cycle that informs the development team about the health of their application code through evaluating the results of builds, unit tests, source code analysis tests, web vulnerability tests and open source policy violations – automating a configurable continuous inspection toolchain provides rapid feedback to the developers where they need it, and also aggregates metrics to assess readiness for test and deployment automation.


Test Automation

The new version of an application is then rigorously tested to ensure that it meets all desired system qualities, ensuring that functionality, security, performance or compliance — are verified by the pipeline. The stage may involve different types of automated or (initially, at least) manual activities.


Deployment Automation

A deployment is required every time the application is installed in an environment for testing, but the most critical moment for deployment automation is production rollout. Since the preceding stages have verified the overall quality of the system, this can be a low-risk step. The deployment can be staged, with the new version being initially released to a subset of the production environment and monitored before being completely rolled out. The deployment is automated, allowing for the reliable delivery of new functionality to users within minutes, if needed.



The deployment pipeline is usually supported by platform provisioning and system configuration management, allowing teams to create, maintain and tear down complete environments automatically.


Where multiple stages in a deployment pipeline involve collaborative groups who oversee and track the progress though any necessary approvals and delivery, orchestrating the release process provides a high level view of the entire pipeline, supporting the ability to define and control the stages, and monitor insight into the overall software delivery process.



Recommendations for achieving Continuous Delivery


For most organizations it may not be feasible to adopt Continuous Delivery all at once, and a better approach is to focus on identifying the prioritized bottlenecks and improving each of  them in the delivery process as you continue to iterate and measure improvements.


Here’s an example of a Continuous Delivery Pipeline process




Recent Comments
Irwin Menson
Tuesday, 21 March 2017 11:11 AM
Mike Jason
Friday, 24 March 2017 11:11 AM
Continue reading
541 Hits

Important Notification to existing customers of PVCS and Dimensions CM regarding expiring certificates


On 25th February, 2017, certificates that Serena|Micro Focus used to sign Java applets provided by PVCS Version Manager and Dimensions CM expire


When opening the Web client for PVCS and the Web client or Admin console for Dimensions CM, if the Java Runtime Environment (JRE) displays a certificate acceptance dialog, there will be a an additional message on that dialog indicating that the certificate is still valid but has expired, similar to:

The certificate used to identify this application has expired.



To solve this problem, users will need to do one of the following:


  • Users of Dimensions CM 12.2.2,, 14.3.1 or 14.3.2 should install the updated applet files available from KB Doc P2787.
  • Users of VM 8.5.3 should install VM 8.5.3 Patch 004. This patch is available from KB doc P2786.
  • The recommended solution for users of older VM 8.5.x releases is to first install the VM 8.5.3 patch, available from KB doc P2757, then install VM 8.5.3 Patch 004.
  • The recommended solution for users of pre-VM 8.5 releases is to first upgrade to VM 8.5.0, then install the VM 8.5.3 patch and finally install VM 8.5.3 Patch 004.
  • If circumstances prevent you from installing VM 8.5.3 Patch 004, you can use KB doc P2788 to obtain a re-signed applet for VM 8.4.6 ComboHotfix 1 through VM 8.5.2.
  • Until the patch can be installed, you can do one of the following:
    • Add the server URL to the Exception Site List in Java Control Panel (Control Panel -> Java : Security)
    • Press "I accept the risk and want to run this application".


If you have any questions, please contact technical support.


Continue reading
475 Hits

Create a Draft State in SBM - easier than before

A couple of years ago, a colleague of mine wrote a blog about implementing a Draft state in SBM.  This has been a common request and is quite simple to configure.  His blog here outlines how to implement a bonus capability with a specific button to "Save as Draft" instead of the user clicking a check box and then clicking ok.  From a usability standpoint, it is easier on users and flows better.

Since the time of that entry (2015) we have made significant advancements in SBM and now you can implement the functionality described in that article with a form action and not all of that complex JavaScript.  

Continue reading
494 Hits