[Anthill-pro] Promote a build to release candidate / YesNo Workflow

[Damian Karlson]

I've been looking into Yes/No questions and alternative solutions as
well. I'm interested in the answer to Frederic's question too.

Thanks.
D

Damian Karlson
Sr. QA Analyst for IT
4747 McLane Parkway
Temple, TX 76503
Office: (254) 771-7264
Email: Damian.Karlson at McLaneCo.com



-----Original Message-----
From: anthill-pro-bounces at lists.urbancode.com
[mailto:anthill-pro-bounces at lists.urbancode.com] On Behalf Of Frederic
Jean
Sent: Thursday, March 20, 2008 3:38 PM
To: AnthillPro user and support list.
Subject: [Anthill-pro] Promote a build to release candidate / YesNo
Workflow


Let's say i have a workflow that start a  build life, build and create a
package and have a step to start a workflow with a Yes/No question then
notify QA that a release candidate is available and I change de status
to release candidate.

If the QA accept the candidate and click yes , the workflow is processed
, the version is created and everyone is happy...

My problem is when the QA , don't accept the candidate and click no on
the question task... , nothing is executed as he clicked no.

In my case , I have a requirement that when someone reject a candidate,
he needs to write down why. Also when he click no, as the workflow isn't
executed, I can't change the status...

One solution I thought would be that instead I add a Manual Yes/No
Question Task , is I create a Manual Workflow Choice Task with a choice
being Accept and the second choice being Reject so either way a workflow
would run and get the reason of reject as a property and create a
version is the workflow is accept.

What is the best approach, someone have a similar behavior ? 

Thank you
Frederic jean

_______________________________________________
Anthill-pro mailing list
Anthill-pro at lists.urbancode.com
http://lists.urbancode.com/mailman/listinfo/anthill-pro