Issue with Default Workspace Dashboards Created in App Engine Studio

[Mike Lynch]

As of the Washington release (confirmed on 2 SN instances), it seems that new and existing apps with workspace experiences are behaving different. When I click a data visualization component to drill into a record from the home page dashboard, it takes me to the classic UI instead of a tab within the workspace. What's going on? How can I fix this? This did not happen in Utah. Thanks!

Steps to reproduce:

1. Create a simple one table app in App Engine Studio

2. Add a workspace experience for the app.

3. Add a record to the table in the app.

4. Go to the workspace home page and click the default score widget showing for the record.

The record open in the classic view instead of the workspace.

[Lakshmi Royyala]

Yep, I got the same "working as designed" response from Support and I argued how landing into Core UI from a workspace built in "workspace builder" is the intended design. Few days ago, I verified this using a PDI on Vancouver release and this was a non-issue.

I'm trying to implement the workaround but its crazy amount of work. Every tiniest thing should be configured properly in UI builder (like spacing, borders, backgrounds, margins, clicking "view All" on SimpleList or 'Show all' on grouped records etc..) But this issue forced me to learn UI builder, which has been a good challenge. 

Even with this issue, I have a newfound appreciation for the AES (esp. workspace builder) team w.r.t how much is done behind the scenes.

I hope they fix this issue soon but I don't think they fixed it in the latest Patch3.

[Mike Lynch]

Platform Analytics App id: sn_app_analytics_w  version 4.2.2 resolved the issue for me.

[Mike Lynch]

Platform Analytics App id: sn_app_analytics_w  version 4.2.2 resolved the issue for me.

[Mike Lynch · Accepted solution]

Platform Analytics App id: sn_app_analytics_w  update resolves the issue. I updated to 4.2.2 and can confirm the issue is resolved!!

Known defect PRB1743694

[Michael Todd]

Hi Mike, thanks for sharing but after installing 4.2.2 on a sub-production instance, still seeing the same behaviour. Can you share the link to the problem record - I can't find it?