question

I think the attributes “scrap” and “good” are not perfectly good for your purpose. It is your aim to separate a flow of items. As previously suggested you can divert 10% directly to an output port and 90% to another port. Or you can assert a label tag, previously called as Type and set 10% to a number value of 1 and 90% to value 2. Both variants do what you want indirectly. You’d like to assert something as “good” and “scrap”. This is possible, but totally ineffective. You would have to test for the existence of “good” and “scrap” each time you want to divert your items. Both suggested variants translate ”good” and “scrap” to number values, because a number is easier to get evaluated than an array of characters like “good” and “scrap”. And there is another problem, if you say at the start of your model that something is currently “good” and it is becoming later “scrap”, how would you do this if have already set a tag called as “good”. Would you delete the tag and then add another tag as “scrap”? Because this takes much more coding, both advanced users suggested an indirectly approach. I would do the same as both suggested. But I would tell you to think about a different name for your label, that indicates the attribute of ”good” and “scrap”. What about “HowAmI”? Then you can still set a value for “HowAmI” as “good” and “scrap”. Yes, you can set a label value as an array of characters called as string. And you can test, if the value of “HowAmI” is “good”. But this test doesn’t automatically involve, that any other value is always “scrap”. It can be anything else. It can be “GOOD”, “bad”, “bADd” and even empty. That is why users suggest to set discrete number values to 1,2,3,4. And programmers are a lazy kind of people, they think how can I make my live more comfortable. The values of a range like 1,2,3,4 is suiting better in FlexSim than 0,1,2,3. That is because the ports, which are responsible for the diverting of flow items are numbered as 1,2,3,4,.. Programmers think of easy and lazy methods. They have already translated “good” and “scrap” indirectly into number values. For once it is ok, twice that’s getting complicate, more often it would be complex. Now programmers do it in their language directly. They think “good” will mostly go to port 1 and “scrap“ will go to port 2. Then it is a good idea to set the value of label “HowAmI” to 1 for good parts and 2 for scrap parts. Then it is not necessary to test anymore. Now anyone need only read the value of “HowAmI” and divert an item directly to port 1 or 2. There are occasions you have to divert items to other numbered states. That is not really a problem, then you translate the number differently by a structure called “switch by case”. If you aren’t convinced of this lazy idea to make life comfortable then you can still assert a label called “good” and for other items called “scrap”. The condition for a test is then

objectexists(item.as(Object).attrs.labels.subnodes[“good”])

Hello Alejandro,

I would suggest the other way arround, I would send by percentage using the "by percentage" option in the first queue and then I would change the label on entry in each Queue.