I have seen a few posts about similar things over time, but none have seemed to garner the answers that I'm looking for.  My issue is with the tendency of views wanting to open on the MutilDock and the MultiDock insisting on being docked in the same window with my track view.  Here are a few observations:
 

1. The MultiDock is docked on my main monitor under the track view by default - It doesn't matter what I do with the dock during the session or if I save the song, if I close it, it opens back up in the docked position instead of where I left it, which is usually floating on my second display.  I understand that I can hit the letter D (for "D"ock, I suppose) to send the dock to a small "Windows 3.1-like minimized window", but that sits right on top of the status area, hiding the "display" option, and yes, I realize that I can move it to some other area down there, but REALLY?  This is a simple UI thing that I just don't think should work this way.  I want it to remember where it was open before.  I don't want to have to create a special screenset for every possible combination of things (or now a Lens maybe) - assuming that would even resolve this.  I just want it to remember where I put it and open up back there again.
2. It is only that I've been able to move the "minimized" MultiDock to the lower part of my SECOND monitor that I think I might be able to adapt to it, but it seems like a silly adaptation.
3. I am reluctant to want anything to go into the MultiDock because of issue #1 above.  I would rather things all just float if the end result them going to the Dock is that they are non-floating.  I want them to float.  I don't really care If they float individually or as tabs in the dock as LONG AS THEY FLOAT!  I might otherwise adopt using the MultiDock, but as it is right now, this dock only seems to mean more clicks every time I use it.
4. The "new" Synth Rack view has a similar problem, but not inside the MultiDock.  It opens in the right docked position by default.  I have assigned a key on my Macro Keyboard (Logitech G900, which is quite awesome, by the way) to press the otherwise somewhat awkward ctrl-shift-s combo.  So I use it to launch and close the Synth rack with a single keypress.  Like the MultiDock, I want it to remember what I told it to do.  It doesn't.  I hit the Key, SynthRack launches, I tell it to float and move it to my second monitor.  I then hit the key to toggle it closed.  I hit key again and it opens back docked to the side of the main window.  Granted, once I put it in the MultiDock and close it, it remembers THAT position, but refer to #1 above for my frustration with the MultiDock.
5. Back to the MultiDock frustration: if I succumb to the change of just dealing with the "D" key to minimize the dock and whatever windows might be in it, then my ability to recall the SynthRack (or any other window that is docked there for that matter) becomes rendered moot.  In other words: hit the ctrl-shift-s to get the Synth Rack, put it in the MultiDock, hit "D" to minimize the dock and its contents, now hit ctrl-shift-s again - right, the MultiDock does not open because it doesn't know the SynthRack is in there and so the answer is that you need to hit D to open the Dock and then find the tab where the Synth Rack is (are there keys for switching between these tabs?).  Used to be a simple "b" for browser (which I used to leave open on the second screen), now I can either lose it in the MultiDock or I can deal with it docking to the side of the main monitor and taking up my screen real estate on the track view, or manually undock it ever time I want to use it.

Am I being ridiculous?  I don't think so.  This feels like the kind of stuff where the development team didn't use the feature and no one in the usability/QA department was allowed  to talk to the developers before the release was made.
 
At this point, I'm ranting, and I don't know what I expect to happen, since opening two support tickets months ago for problems not completely dissimilar to this that have been broken (basically) forever have gone into the abyss called "your request has been sent to development" - i.e. this is unlikely to see the light of day any time soon - get over it.
 
Can anyone help me understand a functional workflow for these kinds of things?  I am tending to try to just make things work "the old way".  I think the new way could be really cool if it were just implemented in a usable manner, but as it is, it feels like a step backwards and a lot of extra keypresses for a lack of any "betterness" at the end of the trail.
 
Being an IT guy by profession with little patience for people who say they are "too old" and someone who is generally ready to embrace new technologies, new methods, new software, new tools and workflows, etc, I HATE to be in the position of "I wish it just worked the old way", but here I am - and I want to be elsewhere.
 
Help. Me. Understand.

Never mind

Hitting CTRL-SHIFT-S is very annoying, I am really hating this new update.

Blades it sounds as though you are making changes to an already locked screenset - try unlocking it, THEN make your changes and save your project

SilverBlueMedallion
Hitting CTRL-SHIFT-S is very annoying, I am really hating this new update.

Put the synth rack where you want it once, then go to the Lens section, drop down menu, hit Save, you're done. It will open in that lens always. It's really not such a big deal.

Thanks for taking the time to express some of your frustrations.
First off we're focusing on various fixes for 2016.12 which will address some of the bugs you've mentioned.
I'll comment briefly on your points below.
 

Blades
I have seen a few posts about similar things over time, but none have seemed to garner the answers that I'm looking for.  My issue is with the tendency of views wanting to open on the MutilDock and the MultiDock insisting on being docked in the same window with my track view.  Here are a few observations:
 

