Feature Request: Replace encoded characters with the characters themselves in Workspace data display



Our pages have always showed up on Reports with the intended characters themselves, but in Workspace we get the raw code instead of special characters in things like page name / page title, so the display is ugly. Logically we'd fix this by changing the data source or processing, but the reality is that we have tens of thousands of site pages and years of data. Changing our data source or rule process to clean up the many pipes, dashes, ampersands and other special characters would lead a bunch of overhead and 2 years of transition time between old and new pages and titles (our long tail is... long). The activities around this would require major, sustained effort in order to:

  • Get reasonable data on most popular content where top page views aren’t splitting counts of the same page between old and new titles
  • Do analysis like year over year comparisons
  • Maintain internal enterprise training and communications reminding stakeholders to use whatever workaround we put in place while doing analysis for those 2 years:
    • probably a SAINT classification name value for all name sand titles work rather than the usual ‘page name’ or ‘page title’ variable 
    • requiring setting up daily automation for adding dozens of new titles to the classification, just swapping characters where code appears. 

The inability of Workspace to render characters instead of presenting the raw code in the display seems like a product issue, since it is out of step with the way content was presented in other Adobe interfaces (Reports). Since Workspace has way outstripped Reports in sophistication and has been made the go-to tool for data democratization and direct stakeholder use, would it be feasible and reasonable to ensure that Workspace displays actual characters rather than code versions, the way Reports does?  Thanks for considering. 

1 Comment (1 New)
1 Comment



I agree this would be a very helpful feature. I can't think of reason why you'd want to see the encoding of a character instead of the character it represents.