Serena Blog

The heart of every Serena xChange User Conference is the track session content and its soul the informative presentations. Very often, and after each  presentation is delivered, ongoing conversations and dialog permeate the conference breaks – engaging your peers, Serena product experts and technical support.

The Call for Speakers is currently open through May 30th

Selected speakers receive complimentary registration to the

Read More

Registration for xChange16 is now open. The Early Bird promotions start today and go on through April 30th. If you register now you can save $600. We have an exceptional hotel rate of just $264++/night but those rooms are limited so book early.

The preliminary agenda can be found on the xChange16 site along with details on the optional training day classes we are providing this year. xChange16 runs from Sunday

Read More

Announced this morning. Link to the press release can be found here.

Read More

make.things.betterWe have discussed in previous blog posts the many issues and challenges facing large enterprise IT as it tries to satisfy the demands of the business. The marketplace in this digital economy is rapidly driving business requirements that traditional software practices can’t keep up with.  Today, software is a critical part of business success and the current software practices in most large enterprises cannot react and respond fast enough to add value to the business.

So how do IT executives lead and drive change to deliver the

Read More

Tags: Serena

I am delighted to announce that Serena Software has earned the 2015 Omega NorthFace ScoreBoard Award℠ for achieving excellence in customer satisfaction in the area of Customer Support.

This is the ninth time Serena has won this award and reflects the strong commitment that Serena Support has to customer success. Not only is this a measure of the Support organisation but also of the entire Serena organisation as we work closely with our customers, across all departments. The

Read More

The 2016 Federal User Group meeting will be held on Tuesday and Wednesday April 5th and 6th, 2016. Once again we will be at the wonderful Newseum on Pennsylvania Ave a few steps from the Capital Building. You can register today, there is no cost to attend this event and lunch is included.

Here’s the agenda:

Tuesday, 5th 08:00 am to 5:00 pm – innovation

Read More

SBM App Winners Blog post imageWe recently closed the SBM App-A-Thon contest and would like to thank each and every one of the contest participants, and in particular those that contributed a process application, form extension or plug-in. Thank you!

It is our pleasure to announce

Read More

Tags: SBM, Serena

DevOps bubbleDevOps is not restricted to platforms that are more modern. Many DevOps teams own the responsibility of mainframe deployments as much as they own the non-mainframe ones. Releasing software safely into production has been a critical skillset in the mainframe community for five decades. It

Read More

Tags: Serena

Large enterprises are under pressure from the marketplace to increase business agility. Failing to do so, could impact market share, competitiveness and financial stability. This translates into delivering higher quality software faster. But the complexity of large enterprise IT produces many challenges. Enterprise IT often supports hundreds of applications across different types of systems that are developed using different methodologies by geographically dispersed teams. There is no single delivery pipeline or release process, there are many, often operating at different speeds from manual to automated, and all operating under a mandate of regulatory compliance.

Gartner recommends that these enterprises take

Read More

During the holiday season, oftentimes people get so busy and distracted with our million and one things to do on our lists, we forget to stop and think about the less fortunate. This year I wanted to team together with all Serena employees to make a real and transparent difference. To unite in helping to build a home for a family in need.

We accomplished this through the charity organization, New Story, who funds life-saving homes, turning tent slums into sustainable communities for families living

Read More

Technical blog posts


Relating Records in SBM - Part 2


SBM Blueprint built using version 11.  Download Here ->


In the previous post, well previous…previous post, I introduced the ability to selected related records via the Relational Grid.  Or you could go the old fashioned route and use the relational fields themselves.  Either way is fine, the Relational Grid gives your users a better experience.


The example we will cover this time picks up once I select those related items, how do I go and update the downstream record’s relational field so that regardless of which record I am looking at, I can see the relations.


The short answer is to create an orchestration that sets the relational fields.  Then pretty up the presentation using Relational Grids.


The included blueprint contains two applications.  Primary Relationship Management and Children.  The Primary Relationship Management contains the parent records and the Children the children with the notion of a one (Primary) to many (children) relationship.  In the Primary workflow, there are two transitions.


1.      Create Child – This uses a post transition to create a child record into the Children workflow and establishes the relationship through the post transition properties and setting the relational fields when the child is created.


2.      Adopt Child – This transition allows the user to select one or more children, then when the user clicks OK, an orchestration is run to set the relational fields in both the parent and child records.  All of the forms, and orchestration steps are documented in the blueprint for your reference.


Then for fun, I decided to add orchestration on the Children workflow for them to select parents.  There are two transitions/orchestrations.


