[ FlexSim 22.1.3 ]
The option "Mark Slots with Outbound Items" on rack objects is coloring all currently occupied slots when a storage item is set as outbound.
Example Image: (The Queue only pulls yellow (Type-4) items, yet all slots with items are colored)
File uploaded to NextCloud as "MarkOutboundBug_22_1.fsm"
This happens in 22.2 and older versions as well.
That option marks shelves containing items that have been released, not just items that are waiting for a transport. All of those items have been released, and some of them have been pulled by the queue and requested transport.
As Joerg said, this is primarily related to Minimum Dwell Time. In a rack, if you use a minimum dwell time, then the item won't be released until after its dwell time. Once an item is released, then the Mark Slots option will draw the slot red.
Thanks for the quick reply. Though the same still happens, if the dwell time of the items hasn't elapsed yet. (The Queue in the screenshot doesn't have the Pull Requirement, the blue and green items are not released yet.)
Furthermore, slots are also colored when the rack is not set as a Fixed Resource and an item is marked as outbound by the Find Item activity in a process flow. In fact all slots but the one containing the outbound item are colored (in a different shade of red). Do all items in a "Non-Fixed Resource-Rack" count as released and the activity is triggering the update of the coloring somehow?
Looking at the StorageObject's code, it seems that it was updated to also draw red based on the item's currentSlot and assignedSlot in addition to the item's FR state. See FlexScript Class - Storage.Item.State (flexsim.com)
Right now, it seems like it is checking that currentSlot is the slot the item is in and assignedSlot isn't null. I think this is a bug, and that the comparison should be that assignedSlot is null or isn't the currentSlot, as described in the Outbound state section of the Storage.Item.State documentation.
The dark red color may be a visual glitch of a texture color spilling onto the red mesh under certain conditions based on what's drawn and in what order.
I'll add a case to the dev list.
