Subflow quantity not reading label from token.

Question

question

Kari Payton asked Aug 09 2016 at 5:00 PM Matt Long converted comment to answer Aug 09 2016 at 7:13 PM

Subflow quantity not reading label from token.

I assigned a number of operators based on man-hours needed for the process. In an assign box I have divided the total number of man hours by 12 and use "ceil" to round the number up. So the label "finishingOps" looks like

ceil(getlabel(token, "totalManHours") / 12)

The token then moves to a subflow where I want to get the quantity from the label "finishingOps". I know the value is placed on the label because the token reads finishingOps 13.0000 when I click on it. But the subflow stops once it reaches this step.

Software Version:

Choose One

labels subflow

displayvalue2.png (16.9 KiB)

· 4

Sam Stubbs ♦ commented · Aug 09 2016 at 6:08 PM

Is there a chance we could see your model? It would be easier for us to troubleshoot if we can run it ourselves. (IF it contains sensitive information you can post it in a private question.)

0 ·

Matt Long commented · Aug 09 2016 at 6:42 PM

What do you mean by "stops"? Are any tokens created in the sub flow? If the getlabel() were to return 0, the token would immediately move to the next activity. If it's non-zero then you should see tokens in the sub flow.

0 ·

Kari Payton Matt Long commented · Aug 09 2016 at 7:03 PM

I mean that it doesn't move tokens through the sub flow. If I replace getlabel() with a number 13, I see tokens moving in the sub flow

0 ·

Matt Long Kari Payton commented · Aug 09 2016 at 7:07 PM

Do you have the same result when using the Label: syntax?

Label: finishingOps

0 ·

______

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-08-09T19:13:03Z

Kari Payton answered Aug 09 2016 at 7:13 PM

@Sam Stubbs @Matt Long I didn't have the subflow connected so that it could move on to the next activity. I couldn't see tokens moving because the run speed was high so I only saw the token when it stopped moving through the overall process-flow. It's working now. Sorry!

question