Page tree
Skip to end of metadata
Go to start of metadata

Signature Configurability

A feature was added to allow the ability to configure signature meanings for each level of an Approval Route. This configuration is done per level of a route in the Approval Policy. If the meaning for a level is missing, the default meaning is set to "Approval."

  • Admin users have the ability to configure the meaning of signatures per level in the approval route.

  • The route tasks will retain their meaning even if re-sequenced during route setup. Approval Policy defines route tasks initial meaning and are maintained even if re-sequenced. 

  • When restarting an approval route VERA retains task meaning and continues to sync from prior route for approver and reviewer levels.

This functionality already existed for the "Approval" signature meaning but has been extended to work with any defined meaning in the Approval Policy.

Control Releases on Requirements and Cycles on Test Set Folders

A feature was added to control associating Requirements and Tests Set Folders to a locked release. VERA for ALM can be configured with a user defined field (eq. Locked) to control the ability to associate the Release with a Requirement or the underlying Cycle to a Test Set Folder. 

For example, when the Locked field is not set or set to "N" the Release can be associated or disassociated with Requirements and the Cycles in the Release can be associated or disassociated with Test Set Folders.  When the Locked field is set to "Y" the Release and related Cycles can't be added or removed from Requirement or Test Set Folders. 

This feature does not control or lock the Release or Cycle entities.  Instead this feature controls the ability modify Releases related to Requirements and Test Set Folders.

Figure: Release Manager can lock a release with a user defined field and prevent the release from being associated with Requirements and Test Set Folders

Figure: Release Manager can unlock a release with a user defined field and allow association with Requirements and Test Set Folders

Figure: This integration replaces the native MicroFocus ALM Release and Cycle fields with new VERA for ALM Actions.

Figure: VERA for ALM users Action Menu can be configured with permission to modify releases associated to Requirements and Test Set Folders

Figure: VERA for ALM users can associate one or more unlocked releases to a Requirement and can associate a cycle in an unlocked release to a Test Set Folder

Figure: ALM will display the associated Release and Cycle in the Release and Cycle fields.

See attached Release Notes for more detail


  • No labels