It's all about the answers!

Ask a question
QuestionsTagsUsersBadges
Guidelines | FAQ
Follow this question
Question details

×12,008
×10,962
×1,381
×11

question asked: Aug 14 '13, 12:49 p.m.
question was seen: 5,724 times
last updated: Aug 27 '13, 2:43 p.m.

Related questions

How can we automatically prevent prior approvals from being accepted to re-approve test artifacts?

0
Paul Spalitta (81●4●30●37) | asked Aug 14 '13, 12:49 p.m.
retagged Aug 27 '13, 2:43 p.m. by Ralph Earle (257●3●9)
An artifact can be moved back to Draft, modified and moved to Approved state without requiring another Approval Group in Formal Review. Does anyone know of a method for preventing this workflow?

Here is the workflow spelled-out in steps:
1. Create Test Script.
2. Add Approval group to Formal Review.
3. Approve Formal Review.
4. Transition Test Script to Under Review and then to Approved state.
5. Transition Test Script to Draft state.
6. Modify Test Script and Save.
7. Transition Test Script to Under Review and then to Approved state.
ERROR: Another Formal Review Approval Group should have been required before allowing transition to Approved in Step #7.

One answer

Most liked answers ↑|Newest answers|Oldest answers

0
permanent link
William Chen (312●1●5) | answered Aug 15 '13, 5:19 p.m.
Hi Paul,

I would suggest you to check out the Defining preconditions and follow-up actions:

http://pic.dhe.ibm.com/infocenter/clmhelp/v4r0m3/index.jsp?re=1&topic=/com.ibm.rational.test.qm.doc/topics/t_ovw_def_preconditions.html&scope=null

Cheers,
Will

Your answer

Register or to post your answer.


Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.