[Anthill-pro] Re: suggestion for project, workflows and jobs hierarquies

[emerson cargnin]

Another way to help with this it would be to have project templates.
I'm doing it now, but even using job libraries and workflow
definitions it still needs a lot of of after copying the project to
create a new one. I though of using some kind of place holders in the
template, like @{PROJECT_NAME} that would be replaced when the
template is copied to a concrete project. So when the user chooses to
use the template, it could have an initial page asking to fill up
those properties that would be used when copying the the template into
a new concrete project.

what do you think?
Emerson

On 08/04/2008, emerson cargnin <echofloripa.yell at gmail.com> wrote:
> What about if we could have hierarchies of projects, workflows and jobs??
> Let me exemplify:
>
> I have an abstract master project, this has stamping strategies,
> triggers settings and a couple of properties set.
>
> I could then inherit it and add more information or override it.
> At the momment we have job library and workflow definiiton library.
> But we can't extend or override the job, and the workflow lib has only
> the definition.
>
> Is it something that was thought already and excluded for some reason?
>
> thanks
> emerson
>