1. The MultiDock is docked on my main monitor under the track view by default - It doesn't matter what I do with the dock during the session or if I save the song, if I close it, it opens back up in the docked position instead of where I left it, which is usually floating on my second display.  I understand that I can hit the letter D (for "D"ock, I suppose) to send the dock to a small "Windows 3.1-like minimized window", but that sits right on top of the status area, hiding the "display" option, and yes, I realize that I can move it to some other area down there, but REALLY?  This is a simple UI thing that I just don't think should work this way.  I want it to remember where it was open before.  I don't want to have to create a special screenset for every possible combination of things (or now a Lens maybe) - assuming that would even resolve this.  I just want it to remember where I put it and open up back there again.  [KA] Supposed to persist the last position.  We'll investigate.
2. It is only that I've been able to move the "minimized" MultiDock to the lower part of my SECOND monitor that I think I might be able to adapt to it, but it seems like a silly adaptation.
3. I am reluctant to want anything to go into the MultiDock because of issue #1 above.  I would rather things all just float if the end result them going to the Dock is that they are non-floating.  I want them to float.  I don't really care If they float individually or as tabs in the dock as LONG AS THEY FLOAT!  I might otherwise adopt using the MultiDock, but as it is right now, this dock only seems to mean more clicks every time I use it. [KA] Each individual view can be undocked which should be able to be saved in the project in that state.
4. The "new" Synth Rack view has a similar problem, but not inside the MultiDock.  It opens in the right docked position by default.  I have assigned a key on my Macro Keyboard (Logitech G900, which is quite awesome, by the way) to press the otherwise somewhat awkward ctrl-shift-s combo.  So I use it to launch and close the Synth rack with a single keypress.  Like the MultiDock, I want it to remember what I told it to do.  It doesn't.  I hit the Key, SynthRack launches, I tell it to float and move it to my second monitor.  I then hit the key to toggle it closed.  I hit key again and it opens back docked to the side of the main window.  Granted, once I put it in the MultiDock and close it, it remembers THAT position, but refer to #1 above for my frustration with the MultiDock. [KA]  We identified this issue as a bug in the persistence.  It's just been fixed and will be in the 2016.12 update.
5. Back to the MultiDock frustration: if I succumb to the change of just dealing with the "D" key to minimize the dock and whatever windows might be in it, then my ability to recall the SynthRack (or any other window that is docked there for that matter) becomes rendered moot.  In other words: hit the ctrl-shift-s to get the Synth Rack, put it in the MultiDock, hit "D" to minimize the dock and its contents, now hit ctrl-shift-s again - right, the MultiDock does not open because it doesn't know the SynthRack is in there and so the answer is that you need to hit D to open the Dock and then find the tab where the Synth Rack is (are there keys for switching between these tabs?).  Used to be a simple "b" for browser (which I used to leave open on the second screen), now I can either lose it in the MultiDock or I can deal with it docking to the side of the main monitor and taking up my screen real estate on the track view, or manually undock it ever time I want to use it. [KA] This also sounds like a bug.  It's supposed to appear with the focused tab.  

 
Thanks for your patience.  As I said we've identified several issues and should address them in the 2016.12 update.
 
Keith

subtlearts

SilverBlueMedallion
Hitting CTRL-SHIFT-S is very annoying, I am really hating this new update.

Put the synth rack where you want it once, then go to the Lens section, drop down menu, hit Save, you're done. It will open in that lens always. It's really not such a big deal.

Doesn't work if the Synth Rack View is floating - it re-docks on re-load.

@Keith Albright - Thanks for reading and addressing these items.  I would certainly like these things to work right.  I look forward to the December release to resolve these.
 
Since the MultiDock stuff has been an issue for some time, I don't know if the 12-16 update will address all of that, but it would really be ideal for the program to be smart enough to have a logic tree that goes something like:
 
View is chosen to be opened (for example synth rack or PRV), identify the state of the view (if not opened, open it - if a previous view state has been established, use it, if not perform the open in the default location) (if opened already, identify where the opened window resides (if that is in the multi-dock, check the status of the MultiDock - if minimized (D), restore the opened window, once the MultiDock is restored (or if it already was) switch to the tab in the MultiDock that contains the requested view).
 
I know it's not THAT simple, but as a "programmer in a previous life/career" it seems that this sort of logic should be pretty addressable in a UI that was developed by Cakewalk.
 
Thanks again for reading and responding.  And I hope you didn't take offense with my obviously frustrated diatribe!

Well - I downloaded the 12.2016 preview release and I'm happy that the Synth Rack seems to remember the place it was last put.  
 
It seems that I was incorrect about SOME views and their remembering the "outside of the multidock" view that I set them to remember, though it would be nice to be able to set some kind of default for views or multidock behaviors.  Basically, I'd prefer to never use it, but especially not as a default - I'd rather have to choose to use it than to have to see every window want to start there and need to select to undock it on first use.  Seems like this could be a preference setting.
 
Again, there are (for me) a lot of broken things about the way that the multidock behaves anyway - like I mentioned, if I put a view in there and then minimize the dock with "D" (since there is no way to close it and have it open back up the way I left it because "closed" = docked with the trackview), when I try to go back to whatever view that was, it should remember that it is in the multidock and restore the multidock view and switch to the view I wanted.  It's smart enough to figure out the multidock when it is docked, it should be able to figure it out when it is minimized from floating view as well).
 
The end result seems that ONE of the things I mentioned was corrected and none of the others seem to have been fixed or even mentioned in the release notes.
 
I suppose I would have hope that these things would be addressed if I didn't have two open tickets that have been open for months with problems that have existed for years - 1 of those has been acknowledged and sent to engineering, the other one is still listed as a new problem and not even acknowledged/reviewed.  Another month gone by and no change to the status on these age-old broken features just doesn't fill me with confidence.

bump - testing ability to post and wouldn't mind some additional feedback while I'm at it.