I'm trying to introduce a user base to SAS studio. They'll first be running Custom Tasks that my team has written for them and the hope is over time they'll start to use the inbuilt tasks.
To begin with we'd ideally like to customise the Studio interface to make their introduction to it as smooth as possible. The kind of customisation's we'd like to make are:
Is there anyway to roll out these kind of customisation's? I was thinking/hoping that there would be config files or folders that can be edited to achieve the result we need.
Thanks.
SAS/Studio has a REPOSITORY feature that allows you to share your custom task, snippets with users.
https://support.sas.com/software/products/sas-studio/faq/SASStudio_sharesnippets.htm
You can use a SAS Studio repository to share tasks and snippets if you are running SAS Studio 3.5 or later. A repository can contain task files, snippet files, XML files, and HTML files. Depending on your security requirements, the repository can be deployed externally to the Internet or internally to a local application server. To access the tasks and snippets in a repository, users must specify the repository URL in their SAS Studio preferences. After this preference is set, any tasks and snippets in the repository are available in the Tasks and Utilities and Snippets sections of the SAS Studio navigation pane. Administrators can create global repositories so that individual users don't have to set a SAS Studio preference to access the repository. For more information, see "Working with Repositories" in SAS Studio: Administrator's Guide.
I created a Global Repository using AWS S3 bucket to host the repository files (.ctm, .xml, .html...) so that custom SAS Tasks are automatically linked/created when a user logs into SAS Studio.
As for hiding SAS Tasks depending on user groups, I have not done this type of configuration. I would be interested in this as well.
As for hiding code or log while the SAS Task is running, the approach is as follows:
1) Create a .sas driver program that contains the macro variables (if required) from the .ctm inputs.
2) The driver program is placed at the very bottom of the .ctm file with a %include statement.
3) The same driver program has the following options at the top of the program,
options minoperator nomstored nomlogic nomprint nodate nosource nonumber;
Calling all data scientists and open-source enthusiasts! Want to solve real problems that impact your company or the world? Register to hack by August 31st!
What’s the difference between SAS Enterprise Guide and SAS Studio? How are they similar? Just ask SAS’ Danny Modlin.
Find more tutorials on the SAS Users YouTube channel.
Ready to level-up your skills? Choose your own adventure.