PAW Dev Issues - Githubissues

Issues and Resolutions in Pano Dev for First Round of Development

Transparency of dev dossiers if people are unable to see dev environment

User permissions: the analysts don’t have the right permissions in the dev environment to do what they need to do

Resolution:

We have compared the privileges and permissions between the PAW Production Workspaces project and the PAW Development Panorama for Content Developers project and made a few updates. I am continuing to review the dossier tickets to test out the issues that have been provided in those.
If you do run into either access issues or missing objects, you can continue to log those in tickets and as well, send a copy of the issue to the following email group: pano-dev-support@datastrong.com
If it would be helpful, we could set up working sessions (could be on an individual dossier basis or generally, as needed) to review any residual access or other items, so we could address those together.

Performance issues during development Speed – everyone is reporting that dev is incredibly slow.

Resolution:

While reviewing the performance today (6/26/2019), we were able to reproduce similar slowness/issues. While troubleshooting, we found that datasets were not using cache as expected. This was determined to be related to the cache storage setting, we increased that and were then able to use cache as expected.
As we found and updated this cache setting at the end of the day, we know that developers have not been able to confirm that this resolves or helps the issue yet. We will continue to monitor this and if developers experience additional or ongoing performance issues, we will review those. If this pertains to individual dossiers, the performance can be noted in the associated GitHub ticket, as well as provide to the email group: pano-dev-support@datastrong.com