02-29-2012 12:26 AM
We are involved in ChM module implementation in SM 7.11.
We have specific change category (Requirement) with two phases (Logging and Build phase). In both phases are automatically generated tasks (without condition).
The phases have marked "When is last task closes -> close this phase" in the Model/Task tab.
When we create the change and going to change the auto open logging phase tasks are getting generated. This is working fine. Then, when we close these tasks, the change automatically moves to the next phase: build phase.
At this phase, it should create auto open task but in this case they are not created.
We don´t know why they are not created…
What is the problem?
Many thanks in advance.
02-29-2012 11:51 AM
The problem is that in several releases, the option to auto-create tasks as a background process does not work.
When you explicity close the earlier phase, the auto-open tasks function is called as a result of the foreground process of you closing the previous phase and starting the new phase.
However, the "Close phase when tasks complete" process is a background closure, so the auto-open tasks process does not invoke as expected.
As a workaround, you could update the previous phase to:
- "Change the status of the change to XXXXXX" when all tasks are complete,
- Notifiy the change coordinator when the change status is changed to XXXXXX that they can close the phase.
- When they close the phase, the tasks will auto-create.
04-09-2012 07:41 AM
04-10-2012 12:22 PM
04-20-2012 11:20 AM
04-21-2012 01:45 AM
I have everywhere Backgroud Open set to false and the tasks open without any prompt to save them. Also on automatic closure of previous phase the tasks are being created. If i try setting this value to true the same stops happening.
So in your case also, u may try setting Background Open to False