Job Processor - Sync properties upon lifecycle state change issue

[kchong78]

Hi all,

I've been noticing this issue occur several times already.

A file gets checked into Vault with the file name, part number and other properties set. Sometimes, a file needs to be renamed as well as the part number and other properties.

The procedure that is adopted to do that is to change the lifecycle state from "Released" to "Work in progress", rename the file using the Vault command, check out the file, modify the properties, check it back in and change the lifecycle state to "Released".

In Vault settings, the lifecycle state transition from "Approved" to "Released" has the action "Sync properties using Job Processor".

I have noticed that there have been instances where after Job Processor does it's thing, the part number of a renamed file gets reverted back to it's old part number.

Is this the normal behavior for Job Processor's "Sync properties"?

Regards,

Kenny

[ihayesjr]

You should check the Part Number mapping to see if a different property has a high priority in the mapping. This could cause what you are seeing.

[kchong78]

Hi Irvin,

Thanks for the suggestion. The property mapping is configured as "synchronizes property between Vault Property and file property".

I assume Vault Property takes priority over file property and that is making the old part number over write the newer one in the file?

[ihayesjr]

There are two areas that I am talking about.

The Red box is how many properties are mapped to the Part Number property.

If you have multiple Inventor properties mapped to Part Number, the order in which they are mapped could be causing the problem.

The Green box is the mapping direction.

This determines if the file value or the Vault value is the master. Or it could be bi-directional.

[kchong78]

Thanks for the explanation. 

This is how it is set up right now.

I'm thinking when the mapping is set to bi-directional, preference goes to the property in Vault when there is a conflict in data. Is that correct?

[ihayesjr]

@kchong78 

"The procedure that is adopted to do that is to change the lifecycle state from "Released" to "Work in progress", rename the file using the Vault command, check out the file, modify the properties, check it back in and change the lifecycle state to "Released"."

According to your process is here is what should happen.

• During the Rename, make sure to select the Update Part Number drop-down option. If the Part Number values are based on the file name, it will get updated automatically. If it has been manually entered and not the same as the file name, it will not get updated.
• Checking out the file: if the part number was updated during the Rename step it should already match the Part Number property inside Vault.  If an Update Properties was executed inside of Inventor when the file was modified, the value in Vault will be set inside of the file.
• Checking the file in: If the value in the file was modified after the Update Properties was executed during Checkout, the Part Number value in the file will be written to the Part Number property in Vault during check-in.
• Change state from WIP to Release and Sync Properties by Job Processor: the check-in should already have the file part number property matching the Vault part number property. The synchronize properties at this point will only update properties in the file that don't match the properties values in Vault. Vault values will be set in the file at this point.

Hope this helps.

[kchong78]

Hi Irvin,

Thank you for your detailed explanation. It makes sense and it's the behavior that I'm expecting as well.

This is what's happening when I change the state of the file in Vault.

The "update part number" drop down box was checked when this file was renamed.

[ihayesjr]

Thanks for the image. I would expect that the part number should not have changed between versions 19 and 20.

Are there any other properties in this file that has the part number in it?

[kchong78]

There are no other properties in the inventor file with the same value "100399".

I have noticed that it has been assigned an Item, and the Number of the item is "100399". Could that be the problem?

[ihayesjr]

Yes, that could be the problem. Check the Number property in the Property Definitions dialog.

[kchong78]

Yes, the configuration is the same on my side. That explains why Job Processor keeps updating the part number in the file to the Number value of the Item.

Is it possible to change the Number mapping to bi-directional? I don't seem to have that option.

[ihayesjr · Accepted solution]

The "Number" property for an Item is the "Item Number". This is why you cannot change the direction. If the Item is to match the new Part Number in the file, you need to manually change the Item Number to match it. If it doesn't matter that the Item Number doesn't match the file's Part Number, then you can remove the mapping in the "Number" property.

I highly recommend that you test changes to this area in a test vault prior to making the changes in your production vault. This way you have a complete understanding of what the change will affect.

[kchong78]

Thanks for the explanation, Irvin. I'll have to discuss with my colleagues on removing the link between the part number and the item number.