Adding steps to a task in RMC
I am using RMC 7.5.2.0. I am creating my own method plugin by extending activities and tasks from existing base rup. So at the task level, if I have to change steps, I am able to only add or remove the existing steps, but not able to create new steps of my choice.
So, how can I create new steps of my choice into an extended/ replaced task?
3 answers
Hi Vineetha,
Can please elaborate your question.
How do you extended your tasks and activities ?
Comments
You can add new states by just going into the Process Template and adding new states and actions between those states. No extensions are needed. See the Process Enactment Workshop for some examples of this.
Hi Vineetha,
Uncheck the "Link Method Element" option.
It sounds like you're using Task Descriptors, not extending a Task. A Task Descriptor lives in the Process, which is where time-based actions take place. The Method Description is where you define a task. content in the Method Description is independent of things like iterations.
You'll notice that it's only in the Process area where you can add dependencies between Tasks, Activities, etc. You are actually creating Task Descriptors and adding dependencies between those descriptors.
A Task Descriptor essentially copies the content of a Task into the Task Descriptor. This way you can add time or context-based additions to the task content, such as adding an extra step in the Task Descriptor when that task is performed during a Deployment iteration instead of an Inception iteration.
When you link a Task Descriptor to a method element (in this case a Task), you are saying that you want the Task Descriptor to always look exactly like the Task. Usually, this is what you want when you use a Task. This option was added because otherwise you need to laboriously synchronize your Task Descriptors with your Tasks whenever the Task changes. The assumption here is that if you edited a Task Descriptor, you don't want RMC to automatically overwrite that information just because you changed the corresponding Task. Thus the tedious manual synchronization of Tasks and Task Descriptors.
By selecting "Link Method Element", you've told RMC that you don't want to add anything to that Task Descriptor. That's why it's not letting you add any new steps. Uncheck that option and you should be able to edit the Task Descriptor.
Uncheck the "Link Method Element" option.
It sounds like you're using Task Descriptors, not extending a Task. A Task Descriptor lives in the Process, which is where time-based actions take place. The Method Description is where you define a task. content in the Method Description is independent of things like iterations.
You'll notice that it's only in the Process area where you can add dependencies between Tasks, Activities, etc. You are actually creating Task Descriptors and adding dependencies between those descriptors.
A Task Descriptor essentially copies the content of a Task into the Task Descriptor. This way you can add time or context-based additions to the task content, such as adding an extra step in the Task Descriptor when that task is performed during a Deployment iteration instead of an Inception iteration.
When you link a Task Descriptor to a method element (in this case a Task), you are saying that you want the Task Descriptor to always look exactly like the Task. Usually, this is what you want when you use a Task. This option was added because otherwise you need to laboriously synchronize your Task Descriptors with your Tasks whenever the Task changes. The assumption here is that if you edited a Task Descriptor, you don't want RMC to automatically overwrite that information just because you changed the corresponding Task. Thus the tedious manual synchronization of Tasks and Task Descriptors.
By selecting "Link Method Element", you've told RMC that you don't want to add anything to that Task Descriptor. That's why it's not letting you add any new steps. Uncheck that option and you should be able to edit the Task Descriptor.
Comments
1 vote