Saving a SlicerDicer session retains its configuration, including the criteria, filters and slices, as well as the chosen measure and visualization, so the user can return to it later or use it as the foundation for further work. This avoids the need to recreate a complex population each time. The third option expresses this benefit. Exporting data as raw SQL is not a function of saving a session, because SlicerDicer is designed to be used without writing queries. A session does not automatically generate a printable report, though data can be exported or displayed separately. Saving does not grant administrative access to report groups, since access is controlled by security and by the distribution settings of the content. A saved session can be shared with colleagues in a read-only form and can be used as the data source of a graph component on a dashboard, which makes saving a prerequisite for those uses. Users should give sessions descriptive names so that they can be found easily, as a long list of unnamed sessions is difficult to manage and may lead to duplicated effort.
Chosen Answer:
This is a voting comment (?). You can switch to a simple comment. It is better to Upvote an existing comment if you don't have anything to add.
Submit