1.      Pick My Parent – Uses an asynchronous orchestration to update the parent record with the new child.


2.      SyncPickMyParent - Uses a synchronous orchestration to update the parent record with the new child.


To enhance the visibility you will notice that I have used Relational Grids.  The columns for a Relational Grid are defined with a Composer report.  This gives you a lot of flexibility in what you want to display about the records you are selecting or have selected.  In my opinion they are much more pleasing to the eye than the relational fields themselves.


Also notice that with the Relational Grids you can allow for searching by using the “Other Controls” on the palette.  I chose to have the user click a button to update the search results, you could as easily have the results auto refresh when the other control value changes.  These settings will be in the Results properties of the Relational Grid.


Included below are a couple of screenshots.  You can play around with the default and create more “Grid Styles” if you want to alter the coloring as I have with the purple you see below.


Selection of the available children:

State form with selected children:


Embedded Parent Record in child:
This is configured by setting the URL for the parent record in a field and then rendering that field in a webpage widget on the form.



Tags: SBM

We are initiating a quarterly SBM Virtual User Group webcast and I very much hope that many of you will  join, engage and ultimately participate topics and agenda items as we move forward. While Serena Central is a great place to hang out, we want to ensure in addition to the on-line forums, the SBM user community has an opportunity to come together to hear latest about latest product news and events, and to hear or watch topics of most interest from R&D, from Technical support and from Customers like you who may have a great story or great process application or use of SBM to share. Ultimately, the VUG will be administered by the Product team but we welcome topic ideas from our SBM User community.


Please join us for the initial SBM Spring 2016 VUG on May 16th where we will share some product news, share a few details on Serena xChange16, hear from our technical support leaders on exploiting the strengths of SBM notifications and e-mail responses and respond to your questions.

Tags: SBM

This blog is a continuation of Implementing Release Control Across Multiple Product Groups, where I discussed how to create and configure different projects for each of the product groups. This blog dives into the details of modifying a process app to create a duplicate workflow.

IMPORTANT: Creating a duplicate workflow is not necessary, and it is recommended that you use the same workflow or sub-workflows, if possible. Sometimes, one product group requires a lot of customization to a workflow. In this case, it may be easiest to duplicate the default workflow and then make your modifications to the duplicate workflow. You will have an issue in that with upgrades, you will need to merge any new features into your customized workflow.

The following procedure explains how to create the duplicate workflow and what modifications need to be made to the rules, orchestrations, and forms in order to use this new workflow. The duplicate workflow will have new states and transitions, and these must be added to the rules, forms, and orchestrations.

The following steps walks you through the changes and modifications that you would need to make to your Release Package application in order to use a new duplicate workflow.

  1. In Serena Composer, open the Release Package process app.
  2. Create a duplicate of the workflow by selecting the default RLC - Release Package workflow and choosing Duplicate from the right-click menu.
  3. Select the duplicate workflow and delete the Submit from Release Train transition. Note this is a workaround for posting into projects with different workflows from the same workflow. The post transition in Release Train, Create Release Package will use the other default transition to submit.
  4. Under the Rules section, modify the following rules to add the states from the new workflow. They will have the same name as the existing states:
    • Return to Dev Rule
    • Is Current Environment Optional
    • Allow component version editing
  5. Under the Forms section, modify the forms and the form actions to include the new states and transitions. See Updating Release Package Forms for details.
  6. Under the Orchestration Workflows section, you need to modify the orchestrations to point to the correct update transition in the new workflow. See Updating Orchestrations for details.
  7. Save and deploy the Release Package process app.
  8. If using Release Trains across the different product groups, see Updating RLC - Release Train for information on how to modify release trains to work with the new 


Updating the Release Package Forms

 When you have created a duplicated workflow, there are two main modifications that you need to make to the forms:

  • Transition Buttons - Map transitions in the new workflow to the existing buttons.
  • Form Actions - Modify the actions to include the states from the new workflow.

For example, on the Master State Form for the Release Package, you would select the PrimaryTransitionButton and choose to Add the new transitions. In the following screenshot the Deliver transition has been added from the RLC - DC Release Package workflow.

In addition, you would select the Actions tab for the Master State Form, and modify the form actions to include the new states. In the following screenshot, we are adding the Acceptance and Construction states to the If statement under the Form Load: Set State Panel form action.

You need to repeat the edits for the transition buttons and form actions listed below:

Release Package Forms

