Separator - How do I split a work item and send to different output ports?

Question

question

Cam Seams asked Jan 18, '17 Sam Stubbs commented Jan 20, '17

Separator - How do I split a work item and send to different output ports?

I have 2 work item types in my model: ItemType1 and ItemType2.

Both ItemType1 and ItemType2 enter the separator.

ItemType 1 does not need to be split, only processed and then sent to a specific output port.

ItemType2 needs to be split into 2 work items, then 1 of each of the split work items needs to be routed to different ports. If one of the output ports is blocked, then neither of the newly split work items can exit the separator.

I do not have the option to send ItemType2 to 2 different output ports, while also holding block restrictions on it within the flow tab. Looking for some help on this one, thanks.

-Cam

separator output port itemtype by port

Answer 1 · 2017-01-19T15:06:14Z

Sam Stubbs answered Jan 19, '17 Sam Stubbs commented Jan 20, '17

I think I may have spoken to you over the phone. Like I said, you'll probably find the easiest way to control your logic is with a Process Flow.. I've created a simple example that does roughly as you described, that turns a processor into a separator. (The last requirement of having the items stay in the processor could be achieved using Resource acquisition or Lists)

Here is my sample model for you to look at.

simpletest.fsm

simpletest.fsm (21.9 KiB)

· 3

Jeff Nordgren commented · Jan 19, 2017 at 07:17 PM

@Cam Seams,

Here is an example of using Resource acquisition as mentioned by Sam to make sure that both output destinations of Processor1 are free before releasing either item.

simpletest-jn1.fsm

0 ·

simpletest-jn1.fsm (25.9 KiB)

Cam Seams commented · Jan 20, 2017 at 05:11 PM

@Sam Stubbs

Yes this is is exactly what I was looking for. I am still on version 2016 however, and it looks like the 'token.processor' type of object is not available. Are there major differences in the process flow tool between 2016 and 2017? Having a difficult time trying to replicate this in 2016.

0 ·

Sam Stubbs ♦ Cam Seams commented · Jan 20, 2017 at 05:58 PM

Process Flow should be the same, the only differences are in the new dot syntax of the Flexscript and new variable types. But the logic should work the same.

0 ·

question