thanks for raising your follow-up question. It illustrates the use-case you've in mind. The application behaves as follows: if you're adding new Tasks to a Task List in status Paused, then it's not automatically added to the template. If you're adding a new Task to a Template, that it only materialized in newly generated Task Lists. As long as the generated or released Task List is not yet active, you could avoid a double maintenance if you set the Task List status to obsolete, maintain the Template and generate the Task List again.
To me it seems that your use case is suggesting a kind of governance cycle of your closing template: if any user affected by or involved in the closing process needs an additional task to be processed in already ongoing closing cycles, he should be able to request it (possibly already providing more or less detailed task attributes). And this request should somehow be taken into account both for the template (i.e. future task lists) and the ongoing closing cycle. Is that what you are having in mind?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.