Master State Form
                PrimaryTransitionButton - needs additional workflow transitions
                SecondaryTransitionButton - needs addition workflow transitions
                UpdateDeploymentUnitsButton - needs additional workflow transition
                EditDeploymentUnitsButton - needs additional workflow transition
                ValidateTaskCollButton - needs additional workflow transition
                EditTaskCollButton - needs additional workflow transition
                updateRequestButton - needs additional workflow transition
                AssociateBRButton2 - needs additional workflow transition
                    Form Load: Set State Panel - needs additional workflow states
                    Form Load Set State Icon - needs additional workflow states
                    Form Load: Add warning about restricted environments - needs additional workflow states
                    Form Load: Closed Message - needs additional workflow state

Child State Form
                PrimaryTransitionButton - needs additional workflow transitions
                SecondaryTransitionButton - needs addition workflow transitions
                UpdateDeploymentUnitsButton - needs additional workflow transition
                EditDeploymentUnitsButton - needs additional workflow transition
                ValidateTaskCollButton - needs additional workflow transition
                EditTaskCollButton - needs additional workflow transition
                updateRequestButton - needs additional workflow transition
                AssociateBRButton2 - needs additional workflow transition
                    Form Load: Set State Panel - needs additional workflow state

Master Transition Form
                    Form Submit: Set System Log Message in Edit Component Transition - needs additional workflow transition

Notes Transition Form
                    Form Load: Unlink Help Text - needs additional workflow transition
                    Form Load: Closer Warning - needs additional workflow transition

Deployment Unit Edit Transition Form
                    Form Submit: Set System Log Message in Edit Component Transition - needs additional workflow transition

Submit Transition Form
                    Form Load: Show Release Team if No Invalid Value in Submit from RT - needs additional workflow transition

Deployment Path Forms

Master State Form
                PrimaryTransitionButton - needs additional workflow transitions
                AddEnvironmentBttn - needs additional workflow transition
                    Form Load: Set State Panel - needs additional workflow states

Master Transition Form
                    Form Load: Show Sections if on Certain Transition - needs additional workflow transition
                    Form Load: Hide Fields  if in Return To Construction Transition - needs additional workflow transition
                    Form Load: Allow delete - needs additional workflow transition


Updating Orchestrations

 In order to use the new workflow, you will need to update the RLC Service Orchestrations to use the System Update transition in the new workflow. The orchestrations are hard-coded to use the existing System Update transition (TURNOVER.SYSTEM_UPDATE) which doesn't exist in the new workflow. 

Here is what you can do to fix this issue after you have duplicated the workflow. Note that creating a duplicate workflow causes each orchestration to have 2 event maps: 

  1. Duplicate each of the orchestration workflows mentioned below.
  2. For each ORIGINAL orchestration, such as "UpdateChildren", "StartDeploy", etc.:
                a. Remove the event map for which the "Event type" references the NEW workflow (skip "Alf..." orchestrations)
  3. For each NEW (e.g., "UpdateChildren2", "StartDeploy2", etc.):
                a. Remove the event map for which the "Event type" references the ORIGINAL workflow (skip "Alf..." orchestrations)
                b. Update each service step listed below, adjusting the internal transition name from the ORIGINAL value ("TURNOVER.SYSTEM_UPDATE") to the NEW internal transition name (e.g., "NEWWORKFLOWNAME.SYSTEM_UPDATE")

Orchestrations to Update

            UpdateParent step - transition hard-coded to original workflow
            UpdateChild step - transition hard-coded to original workflow
            ClearTechField step - transition hard-coded to original workflow
            validateParent step - transition hard-coded to original workflow
            validateChild step - transition hard-coded to original workflow
            AddChildToParent step - transition hard-coded to original workflow
            validateParent step - transition hard-coded to original workflow
            validateChild step - transition hard-coded to original workflow
            AddLastExecutionAndLog step - transition hard-coded to original workflow
            clearParent step - transition hard-coded to original workflow
            clearChild step - transition hard-coded to original workflow
            sbmappservices72_TransitionItem step - transition hard-coded to original workflow
            sbmappservices72_TransitionItem step - transition hard-coded to original workflow
            ClearRP step - transition hard-coded to original workflow

Updating RLC - Release Train

This topic assumes that you are not duplicating the Release Train workflow. Even though the change was to create a duplicate workflow for Release Package, you will need to make updates to the Release Train process app in order to use this new workflow. This is required since the duplicate Release Package workflow has new transition names and two projects to choose from during post transitions. 

