[Anthill-pro] Using properties as a condition to bypass a step

[emerson cargnin]

It would be good if the preconditions could be included at the step level,
at the "Continuation Condition:", this could also include a scripted option.
PS: by the way, the name "continuation condition" is a bit confusing, as
that is actually a pre-condition, and *"PreCondition:" *is the name used at
the steps list level (when pressing at '+').

regards
Emerson


On 10/04/2008, Uldis Karlovs-Karlovskis <uldisk at ctco.lv> wrote:
>
>  I`ve found an only way to accomplish this by splitting those steps into
> Jobs, so after then You can use Job Precondition scripts.
>
>
>
> Regards,
>
> Uldis, C. T. Co
>
> *uldis.karlovs-karlovskis at ctco.lv* <uldis.karlovs-karlovskis at ctco.lv>
>
>
>
> -----Original Message-----
> *From:* anthill-pro-bounces at lists.urbancode.com [mailto:
> anthill-pro-bounces at lists.urbancode.com] *On Behalf Of *Tyler Andreasen
> *Sent:* ceturtdiena, 2008. gada 10. aprīlī 0:43
> *To:* anthill-pro at lists.urbancode.com
> *Subject:* [Anthill-pro] Using properties as a condition to bypass a step
>
>
>
> I have a job with several tasks.  I want to have a Boolean property (0 or
> 1) such that if set to 0, certain steps in a job will NOT run.  Is there any
> practical way to do this using properties?  Or is there another way.
>
>
>
> Thanks,
>
> T. Andreasen
>
> _______________________________________________
> Anthill-pro mailing list
> Anthill-pro at lists.urbancode.com
> http://lists.urbancode.com/mailman/listinfo/anthill-pro
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.urbancode.com/pipermail/anthill-pro/attachments/20080413/6a3acddb/attachment.htm