If you don't want combinations of colors in either section, you could just as easily use List Picker, List Views for them, and JOIN the resulting .SelectionIndexes to get a print job number, like red/green ==> 14.
You still haven't told us about print job numbers.
Must they be unique?
Should their values have specific numerical order requirements, like reds should precede greens?
What are they used for? For filing the print job outputs? For sequencing the jobs at the printer?
The print job number is simply there for the user to indicate which print job is being processed.
You can specify a maximum of 10 print jobs that will be processed one after the other.
If these are processed then this should also be displayed at the end.
And what you mean with list picker I do not really understand.
So currently it looks like this I just don't quite know which block I have to use now so that when you have made your selection it is added, it would be best if it would do this automatically and then I have to press another button to start the job.
Label 4 is currently only there to show me if what I have tested also works later it would be better if this also works via a button so that I can then print the button to start the job.
I don't see how you can go further in this project without knowing the web API of the web server.
How are the URLs formatted to deliver the color codes, and how are the responseContents encoded to deliver information from the Web server about its print queue?
The colors have certain values so that a certain number comes out which tells the program in the PLC which part must be pressed together with which part.