Showing results for 
Search instead for 
Do you mean 

Run a Teamcenter based Workflow from inside NX

[ Edited ]

Hi everyone,


I have been tasked to create a solution in which highly customisable emails containing CAD data (as a 2D PDF) is sent to the correct people in the manufacturing downstream. Since my experience as a programmer is limited, I created an NXOpen/Windows Form program (Lets call it "WF Program"  to accomplish this. It can grab emails directly from Outlook, make a PDF, and send it to relevant parties. However, one additional constraint that has been put on me is that I must also release the CAD part in Teamcenter through a release workflow that my company has made.


Right now, I'm accomplishing this by sending the part attribute data from the "WF Program" (which is in to an ITK program that I wrote (which is in specialised C++) which can create a new process and release it. However, this is very cumbersome and difficult to maintain.


So I was wondering if there was an elegant and simple way to create TC workflow processes in NX. OR Call my Windows Form Program as an EXE during the Release process of a part in TC.




Re: Run a Teamcenter based Workflow from inside NX

Interesting requirement (complicated). Since the whole thing needs to be automated (no approvers) then maybe a simpler approach using the release_man utility is viable?

Randy Ellsworth, Teamcenter Architect, Applied CAx, LLC
NX 11.0.1.mp01 | SW 2016 | TcUA 11.2.3
Evaluating:AW 3.2

Re: Run a Teamcenter based Workflow from inside NX

[ Edited ]

I definitely considered that utility since we use it to unrelease parts, but is there a way to programmatically resolve the location of dataset within the Teamcenter DB? That's the main quirk I have to overcome. With the ITK's tag system I don't have to worry about finding the location of the file

Re: Run a Teamcenter based Workflow from inside NX

Hello Karz,


If you looking for invoking your EXE from release process, then there are workflow action handlers -

"EPM-system" and "EPM-invoke-system-action" which can be used to run an external command.


You can check the behavior in Workflow Designer help document and see if that helps.