Is it possible to create a "triggered action" on a Child?

Hi all

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.

Maybe I'm doing it wrong?

 

Thank you in advance for your attention:)

1 Like

Small clarification: I use DRIVEWORKS PRO

Hello!

Small questions:

  • Individual or Shared Group?
  • What is or are the files used as a trigger? Are they generated by the Child Specification?
  • Where is the Release Document for the Triggered Action placed in the Flow Specification of the Child Specification?
  • Is this Task Released when using the Create Closed Child Specification Task?
  • Can you give us some screenshots?

I will also recommend contacting your SOLIDWORKS reseller if it currently limits you in your production, it will be faster ;-)

1 Like

Hello

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.

Is that the case?

Oh I forgot!

  Are Child Specifications embedded? 

see the paragraph "Embed Child Specifications":

http://docs.driveworkspro.com/Topic/SettingsProject

The "Embed Child Specifications" option is enabled.

After reading it seems that the concern comes from there, if it does not impact the projects of my colleagues I will try to dig into this side.

Thanks for everything.

Nico