question

Hi @Marc K,

Unfortunately, there isn't an easy way to accomplish this. However, I was able to design a work-around using process flow.

1. You will need to replace the hallway with two one way Network Node paths.

   1. 

2. Since the process flow is quite involved, I will explain it at a high level. Refer to the attached model for specifics. Please feel free to ask any questions.
   1. The resources represent the cross hallway having traffic. You only need to use the default settings.
   2. The Event Triggered Source is the key to this setup. It will trigger a token to be created whenever a specific Transporter requests to enter the hallway.
   1. 
   2. In the Label Assignment/Match Value field, the "Traveler" will be the Transporter requesting the hallway. Use Model.find("(The transporter you refered to)").
   3. In the "From Edge" row, you will need to enter the integer from which the transporter enters the node. This will stop the Source from generating a token when the Transporter is exiting the hallway.
3. The Assign Labels activity assigns the transporter to the token. This will allow us to control the Transporter using the token.
4. The Acquire resource makes the transporter check that there is no cross traffic in the hallway.
   1. Additionally, use the Max Wait Timer to stop the Transporter if it cannot acquire the hallway.
5. The Custom Code simply starts the Transporter again if it was stopped in the Acquire activity.
6. The Wait for Event activity waits for the Transporter to reach the end of the hallway. You will need to configure it similarly to step 2.
7. In the Release activity, use the default settings.
8. Use the Sink activity with the default settings.
9. You will need to do this block of activities for each transporter going each way.

I hope this helps!

onewayhallway.fsm