Is there a way to set Change Task Asignee / Reviewer with template?

[jbailey]

Version: Windchill 12.0

Use Case: Have a scenario where a Change Notice Template would be useful where specific tasks can be automatically assigned to certain roles or people. (I have WC 12 as the version, but will be migrating to WC 13)

Description:

Looking into creating change notice templates where we know who the assignee (and reviewer) should be for certain (or sometimes all) tasks. There isn't a way in the template to set assignee/reviewer.

[Catalina]

Hi @jbailey,

Thank you for your question!

Your post appears well documented but has not yet received any response. I am replying to raise awareness. Hopefully, another community member will be able to help.

Also, feel free to add any additional information you think might be relevant. It sometimes helps to have screenshots to better understand what you are trying to do.

Best regards,

[Hari_Vara]

Hi,

The Change Task template will have the Assignee and Review, not the Change Notice template. You need to check there to pre-populate.

Cheers

Hari

[jbailey]

@Hari_Vara - The Change Task Template is within the Change Notice Template... and you cannot set assignee/reviewer from there

[Florent@BRP]

Hello,

I suggest implementing CS154668.

However, when you create the ECN template, the system will not allow assignments.

But when your ECN template is created, navigate to each Change Task, and edit the team according to your requirements

Here is an example:

Unfortunately, you can only select users and groups but it is still a finding that made my day.

While writing this response, I found this CS20308 which is more or less what I described.

Florent

[jbailey]

I will have to go back and look at that... I implemented per that CS, but couldnt set on creation of the template, so I didn't go any further - I will look at it again and see if it works for me.

[jbailey]

Florent@BRP ,

After further review- I don't think either of these meet my needs (either by function, or practicality).

In my scenario, I may have multiple tasks per CN (the specific need I would have a dozen change tasks, and EACH task would need a different assignee/reviewer). In this case, I know exactly what member/role that each task should be assigned to. This isn't an activity that happens occasionally either - this type of change would happen 2-3 times a week on different objects. Manually populating the assignee / reviewer on ECN creation would be cumbersome and error prone. Additionally, this isn't the only type of CN that we would be using... and we have over 300 Products in Windchill, each one with their own needs (teams, roles, processes etc).

[Florent@BRP]

You seem to have misunderstood the explanation.  It was not clear enough I guess.

The key point is to edit the team of the change tasks on the ECN template.

Once you created the ECN template, navigate to its implementation plan, and display a change task information page.

From there you can edit its team (on the Process tab) as you need.

Florent

[jbailey]

I tried that, and even after following the CS I still cannot edit in the template.

Jim

[Florent@BRP · Accepted solution]

Hi Jim,

You can edit the template, regardless of the CS. When you are in the Change Templates table, you just have to access the information page of the ECN template by clicking on the "i" icon.

If you don't see the process/team tab on the change task, that means it still uses a basic lifecycle template (this drives the creation of instance/object team)

Florent

[jbailey]

I can get into the editing of the template, it just doesn't give you the ability to change (set) the assignee/reviewer

Jim

[jbailey]

OK I think I missed "on the process tab" 🙂 Let me test again

[jbailey]

Also, usually helps when I am not working on 32 things / working on vacation:-) Thanks!

[jbailey]

So what is interesting here - the fact that you can't assign to a Role in the template(only group and user)... even though the "Multiple Participant Selection" allows you to select a role in the CN itself once created... I would call that a Bug, or in PTC terminology "Works to product specification"