topic Re: job processor - Vault - PLM integration. in Vault Customization Forum

job processor - Vault - PLM integration.

mchi_topsoe — Thu, 30 Jan 2025 14:28:59 GMT

We are using the Job Processor to release file to our PLM system (ARAS).

It is based on Item State changes.

ie user set the Item state to "Release to Aras". For an assembly this create one entry in the job queue for each file.

Job Processor picks jobs accordingly starting Top Down from assembly.
1 job:
- Opening the assembly,
- exports the step file,
- closes the assembly,
- updates the Item state in Vault to "Released",
2 job:
- Opening the part file
- export step
- update the item state to "Released"
- close
-- Etc...

Even though it is working, there are a couple of caveats:
Performance: When opening the top assembly, all files are already in memory, and it would be much faster to just travers through the assembly and generate all the files in one go.

Error handling:
- If there is an error when handling a sub part then the main assembly should not be released, everything should go back to previous state.
- The entire batch of step files should not be send to the PLM system, before we know everything is ok.

Any suggestions on how to handle this? Ideally we want to release the Main assembly with all its sub-components in one go. But the Item state change seems to be a bad option for this?

Re: job processor - Vault - PLM integration.

Nick_Hall — Fri, 31 Jan 2025 04:01:40 GMT

If you have something that differentiates a top-level assembly from all the other parts/assemblies - such as a property or category - you could have some logic like this:

if (identifier = "TopLevel") { // Walk the assembly tree // Export the STEP files // Set the status } else { // Set the job status to Success }

You could handle all your other logic in the "if" clause

It's a bit simplistic, but the approach should work

Hope that helps

Nick

Re: job processor - Vault - PLM integration.

mchi_topsoe — Sun, 02 Feb 2025 15:24:15 GMT

Hi Nick

Thanks for your suggestion, but i can not mark individual components differently. there can also be cases where i actually do want to only check in a sub element.
The approach i will take, is to start by changing the state. Then the user should run a single command. This will then validate that components are released. After this start call the job processor to start on the top assembly only.

Unfortunately this requires two actions for the user. But i can not see how else it can be done.

/Michael

Re: job processor - Vault - PLM integration.

Markus.Koechl — Tue, 04 Feb 2025 08:55:13 GMT

An alternate option might be implementing an event handler on the lifecycle state change to Released: this handler runs on the success of the top assembly only and submits the job to transfer. It also might add a user input action asking to transfer Yes/No.

Re: job processor - Vault - PLM integration.

mchi_topsoe — Tue, 04 Feb 2025 09:23:14 GMT

Thanks Markus.

Do you mean a client event handler?

Can the event handler detect the Top-Assembly?

When the user clicks on OK, the files state gets changed, then the event is triggered => we send one single job to the queue?

Re: job processor - Vault - PLM integration.

Nick_Hall — Tue, 04 Feb 2025 21:10:32 GMT

Hi Michael

With Markus' idea, the arguments passed to the event handler will contain an array of all the changed state items.

You would need to check which one has no parents, which will be the top-level assembly. You might have to use GetItemBOMByItemIdAndDate.

Then you add one job to the queue, passing the Item ID as a parameter.

Nick

Re: job processor - Vault - PLM integration.

mchi_topsoe — Wed, 05 Feb 2025 06:17:55 GMT

@Nick_Hall @Markus.Koechl Thanks for your support:-)

Much appreciated.

/Michael