For detailed information on this functionality, refer to the FixedResource.
Output
These properties determine how the object sends flowitems downstream.
Send To Port - This picklist returns the output port number connected to the object that the flowitem should be moved to. If 0 is returned, all outputs are opened and the flowitem is moved to the first downstream object that is able to receive it. See Send To Port picklist.
Use Transport - If this box is checked, the object will request a transport using the Request Transport From picklist to move the flowitem downstream. If it is not checked, the flowitem will be moved automatically.
Request Transport From - This picklist is only available if "use transport" is checked. This function returns a reference to the Dispatcher or Transporter that will be used to move the flowitem. See Transport Dispatcher picklist.
Priority - This parameter is only available if "use transport" is checked. This value sets the priority of the task sequence that will be sent to the transporter or dispatcher. Transporters and dispatchers generally sort task sequences so that sequences with higher priorities will be performed first. Task sequences with the same priority will be performed in the order that they were received.
Preempt - This parameter is only available if "use transport" is checked. If set to one of the preempting values, the task sequences sent to the transporter will automatically preempt whatever the transporter is doing at the time. This may cause the transporter to perform tasks that would normally not be allowed, such as carrying more flowitems than its capacity. For more information on preempting task sequences, see Task Sequence Preempting.
Reevaluate Sendto on Downstream Availability - If checked, the Send To Port will be re-evaluated every time a downstream object becomes available. It's important to note that this is only executed when the downstream object becomes available. It does not continuously evaluate just because a downstream object is already available. If you want to manually force a re-evaluation at some other time than when a downstream object becomes available, then you can do so by calling the openoutput() command on this object.
Input
These properties define how an object pulls flowitems from upstream objects. See
Pull - If this box is checked, the object will pull flowitems from upstream objects. The upstream objects should open all their output ports to allow the object to pull the flowitems it needs.
Pull Strategy - This parameter is only visible if "Pull" is checked. This picklist returns the input port number connected to the object that the next flowitem is to be pulled from. This field is evaluated only on reset of the model and when the pulling object becomes ready to receive its next flowitem. For a Processor with a capacity of 1, this means that the Pull Strategy field will only be evaluated once right after each flowitem exits the Processor. See Receive From Port picklist.
Pull Requirement - This parameter is only accessible if "Pull" is checked. This picklist needs to return either a true or a false (1 or 0). This field is evaluated when considering whether or not to pull in a particular flowitem from the upstream object that was defined by the "Pull from port" field. This field will only be evaluated for flowitems that are in the "ready" state (i.e. FRSTATE_READY) meaning the flowitems are ready to leave the upstream object. Basically, the "Pull Requirement" field is evaluated for every "ready" flowitem immediately after the "Pull from port" field gets evaluated. The field is evaluated again for each new flowitem that later becomes ready in the upstream object. See Pull Requirement picklist.
Reevaluate Pull Requirement on All Items When Each Upstream Item is Released - This parameter is only visible if "Pull" is checked. If checked, the object will re-evaluate the pull requirement for all released flowitems upstream every time a new flow item is released. This is much like the Reevaluates Sendto on Downstream Availability check box, in that you may need to explicitly call openinput() if you want to manually trigger the re-evaluation of the pull requirement.