The following updates must be performed to the RLC - Release Train application:

  1. Open the Release Train process app in Serena Composer. 
  2. In the workflow, modify the Create Release Package transition to point to default Submit transition.
  3. For the LinkReleasePackage orchestration, under Release Train Sync Orchestration, you will need to change the UpdateRp step. It is hard-coded to the original workflow. To fix it, remove the internalName value and update the displayName value to "System Update" without quotes.
  4. Deploy the changes.
  5. In Application Administrator, modify the Create Release Package transition in the Release Train projects to set the appropriate Release Package project to post into. For example, if you have two release train projects - one for Group A and one for Group B - you would set the Create Release Package transition to post into Group A's release packages project and Group B's release packages project, respectively.

 Troubleshooting Release Train

If the post transition does not display the correct submit form into Release Package, make sure that you have chosen the default submit transition for the Create Release Package transition.


Tags: SBM

In SBM, it is sometimes necessary to find out all users that have a specific privilege. This can be done easily by directly querying the database.  I referenced the SBM Schema guide for this information.

Privileges are stored in the TS_PRIVILEGES table.  A user will have multiple records depending privilege type.  To see what all the privilege types mean, please reference the SBM Schema guide.  Use the steps below to determine how to identify users that have a given privilege.

Tags: SBM

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


Tags: SBM

I have written a JavaScript a long time ago using the fancytree framework to display SBM items in a tree structure. Furthermore, the sequence of the items, can be modified in this tree.

Basically, the fancytree is a JavaScript tree view plugin for jQuery with support for persistence, keyboard, checkboxes, tables, drag'n'drop, and lazy loading. I implemented this tree on a form using a HTMLJavaScriptWidget (see screenshot). In the "Content" section of the HTMLJavaScriptWidget, I defined a div section with the id="tree" to determine the place where the fancytree should appear.

Tags: SBM

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.

Tags: Release Manager/Release Control

Wireshark is often the preferred method of doing network captures. However, what if security posture will not allow installing Wireshark on a production server? In this case, we can use the NETSH TRACE command built into Windows. This command works on all Windows machines both client and server.

Tags: SBM

I was doing a little research today and stumbled across a new feature in SBM 11 that I thought should get a little extra attention.  It is small, but has a lot of impact if you have been in the situation of have a browser tab with Prod open and the next browser tab has Dev open and you are tweaking a workflow and testing changes and then getting frustrated when you are not seeing them, only to find out that you were looking at Prod. 

Wouldn't it be nice to have a bit red flag to let you know you are not in Prod?  This feature does just that.  I suspect you will not include the banners on your production system, but any other development or test SBM instances would be a great place to make this change.  It does require a database row modification and a template modification, but the level of effort is minimal.

This enhancement is referenced in the ReadMe and here is a link to the KB article for instructions:

My image below shows how this is represented via the Work Center.  Banners are also visible in the classic UI, Admin and App Repository.  By default the background is light blue, however you can change the HTML so that it jumps out at you as I have in the image below.



Tags: SBM

So you've just upgraded to SBM 11. You log into Work Center and everything looks shiny and new! You go to composer and you get an error!

Composer Error


What do you do? Fortunately there is a fix for this known defect DEF262557. The issue has to do with the maximum TCP packet size in Load Balancer. The default is set at 8kb in the Apache HTTP server when it needs to be 16kb for SBM 11.

To change this go to Configurator and under Tomcat Server click the Advanced Settings button.


The following box opens. Check the box next to Overide the maximum HTTP header size for SBM Tomcat requests and responses. Type in the new value in the header size field (16,384) and click ok. Apply the settings and close Configurator. Now when you connect with Composer it should work. No more error!

Advanced Settings

Tags: SBM


Registration for Serena xChange16 is now open. The Early Bird promotions run through May 30th and I would encourage early registration.

The preliminary agenda can be found on the xChange16 website along with details on the optional training day classes we are providing this year. Please be sure to check out the Agenda and the 1 day Training classes that will be held on Sunday, September 18th. xChange16 runs from Sunday 18th September with our traditional welcome reception, through Wednesday September 21st. Customer Advisory Board Meetings will be held on Thursday, September 22nd.

This year we are back in Chicago at the newly renovated Renaissance Hotel on Wacker Drive, a terrific conference location. We very much look forward to helping our customers get the most value out of their Serena investments, with presentations and workshops featuring outstanding thought leaders, technical experts, customer champions and technology partners.

As a reminder, the Call for Speakers is open through May 30th, and if selected we are waiving the conference fee! This is a great opportunity for customers to contribute to what makes the conference so special – sharing experiences with your peers and as always, the best customer presentations will be shortlisted for a Serena Innovation Award.

