Welcome Serena Central users! CLICK HERE
The migration of the Serena Central community is currently underway. Be sure to read THIS MESSAGE to get your new login set up to access your account.
Trusted Contributor.. bton99 Trusted Contributor..
Trusted Contributor..

Workflow code in Manual Runner Module is unreliable


I have a query about workflow code within the Manual Runner module in HPALM. We use quite a lot of customization within HPALM across all modules, and are pretty experienced with it. However the behaviour of the Manual Runner module appears quite flaky.

What We want to do is pretty simple:  For manual test runs, when the user clicks on End Run we want to update a couple of User fields on the test run – e.g. RN_USER_01 should say “Not Confirmed” until the run has been reviewed. Another field gets the TIME that the run ended, etc. ( so we do want it to happen at end of run.)

To start with, based on the Active Module, we re-direct the Common ActionCanExecute checks into the individual module scripts, So we have a ManualRunner_ActionCanExecute function.

When you click to end a run, the main action is act_end_run, this actually triggers several other actions, and even gets triggered twice itself, but we have resolved that.

Our problem is that  - for the same user workflow - sometimes our run Fields are updated and other times they are not. So the essential question for this forum is “has anybody else had issues with reliability of setting run field values in workflow?”

The following snippet of code is what we are using. It is s simplified for this demo, but even like this we have a problem.


Function ManualRun_ActionCanExecute(ActionName)
On Error Resume Next
'Msgbox 1	
Msgbox ActionName

'Msgbox 2	
Msgbox Run_Fields.Field("RN_USER_01").Value		'(the value should be blank.)

.... 'Some other code 

Select Case ActionName
      .....' other code for other Actions.
       Case "StepsView.EndRun", "RunView.EndRun"    'these get triggered after act_end_run
             	Run_Fields.Field("RN_USER_01").Value = "Not Confirmed"

'Msgbox 3	
Msgbox Run_Fields.Field("RN_USER_01").Value	   '(the value should be " Not Confirmed ".)
End Select

On Error GoTo 0
End Function


The problem is that even when the ActionName is shown (in Msgbox1) as "StepsView.EndRun, SOMETIMES the field is updated correctly on the run AND msgbox3 does show “NOT CONFIRMED”,

and SOMETIMES, the value is blank – both in msgbox3 AND in the run field.

This is for the same manual workflow and conditions, it just appears to be unreliable

Any suggestions?


3 Replies
Absent Member.. Alonso_S_QC Absent Member..
Absent Member..

Re: Workflow code in Manual Runner Module is unreliable

Hello Bton99,


Thank you for using HPE Forums.


Regarding the issue, I would like to ask you some questions regarding this:


What is the version of ALM and the patch level?

Is this happening with all the users ?

If you use the workflow in another project so you have the same behavior ?

Do you have this behavior only in Manual Runner ?


We will be waiting for your reply.



Alonso Sequeira Morales
SW Support Technical Consultant
San Jose, Costa Rica
Hewlett Packard Enterprise

If you find that this or any other post resolves your issue, please be sure to mark it as an accepted solution.
If you are satisfied with anyone’s response please remember to give them a KUDOS by clicking on the STAR at the bottom left of the post and show your appreciation”
Trusted Contributor.. bton99 Trusted Contributor..
Trusted Contributor..

Re: Workflow code in Manual Runner Module is unreliable

Hi Alonso,
Thanks for your reply - I did try to respond earlier but got a message saying the "Forum is closed for maintenance".

We are still using HP Enterprise (ALM) V 11.0 with Patch 19.

This happens on both our DEV server and on our live server, across several projects.
It happens with all users, across various user-groups (although the permissions for running tests are the same in all groups)

We have quite alot of workflow customization across all modules and it is only with Manual Runner we have a problem.
In the projects where this is being tested we see approx 40% of the time it works and 60% it doesn't, possibly more 30/70.
And thats for exactly the same workflow/button clicks that we use.

Just by flagging/msgboxing all of the actions between test lab and manual runner it appears to be a very convoluted hand-
off between them and also between manual runner and its sub-views.
For example just for End-Run, LOTS of actions get triggered, and several of them get triggered more than once. I believe we have accounted for that, but to be honest it looks a pretty crazy workflow.

Any suggestions appreciated.

Absent Member.. yanjuansu Absent Member..
Absent Member..

Re: Workflow code in Manual Runner Module is unreliable

Hello, Just want to say, we met the similar issue for End Run event trigger.

Our workaround is instead of trigger event for End Run action, I use Run_CanPost or AfterPost functions.

The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.