All ideas are welcome. Just because the Idea doesn't make it into the product immediately does not make it a bad idea.
Per support:
[Tier 3 Framework team] confirmed that 15 pages of history is the intended design of the DSP. They also stated that a code change would be necessary to make that 15 number configurable.
I need the page history to extend beyond that for end users who work in dspConduct. Because of the frequent webapp changes, you can get stuck in Conduct proper without being able to return to a content webapp once the history goes beyond 15.
Alyssa Sliney
Thanks for registering the idea. We are looking to improve the navigation and UEX within the DSP starting with the UI refresh in 7.0. We will look to include / consider this requirement post 7.0 to improve the usability of the DSP, especially in the Conduct user experience you specify.
