topic Re: One item, two open revisioning records in Fusion Manage Forum

One item, two open revisioning records

bryce_crawford — Thu, 10 Jan 2019 23:21:24 GMT

I came across an interesting issue while testing out our tenant. I have a change request workspace that people can add items they would like a new revision for. I created a script that will take most of that information from the request and create a change order in a revisioning workspace and attach any items from the request. While testing it out I noticed that two separate requests had the same item, and when the script automatically generated the second change order it ignored the usual constraint that only allows one revisioning workspace record to control an item. It appears that the change order that completes first locks in the revision. I would however like to find out how I can prevent this in my scripting. I can't see any reference to finding out if an item is already controlled by a revisioning workspace although there is a notation on the item's page.

Re: One item, two open revisioning records

PLM-Sylvain.Bailly — Mon, 14 Jan 2019 09:05:21 GMT

Hi Bryce,

I know that we already discuss about this issue in 2 different topics and no solution was given:

- CR/CO CLONE MANAGED ITEMS OPTION

- Problem: possibility to have an item in 2 CM

During the CO creation, you must find a way to check all the CO or all the items of your current CO to see if each one is not used in another CO. If you use the scripts in Administration > System Configuration > Scripting to do this check, do not forget that the script cannot run more than 8 seconds (Autodesk restriction). That's why, I think that this operation should be externalized.

Re: One item, two open revisioning records

bryce_crawford — Thu, 24 Jan 2019 23:38:49 GMT

"During the CO creation, you must find a way to check all the CO or all the items of your current CO to see if each one is not used in another CO. If you use the scripts in Administration > System Configuration > Scripting to do this check"

I looked through your links and I came to the same conclusion that I could use scripting. How would you do this check? I can't see any calls in the scripting reference to check if an item is on a change order already. There must be a system flag because there is a green icon when i navigate to an item that has an open ECO. My best guess would be the item.descriptor.dvi but it appears there is no call to see if it appears on a managed item tab somewhere.

Re: One item, two open revisioning records

PLM-Sylvain.Bailly — Fri, 25 Jan 2019 09:22:50 GMT

Hi,

The flag that you see is the "Pending Change" information (more info here).

If you go to the administration of the items and BOMs workspace (Administration > Workspace Manager > Items and BOMs > Bill of Materials Tab), you can see that the field "Change Pending" is a System property. I am sorry but I don't know if it is possible to access it in a validation script.

But, if it is possible, I think that you will be blocked with the 8 secondes problem because you need to check all the children and the children of the children. I try to do this kind of script this week for another problem and I was also blocked: Script BOM review all sub levels. But as Tony said, it is perhaps better to use "an external tool to do the processing. Jitterbit or similar.".

Re: One item, two open revisioning records

tony.mandatori — Fri, 25 Jan 2019 13:34:05 GMT

It sounds like the issue is due to the script's ability to override system constraints.

I think you can use a workspace picklist on the item to identify if it is already attached to a Change Order. I realize this is a redundant attribute, but you don't have to display it to the user. Whenever an item is added to the affected items of a CO, use a script on the workflow transition of the CO to set the attribute on the item to the CO descriptor. Then, modify the script that automatically creates and attaches the CO to check this new attribute during creation of the new CO.

Would that work?

Re: One item, two open revisioning records

bryce_crawford — Fri, 25 Jan 2019 20:13:07 GMT

That would work, but isn't worth it. I was hoping to have an easy method to do a check on the managed items. There should only be a handful of items on a change request that would be converted to a change order. I'm really just trying to save the user some work in entering redundant information since the affected items would already be attached to a request.