Starting with the release of Strategy ONE (March 2024), dossiers are also known as dashboards.

How to Troubleshoot Workstation Engine Performance

The Workstation engine supports the main dossier authoring screen in Workstation. The dossier authoring screen appears when you create or edit a dossier on your local machine or within your environment. The Workstation engine directs the communication between the dossier authoring screen and back-end support. This engine also communicates with Workstation to update the screen status and receive requests from Workstation.
When troubleshooting issues related to the Workstation engine, determining the source of the problem is a key step that can help narrow down the root cause and potentially resolve the problem. The first question to ask is, "Does the issue occur in a live dossier (on the server), local dossier, or both?"

Live Dossiers

1. Test to see if the issue is reproducible in Strategy Web or Strategy Library.
   If the issue is reproducible in Strategy Web, it's most likely caused by the server.
   If the issue is reproducible in Strategy Library, it's most likely caused by either the REST server or the front-end. Workstation and Web share the same front-end code for dossier authoring.
   If the issue is only reproducible in Workstation, it's most likely caused by Workstation.
2. Test if the issue is project-specific. Is it reproducible within another project?
3. Test if the issue is user-specific. Does it occur when logged in as an administrator? Does it occur when logged in as a user with a different language?

Local Dossiers

1. Test to see if the issue is reproducible only in a specific dossier or multiple dossiers.
2. Verify if the issue is specific to newly created dossiers, existing dossiers, or both.
3. Test if the issue is reproducible from a different Workstation machine or with different operating system (Mac or Windows).
4. If you can consistently reproduce the issue, obtain a copy of the .mstr file. This step is applicable to dossier authoring related issues.
5. Obtain both the detailed Workstation version and operating system versions.
6. Is this a fresh Workstation install or an upgrade? Upgrades retain user preference information, such as custom color palettes, custom visualizations, database roles, etc., while fresh installs do not.

If you are migrating from one platform to the next, such as Strategy 10.4 to 11.0, the cumulative effect of the changes can have a significant impact on your execution results. To minimize these impacts when performing a platform release upgrade, Strategy Workstation allows you to choose the data engine version for each project in your environment.
If you are upgrading from Strategy 10.4.x or earlier, you should set the data engine version to 10 for all projects in your environment, following an upgrade to Strategy 11. Once the upgrade process is complete, change the data engine version to 11 on a project by project basis. This allows data changes to be identified, evaluated, and resolved while maintaining consistent performance across the rest of the environment.
See Minimizing the Impact of Data Changes for Platform Release Upgrades for more information about selecting the data engine version.