Community Tip - Visit the PTCooler (the community lounge) to get to know your fellow community members and check out some of Dale's Friday Humor posts! X
We have a document template stored at the Org level. Is it possible to route such a document for approvals? The idea is to control the template itself.
Has anyone done something similar?
Solved! Go to Solution.
Joe,
This is very doable.
Do you plan to revise the template or just iterate it? Doesn't really matter, just curious.
Let's assume you already have created a workflow for the approval process.
Create a lifecyle template (first state is Open) and point state Open to your approval process.
Reassign the lifecyle of your Doc template to the new lifecycle template that points to your process.
When you plan to change the template just use Set State and set the state to Open (or Revise if you care about revision control on your templates) and that will start the process. Keep in mind the last thing the process should do after the template is approved is enable it. By 'it" I mean the latest iteration of the doc template because that's the iteration that is approved. There are APIs to enable (or disable) a template so this should be done automatically in the process after it gets through the last/final approval task.
Note: Currently Windchill OIRs do not differentiate between a WTDoc and a WTDocument Template therefore the little trick of reassigning the doc template's lifecycle to a lifecycle that points to your process is probably the simplest way to get the job done. Plus, if your doc template already exists the OIR would have no affect.
Hope this help,
David
Joe,
This is very doable.
Do you plan to revise the template or just iterate it? Doesn't really matter, just curious.
Let's assume you already have created a workflow for the approval process.
Create a lifecyle template (first state is Open) and point state Open to your approval process.
Reassign the lifecyle of your Doc template to the new lifecycle template that points to your process.
When you plan to change the template just use Set State and set the state to Open (or Revise if you care about revision control on your templates) and that will start the process. Keep in mind the last thing the process should do after the template is approved is enable it. By 'it" I mean the latest iteration of the doc template because that's the iteration that is approved. There are APIs to enable (or disable) a template so this should be done automatically in the process after it gets through the last/final approval task.
Note: Currently Windchill OIRs do not differentiate between a WTDoc and a WTDocument Template therefore the little trick of reassigning the doc template's lifecycle to a lifecycle that points to your process is probably the simplest way to get the job done. Plus, if your doc template already exists the OIR would have no affect.
Hope this help,
David