Custom Job on lifecycle state change

Anonymous — Mon, 01 Jul 2019 23:32:51 GMT

Hi All,

I've downloaded coolOrange powerJob's for Vault and have begun experimenting with some of the sample codes (creating STEP, DXF etc).

I began by adding the Sample.CreateSTEP custom job type to the Review > Released lifecycle state change. During testing I could see the job getting added to the job server queue but it would fail to create a STEP file. I discovered that it would work perfectly if our lifecycle was assigned to files, but we use lifecycles on items instead!

Can anyone point me in the right direction to get this working for lifecycle state changes on items? I want the job processor to create STEP files for all .ipt's that get released.

Thanks,

Re: Custom Job on lifecycle state change

Markus.Koechl — Tue, 02 Jul 2019 11:51:08 GMT

Assuming that your target file is the primary linked component of your item you could get the file id in a single line if you got the item object instead of the file object within your job context:

$primaryFile = $vault.ItemService.GetItemFileAssociationsByItemIds(@($item.Id), "Primary")

The $primaryFile[0].CldFileId allows continuing in the given context of your job sample.

Hope this helps.

topic Re: Custom Job on lifecycle state change in Vault Customization Forum

Custom Job on lifecycle state change

Re: Custom Job on lifecycle state change