Identify Process Flow Event-Triggered Source's Current Object

Question

question

Stan Davis asked Jun 20 2016 at 8:38 PM Stan Davis commented Jun 23 2016 at 2:05 PM

Identify Process Flow Event-Triggered Source's Current Object

Is there a method of determining the name of the current object associated with a Process Flows' Event Triggered Source activity? Once an object is sampled from the 3D model, there is no indication of the object's name in Quick Properties or on the Process Flow itself (short of putting the object's name in the activity's title). Thanks.

process flow activities

______

Cookie preferences

Your privacy is important to us and so is an optimal experience. To help us customize information and build applications, we collect data about your use of this site.

May we collect and use your data?

Learn more about the Third Party Services we use and our Privacy Statement.

Strictly necessary – required for our site to work and to provide services to you

These cookies allow us to record your preferences or login information, respond to your requests or fulfill items in your shopping cart.

YES

Improve your experience – allows us to show you what is relevant to you

These cookies enable us to provide enhanced functionality and personalization. They may be set by us or by third party providers whose services we use to deliver information and experiences tailored to you. If you do not allow these cookies, some or all of these services may not be available for you.

YES

NO

Customize your advertising – permits us to offer targeted advertising to you

These cookies collect data about you based on your activities and interests in order to show you relevant ads and to track effectiveness. By collecting this data, the ads you see will be more tailored to your interests. If you do not allow these cookies, you will experience less targeted advertising.

YES

NO

Are you sure you want a less customized experience?

We can access your data only if you select "yes" for the categories on the previous screen. This lets us tailor our marketing so that it's more relevant for you. You can change your settings at any time by visiting our privacy statement

Your experience. Your choice.

We care about your privacy. The data we collect helps us understand how you use our products, what information you might be interested in, and what we can improve to make your engagement with Autodesk more rewarding.

May we collect and use your data to tailor your experience?

Explore the benefits of a customized experience by managing your privacy settings for this site or visit our Privacy Statement to learn more about your options.

Answer 1 · 2016-06-20T20:42:44Z

Matthew Gillespie answered Jun 20 2016 at 8:42 PM Stan Davis commented Jun 23 2016 at 2:05 PM

The object field in Quick Properties should be populated with the name of the object. It should also show the name of the first object your listening to to the right of the activity when you click on it.

objectname.gif (134.5 KiB)

· 3

Stan Davis commented · Jun 20 2016 at 9:07 PM

Yes, that is what I thought. However, I was re-performing phase 1 of the Kanban process flow tutorial and had Object as 'current (No Instance)' and Event as 'OnEntry' for the event triggered source. The model appeared to run correctly. After your reply, I re-selected the processor, and I see the processor as the 'Object' and see it listed next to the activity on the process flow. It appears I previously had the trigger set on the ProcessFlow's OnEntry event not the processor's. Thanks.

0 ·

anthony.johnson ♦♦ Stan Davis commented · Jun 21 2016 at 2:47 PM

Stan,

The reason the tutorial Kanban process flow uses 'current' as the object of an event triggered source is because that process flow is a fixed resource, or 'instanced', process flow, not a general process flow. What that means is that the process flow has a defined set of objects that it is attached to, and a different 'instance' of the process flow runs for each attached object, where 'current' is a reference to the attached object for that instance. Implementing the process flow this way makes the process flow easily reusable because you can make another object into a kanban labeler simply by attaching it as a new instance of the process flow. If, on the other hand, you use a direct reference (to Processor2 in the pic above), then it becomes difficult to expand the process flow to make multiple objects into kanban labelers. You'd either need to use something like a resource, or you'd essentially have to copy/paste the entire flow chart and redefine the direct reference for each labeler object. Both of those make it harder to maintain and tweak going forward.

0 ·

Stan Davis anthony.johnson ♦♦ commented · Jun 23 2016 at 2:05 PM

Anthony,

Understood.

I figured out where I got turned around. When adding the Event-Triggered Source activity on page 253 of the 16.0.0 manual, the tutorial states to ensure Object is current and then to sample the processor in the model and choose the OnEntry event. Because I sampled the event on processor, I was thinking the event-triggered source activity is now connected directly to the processor, and I should then see its reference somewhere in the activity's Quick Properties. That drove the initial question.

I now understand that I was simply sampling the 3D model as a means to get 'OnEntry' in the event field and not to get a specific object's OnEntry event. Obviously, I could have equally just typed 'OnEntry' or selected it from the dropdown or sampled OnEntry from another object (which I tested).

Thanks for the support.

Stan

0 ·

question