I have overall Track responsibility and will be coordinating the Track content with the Track Leaders:

Business and IT processes with SBM: how you have used Serena's SBM platform to improve efficiency and effectiveness of your IT and Line-of-business processes - Dave Easter

ALM solutions with Dimensions RM & CM: how you have used Serena solutions to plan, define and develop applications, support development practices, and deliver quality deliverables - Don Irvine

Change, Release and Deployment: how you have used Serena solutions to automate release and deployment of applications - Julian Fish

ALM solutions with ChangeMan ZMF: your opportunity to show how you use Serena Mainframe solutions in your business - Al Slovacek

Enterprise DevOps: perspectives and insights on Agile and DevOps best practices - Mark Levy

We very much encourage speaker submissions which must be received by May 30th. Selected speakers will be notified in early June and their conference fee waived or refunded.

As always, we appreciate your feedback and engagement as we gear up for Serena xChange16 and look forward to seeing many of you there.


Tags: SBM

When you purchase Serena Service Manager and Serena Request Center, you gain the ability to have SLAs assigned. As part of that functionality, we provide some metrics around that data.

Some customers have purchased Serena Request Center and are not using our Request process applications, choosing to use their own and simply using the Request Center for a Service Catalog. These customers oftentimes do not want to have those SLA reports available to their users in the Serena Work Center.

Those reports are driven by SWC_MENUITEM table in the SBM database. In order to remove those reports from Work Center, you can run the following query:

WHERE TS_TYPE in (19,20)

After running this query against the SBM database, you will note that those SLA Reports have now been removed from the navigation pane.

I hope this article helped you remove those SLA reports from the navigation pane in those instances where you are not intending to use them.

Tags: SBM

Hi All,

We are trying to build an integration with Remedy using web services.

We have got it working for the most part.

The calls are tested and working from SoapUI.

We have an issue when trying to call from SBM. Our original issue was due to the WSDL. The Remedy web service requires header information (username/password token via WS-Security) which is required by the web service, but is not defined within the WSDL. We have now customised the WSDL to contain these fields and the WSDL imports correctly into SBM to allow us to map these fields.

When calling the web service, Remedy rejects this due to the format of the XML payload. SBM is adding additional elements (the name of the orchestration), which wraps the header components. A sample of the XML below. How do we remove these additional SBM elements/tags that are added to the XML being sent? They cannot be deleted within the Composer. The tags are highlighted below "RemedyTestService_executeProcess_Envelope".

Normal 0 false false false EN-ZA X-NONE X-NONE MicrosoftInternetExplorer4

<env:Envelope xmlns:env='' xmlns:xsd=''><env:Header><RemedyTestService_executeProcess_Envelope xmlns='' xmlns:bpws='' xmlns:defaultNS='' xmlns:defaultNS1='' xmlns:ns8=''>

              <ns9:Security xmlns:defaultNS='' xmlns:defaultNS1='' xmlns:ns9=''>

                <ns9:UsernameToken xmlns:defaultNS='' xmlns:defaultNS1=''>

                  <ns9:Username xmlns:defaultNS='' xmlns:defaultNS1=''>SBM</ns9:Username>

                  <ns9:Password xmlns:defaultNS='' xmlns:defaultNS1=''>sbmtoremedy</ns9:Password>



            </RemedyTestService_executeProcess_Envelope></env:Header><env:Body><defaultNS1:executeProcess xmlns:bpws='' xmlns:defaultNS='' xmlns:defaultNS1='' xmlns:ns10=''><ns10:gridName>GRID1</ns10:gridName><ns10:processName>:SBSA-OA-SBM_Integration:Submit</ns10:processName><ns10:parameters><ns10:Input><ns10:Parameter><ns10:Name>INP_EmployeeNumber</ns10:Name><ns10:Value ns10:type='Text'><ns10:Text>A186617</ns10:Text></ns10:Value></ns10:Parameter><ns10:Parameter><ns10:Name>INP_RequestDetail</ns10:Name><ns10:Value ns10:type='Text'><ns10:Text>Testing</ns10:Text></ns10:Value></ns10:Parameter><ns10:Parameter><ns10:Name>INP_ExternalReference</ns10:Name><ns10:Value ns10:type='Text'><ns10:Text>9389280</ns10:Text></ns10:Value></ns10:Parameter></ns10:Input></ns10:parameters></defaultNS1:executeProcess></env:Body></env:Envelope>HTTP/1.1 500 Internal Server Error


