is there a way to prevent users from moving requirements to different folders

  • Questions
  • is there a way to prevent users from moving requirements to different folders
Question ID: 107649
0
0

how can i prevent users from moving requirements from one folder to the other?

Marked as spam
Posted by (Questions: 19, Answers: 17)
Asked on May 8, 2017 3:10 am
4 views
Answers (3)
1
Private answer

Hello,

I would think you could block that. Would require some thought as to best method on how you would want to limit the action item.

For requirements and the ''moving'' of items to other folders, that action name is called Requirements.Drag.

Can use workflow such as If ActionName = ''Requirements.Drag'' then...

Then would be followed by whatever criteria you would use as your basis to prevent the action.

You could try something like blocking by user group like this:

If ActionName = ''Requirements.Drag'' then
If user.IsInGroup(''GROUPNAME'') Then
msgbox ''Groupname members cannot move requirements''
ActionCanExecute = False
End If
End If

How you limit this would be up to you. Also would require some thought and possible experimentation as to what sub routine you would best want to add this code to trigger.

Marked as spam
Posted by (Questions: 1, Answers: 116)
Answered on May 8, 2017 6:51 pm
0
Private answer

no sorry requirements.drag not working for me did this work for you ? thanks

Marked as spam
Posted by (Questions: 19, Answers: 17)
Answered on May 12, 2017 8:50 pm
Requirement.drag is the name of the action performed when you move a requirement from one folder to another. The actin is a drag and drop. Your question was that you wanted to block a move to folder, which is a block of the drag action. Code then should be written to stop the action requirement.drag. The example I gave is a sample of code. Not sure what function it would best be used, but would have to experiment if under req_moveto or something else on when to best block.
( at May 12, 2017 8:55 pm)
0
Private answer

ok 100% right here it works i had to place the code under ActionCanExecute now we can freeze fields and prevent users from moving the requirements around curiously i wrote code to see what action name is identified with moving test cases like say testcasedrag and no action was reported by alm. thanks very much. solved

Marked as spam
Posted by (Questions: 19, Answers: 17)
Answered on May 12, 2017 10:18 pm
Glad you got it working.
( at May 14, 2017 1:24 pm)