If you are in QC/ALM version 11.52 or higher, there is a new BugLinkFactory to assist with the linkage. This makes things ''a little'' easier.

Try the below example:

Function Step_FieldCanChange(FieldName, NewValue)
On Error Resume Next

'If the ST_STATUS field is changing...
If FieldName = ''ST_STATUS'' Then

'If the new value is going to be Failed or Blocked...
If NewValue = ''Failed'' or NewValue = ''Blocked'' Then

'Get the Step ID of the current Step.
StepID = Step_Fields.Field(''ST_ID'').Value

'Get the Step factory from the StepID
Set StepFact = TDConnection.StepFactory

'Get the Step object from the Step Factory
Set StepObj = StepFactory.Item(StepID)

'Get the BugLinkFactory from the Step
Set BugLinkFact = StepObj.BugLinkFactory

'Set a blank filter to find all the current defects in the BugLinkFactory
Set BugLinkFactFilter = BugLinkFact.Filter

'Apply the filter and add the filtered items to a list
Set BugLinkFactList = BugLinkFactFilter.NewList

'Check the list to see if it is empty
If BugLinkFactList.Count = 0 Then

'Inform the user.
MsgBox ''You must link a defect.''

'Block the status change
Step_FieldCanChange = False

'leave
Exit Function

End If

'Kill the objects
Set BugLinkFactList = Nothing
Set BugLinkFactFilter = Nothing
Set BugLinkFact = Nothing
Set StepObj = Nothing
Set StepFact = Nothing

End If
End If

On Error GoTo 0

End Function

you mention linking a defect. Are you wanting to force the user to select an existing defect or create a new defect when step status changes to failed / blocked?

Dear @Jafar, first of all thank you for your interrest.
I would like to force the user to link an defect... The linkage can be done in two ways... By adding it from the new defect button or just create a link with an existing one, but the result is the same... The step would have a link between the failed/blocked step and thr defect. So the answer is: if you select the status blocked ... Check if any linkage exist if not do not allow to change status and revert to old status.

I have done the same for the execution grid and test runs but i was not able to do it for the manual runner.

@jafar, Thank you so much. It worked just perfectly, really appreciate your support.

@jafar do you also have any idea how to force the users to add attachments when raising defects?
I tried different ways but that flag for attachments just doesn't seem to be changing properly. i am on ALM 12.20.

Thank you again!

adip,

I've been down that road before. There just isn't a way to do this. I would recommend opening an Enhancement Request with HP for this to see if they will provide some option in a future release.

failed options:

1) BG_BUG_ID field is not updated until after the defect is created.
- This prevents access to the api for checking the attachments object.

2) BG_ATTACHMENT field is not updated until after the defect is created.
- This prevents a workflow check on the BG_ATTACHMENT field value.

3) The Attachment_* workflow triggers don't fire off in New Defect.
- This prevents setting a flag when the attachments are added.

@Jafar, thank you for confirming the same thing that i encountered, actually i will raise an issue with HP, as we still are under support.

Thanks again for all the support offered.