Tags: SBM

SDA: Understanding process JOIN

SDA utilizes a graph-based system to represent the steps in a deployment process.  This allows the creation of some complex deployments with a drag and drop interface.  Within a process, there are times when we must connect one process step to another.  These connections are represented within the graphical tool with a directional flow (or an arrow).  Whenever a process step has 2 or more inbound connections, we have created a join.   To be effective at process development, we need to understand the implications of several types of join operations.  We may need to understand when the process step will run, if the step will run when some inputs (or inbound connections) are missing, or if the status (success or failure) of an inbound connection will have any effect on whether the step will run?

Some Definitions

In the following descriptions, a connection is invalid if the parent step runs but the outbound connection is not used.  Therefore any process step that succeeds, the outbound connections marked with the green check or the grey circle for both are valid.  If the step succeeds only outbound connections marked with the red check mark will be invalid.

Further, a connection is not needed if the parent step does not run.  In the following example, let’s assume that the tomcat version installed on this resource is tomcat 8.  The first step depicted, is the switch set to check the version.  After this, the flow followed would be down the left-hand side of the graph.  The center and right-hand outbound connections from the Switch are now Invalid.  This is because the parent step executed, but the connection is not followed.  Further down, the outbound step from “Check Tomcat 7 Online” is not needed.  The parent step was not executed, therefore the remainder of this execution path is not needed.

Types of Joins


In the case of an Explicit join, the process step named Join is utilized.  All inbound connection paths must be valid.  In the example below, the Join will only be executed in cases when the “Check Win or Unux” switch step resolves to “Win”.  In all other cases, the outbound connection from that process step is not valid and therefore, the join will fail and no further execution along that path will be undertaken.  Also the process steps “Check Free Diskspace” and “Check Privs” must also have a SUCCESS status as written in order for the Join to execute and continue execution.

The Join step may also accept inbound connections of fail status so long as the appropriate connection is marked with the fail or both conditional flag (meaning instead of the green check mark, it has a red mark or a grey open circle).

Implicit Joins

An implicit join can be made with any process step that is not a join.  The implicit join occurs whenever a process step has more than one inbound connection.  The process step with the implicit join will not execute until all input connections can be evaluated as to status and validity.  A process step with an implicit join will execute if the following are true: 

  • All inbound connections are valid (invalid connections will cause the join to fail, not needed connections are acceptable).
  • The status from the previous step on the connection must match the flag on the connection.  Therefore, a connection with a green check mark must have a status of success.  A connection with a status of failure will match a red mark or a grey “both” circle on the connection diagram.
Tags: SDA/Deployment Automation

14.2 release brings changes in UI to refresh and modernize desktop client look. Multiple places were changed: main views, navigation panels, dialogs and toolbars.

One of the most used views is probably Folders and Items. In 14.2 the view has flat and Zen look – there are no borders with 3D edges, the grid and its header are flat and have thin one pixel separators, new icons were designed for folder and item and other control elements on the view.

Tags: Dimensions CM

As we approach the release date for ChangeMan ZMF 8.1.1,  here is a screen print of a complete list of the HLLX Exits available in this new release..


 We would like to solicit input from the user base as to what HLLX exits should be considered next for inclusion in the product. 

One area that we feel should be looked at is ERO and we would like to get feedback on that.


Tags: ChangeMan ZMF/Mainframe

As of RLC6.0 the Release Train application contains a mechanism to make scheduling easier. The tool can be used in many ways which will be broken down here.


Tags: Release Manager/Release Control

Sometimes it’d be nice not to have to move to the standard transition bar to perform a transition on some information that’s relevant to where the user currently is on the form. Luckily, this type of button manipulation can easily be done and it doesn’t take a wizard to do it!

Tags: SBM

Use the attached form extension in Composer with versions of SBM 10.1.5+ to show a drop down list of all available transitions for the current state. When you select a transition in the list it is then executed. You can choose at design time whether the transition list is shown in alphabetical order or the default order dictated by the workflow.

Tags: SBM

Changesets were first introduced in CM 14.1. Changesets enable you to view changes to streams, projects, and folders and get information such as: who made the change, which request was used, and what comments made at the time of delivery.

In CM 14.1, Changesets included a set of filters to limit the information displayed. Text filters allowed you to pick an attribute and display changes that match a specific value. Date filters allowed you to choose a date range.
CM 14.2 adds two filtering options: Version and Changeset Type.

Tags: Dimensions CM