Virtual Dock Management board for warehouse

Hey, cool use case. There’s a couple options I’d suggest exploring:

• One would be to assign conditional formatting to each spur that could then be toggled using actions to flip the formatting off or on depending on when that bottom circle is clicked.
• Another would be to assign custom data to each shape that notes whether the pallet is occupied, and then using conditional formatting based on the shape data to show when something is highlighted (you could extend this so that if any of the shapes in that spur have custom data that show they’re occupied, then the conditional formatting would show all shapes in that row as occupied - this would be a little harder and would require formulas)

Either way, I think a combination of conditional formatting plus custom data are the way to go here. Our Intelligent Diagramming badge would be perfect for learning more about these options. I’d start by watching this video. 

Now let’s go for that Bonus :) ...that’s actually pretty doable using some of the features noted above. I’d suggest adding another Custom Data element that represents the route code...you could hit the +T next to the custom data so that data shows up on the shape itself; it could also be used as the way to show to the solutions above that the spur is filled (ie: conditional formatting that if the route code is not empty, then show it as grey). Total positions as well as number of filled pallets could also be custom data...though you may want to consider another shape that represents the spur and it’s related data so you can calculate things based off that. You could get fancier with some formulas, but I think this would do as a start. 

Give that a go and let us know how it’s working for ya.

Bonus: You can use a conditional formatting rule to show the routes for each pallet too, and you can hide it anytime you don’t want to see it.

Lance, terrific work as always. I appreciate it!

Is there any way to simplify the way pallets are highlighted? Like just making the header into a button or something? 

Alright, I added functionality that makes it possible to simplify this. The Check Box and Radio Button shapes in the UI Input library now have the attributes “selectedvalues” and “selectedvalue”, respectively.

We can replace the route boxes on the left with a Check Box shape and add the property “Occupied routes” set to =this.$selectedvalues. This will return an array of all checked values.

Then, we can update each of the pallets to set the “Occupied from route” property to =IN(SIBLINGS.'Occupied routes', this."Part of route").

It will find the sibling object (on the same page) that has the property “Occupied routes”. Since there is only one, it directly returns that value. And we check if the property on the pallet, “Part of route”, is in the returned array.

Similarly, we can replace the spur headers with Radio Buttons. (It doesn’t actually matter if we use Radio Buttons or Check Boxes, but remember that the attribute on the Radio Button is “selectedvalue” and on the Check Box is “selectedvalues”. You can check what attributes are on a shape by using the formula “=ATTRIBUTES”.)

On the radio buttons, I added the attribute “Occupied spur”, which is set to =this.$selectedvalue. It returns the value of the selected option (in this case, there is only one possible option because I have a separate radio button shape for each spur).

Then, we can update the “Occupied from spur” property on the pallets to =IN(SIBLINGS."Occupied spur", ASSTRING(this."Part of spur")). We have to use “ASSTRING” because our “Part of spur” property is interpreted as a number, but the “$selectedvalue” attribute is always interpreted as a string since it is the text typed into the shape.

Now we end up being able to easily select routes and spurs.