API – no GetRestrictions events for ECO record lifecycle state change

[Bronislav.Simunek]

Hello

When programming a custom restrictions for items only, everything is fine. UpdateItemLifecycleStateEvents are available on the ItemService and you can add any restrictions that are required to force a customer standard.

Things change significantly when items are driven by change orders (ECO). Then items are linked as ECO records and their lifecycle state can be changed only within the ECO. UpdateItemLifecycleStateEvents (ItemService) are not invoked on such item lifecycle state change. In ChangeOrderService there are no such events available.

Please make UpdateItemLifecycleStateEvents (or UpdateFileLifecycleStateEvents) available for ECO records.

Kind regards

Bronislav

[psaarloos]

I fully agree with this idea. API events should be invoked in all circumstances, not matter where the action is initiated from! It's a real pain for many users of our extension product for Autodesk Vault that the behavior of changing item life cycle states is different from changing file life cycle states from within an ECO.

I've had quite some discussion about this issue through the support system. Please take a look at ticket 13032283. I've noticed update 2018.2 contains the following line in the readme: 'Missing events when an item / file status changes within an ECO. Although this is noted as a fix, I can confirm the issue is only solved for changing item life cycles from within an ECO!

Our extension product is capturing the UpdateFileLifeCycleState event in order to start a post processing procedure. Many issues arise when users change the state of a file from within an ECO right now. Please implement this 'change' as soon as possible in Vault 2017 and Vault 2018.

Regards,

Pim

'

[rbergsma]

Dear Autodesk

I agree with Bronislav and Pim. Using an Item within an ECO should not change the behaviour of the API. 

We at CADAC noticed that our customers do not want to miss our product extension when working with an ECO.

Vice versa, we noticed that an increasing number of customers start to see the benefits of using an ECO.

By the way: ECO is not only shorthand for Engineering Change Order, but also Engineering Create Order.

An excellent tool when you want to manage your engineering activities

[kerrild]

 This frustrating restriction in the system has actually limited the usability for our users. The attached image is an example of a live ECO in our system with 13 files receiving the same change. For our user to right-click and go to folder for each individual file then navigate back to the eco to go to the next number (instead of just right-click and change state) introduces a lot of additional steps and/or manual intervention if they have to manually type each number in project explorer. This is a lot of unnecessary excess work in comparison and this example isn’t the largest of ECOs some have hundreds of files attached. 

It seems crazy that calling the same event does not perform the same function?

[YounesYammouri]

The request for UpdateItemLifecycleStateEvents has been implemented and is invoked now from the ChangeOrderService in Vault 2018.2 Update:

When items are driven by change orders (ECO). Then items are linked as ECO records and their lifecycle state can be changed only within the ECO. UpdateItemLifecycleStateEvents (ItemService) are not invoked on such item lifecycle state change. In ChangeOrderService there are no such events available.

However the request for UpdateFileLifecycleStateEvents to be invoked by the ChangeOrderService is still under evaluation.

Thanks

Younes

[Anonymous]

We do have the same behaviour with one of our customizations concerning documents.

The document state changes are not limited to the ECO.

If the user selects one document in the ECO tab and start the state change via the button in the toolbar, the events are triggered.

If the state change is started via the right mouse click, the events are not fired.

It is an 2018.2 environment. We do not have item linked to an ECO, so no test results on this specific topic.

regards

Guido Terbrack

[dmorse]

Why has the UpdateItemLifecycleStateEvents been updated so that it is captured and not UpdateFileLifecycleStateEvents? We need the ability to capture both.  When can we expect the Files portion to be implemented?  "What's good for the goose is good for the gander"!

[YounesYammouri]

UpdateFileLifecycleStateEvents supports within ECO has been implemented and is available now within Autodesk Vault Professional 2019.

[kerrild]

@YounesYammouri are there plans to backport this to Autodesk Vault Professional 2018?

[YounesYammouri]

@kerrild yes there is a plan to backport this to Autodesk Vault Professional 2018.