Given this limited information, my guess is you need one.

Kai
Jazz Process team

gdang wrote:

In CQ, I have custom record types with different workflows, actions,
and application hook logic. I need to be able to create these in
RTC/Jazz. Does this mean that I need to create one custom process
template or mulitple process templates?

You can apply a process template to different projects. And you still can customize the process after applied to a project.
You also can save a process as a new template.

If you like to have a process template that mappes your CQ Schema then you should change the same process template corresponding your changes in the CQ Schema.

I hope that somebody else can give you an example how to add a WI of type defect corresponding the out of the box CQ record type.

/Elisabeth

Gary,

If I understand your question, you'll only need one custom process template to define your different work item types corresponding to your CQ record types. Please refer to the Work Item Customization topic in the Learn section of jazz.net, https://jazz.net/learn/LearnItem.jsp?href=content/docs/work-items/index.html. I'll put together an example of how you would specify a workflow for a custom work item type for the out-of-the-box CQ defect record type, but it will not be complete but hopefully give you an idea of what you would need to do. I don't know how the hooks would translate to the process spec. Hopefully someone else can help you with that.

Lorelei Ngooi
Jazz CQ Connector Team

Here's a simple example of what you would need to put in the process spec to create a custom work item type that resembles the CQ Defect record type from the out-of-the-box DefectTracking schema.

First, define a custom work item type cqDefect.

<configuration-data id="com.ibm.team.workitem.configuration.workItemTypes" xmlns="http://com.ibm.team.workitem/workitemTypes">
<type id="com.ibm.team.workitem.extension.workItemType.cqDefect"
category="com.ibm.team.workitem.workItemType.cqDefect" name="CQ Defect">
</type>
</configuration-data>

Then, define the custom workflow.

<configuration-data id="com.ibm.team.workitem.configuration.workflow"
xmlns="http://com.ibm.team.workitem/workflow">
<workflowDefinition
id="com.ibm.team.workitem.cqDefectWorkflow">
<workflow
name="CQ Defect Workflow"
startActionId="Submit">

<resolution id="r0" name="Unresolved"/>
<resolution id="r1" name="Fixed"/>
<resolution id="r2" name="Fixed Indirectly/>
<resolution id="r3" name="Functions As Designed/>

<action id="Submit" state="s10" name="Submit"/>
<action id="Assign" state="s11" name="Assign"/>
<action id="Open" state="s12" name="Open"/>
<action id="Resolve" state="s13" name="Resolve"/>
<resolution id="r1"/>
<resolution id="r2"/>
<resolution id="r3"/>

<action id="Validate" state="s14" name="Validate"/>
<action id="Close" state="s14" name="Close/>
<state id="s10" group="open" name="Submitted">
<action id="Assign" />
<action id="Close" />
</state>
<state id="s11" group="open" name="Assigned">
<action id="Open" />
<action id="Close" />
</state>
<state id="s12" group="closed" name="Opened">
<action id="Resolve" />
</state>
<state id="s13" group="closed" name="Resolved">
<action id="Validate" />
</state>
<state id="s14" group="closed" name="Resolved">
<action id="Validate" />
</state>
</workflow>
</workflowDefinition>
</configuration-data>

Finally, link the custom workflow to the work item type.

<configuration-data id="com.ibm.team.workitem.configuration.workflowBinding"
xmlns="http://com.ibm.team.workitem/workflowBinding">
<workItemCategoryBinding
workItemCategoryId="com.ibm.team.workitem.workItemType.cqDefect"
workflowId="com.ibm.team.workitem.cqDefectWorkflow" />
</configuration-data>

Hope that helps.

Lorelei Ngooi
Jazz CQ Connector Team