I'm looking to create a "triggered action" on the elements of a child list. This action is functional when I use the child projects separately, but not when they are called by my childList. (Message:<Missing Specification - [Id Spec]> in Autopilot)
FYI: my children are automatically generated in my childList by a macro using "Create close child specification" and then modified by the user. After modification the user "launches" the 3D in the autopilot, at this moment I create my "triggered action" to change state at the end of the generation.
Thank you for the quick answer, I'm not blocked because it's a "bonus" feature that I wanted to add and if I believe your answers it's possible: I'll dig on my side.
To answer anyway:
The project is shared.
The file is generated by the child spec at the same level in the flow, I launch the release of my 3D and then that of my document.
The Create Closed Child Specification is launched upstream, the specs are re-opened and it is when they are closed that the elements are launched.
In my project the 3D are re-used by the user at the end of their entry, the idea is to indicate to them automatically by a change of phase their availability.
So cold, the message <Missing Specification - [Id Spec]> makes me think that at the time the triggered action is released, there has not yet been a transition made on the Child Specification.