Week 5: Understanding Packages
I've attached the PDF of the slide deck for the Packaging Working Group session. To view the recording of the session, click the following hyperlink:
Next week we will take a detailed look at RSA Archer's updates to the Searching and Reporting feature.
For responses to the open questions from the session, see the follow-up posts attached to this thread. As always, I welcome your feedback on this session and our approach. Feel free to post any additional questions or comments on within this thread.
- Community Thread
- Forum Thread
- RSA Archer
- RSA Archer Suite
During the Packaging web cast, a few participants raised the issue of using packaging to migrate Personal Reports between RSA Archer environments. While Global Reports are included as part of a package, Personal Reports cannot be included.
However, one participant did send me a note on a possible work-around:
- In your starting environment, promote the Personal Report to a Global Report, permissioned to just a single user (the owner of the personal report).
- Create and download the package.
- Upload the package to the destination environment.
- Open the migrated Global Report and then click "Save Report Changes."
- Save the report as a "Personal Report." The report will now be viewable only by the person that originally created the report. (Switching to Personal Report assigns access back to the user listed as the report creator.)
While labor intensive, this approach does get the report from one location to the other and then allows you to make a change to ensure only a single user can have visibility into the data.
Has anyone figured out how to scrub the SQL database?
Refreshing the environments by migrating packages is a time intensive manual process that's prone to error.
It's much faster and simpler to just copy the SQL DB.