It would be nice to be able to copy text from an individual cell in the list table. This is possible in a crosstab but it would be nice to mimic the excel function of copying from a regular table/cell for the list table.  ... View more

The objective would be to have a user scan a mock table shell and then have AI generate the code to fill out the table given an input sas procedure ( e.g. results of proc univariate or proc freq ) .   This would eliminate the need to build table macros  and allow a programmer to be more productive. ... View more

  The new (and former) site SAS for Developers does not contain proc http examples when using the rest api's I think this is a great omission sincs many customers uses this api's from whitin.     ... View more

Hi Team We are big SAS customer running our SAS on Solaris OS. Currently GIT functionality with in SAS Studio is not supported for Solaris OS. We need this feature.     Thank you ... View more

Currently in the SAS-Viya/SAS Studio (Version Stable 2024.02) QUERY interface, it is difficult to control where new columns are inserted in the Query column listing.   The interface is set up for a user to drag a new column from the tables/Columns window on the left into the QUERY>SELECT>Columns Tab on the right for insertion.   It highlights the row the user hovers over, but upon insertion, the new column is not inserted there.  Instead it shows up at the bottom of the Query column listing.  SAS Technical Support informs me this is the "expected" behavior in the current version.   Request:  Please improve this interface to allow users to insert new columns where they are desired in the overall Query column listing.   i.e. provide ability to: - Select where in the column listing to insert new column(s) and put them there when executed. - Allow selection of multiple columns by holding SHIFT or CNTRL keys and selecting them.  Then allow user to drag them to the desired position in the listing.    - When insertion/move occurs, leave the display showing the same section of the column listing so the user can confirm where they went.  Currently, when a move is done, the entire listing changes to a different view so you have to go looking for what was done.  ... View more

Date formatting in SAS VI / LEI is controlled by browser language settings. For example if your browser language setting is English UK then dates will be UK formatted in the UI. Whereas, if your browser language setting is English US then dates will be US formatted in the UI. Clients don't always have access to change language settings on company laptops and therefore feel it would be beneficial for SAS VI / LEI to have a global language setting in VIYA / Environment Manager that automatically formats all dates to the preferred style of the client. ... View more

The disposition list on Alert detail screen should contain only the list that authorized by user queue.   For example The Manager group queue and Manager Employee queue are in the same Strategy. Our user expect that the disposition button list should be displayed only disposition of that user's queue. The attachment is the Manager's screen, our user expect that the gray button will not be displayed. ... View more

Please consider adding a feature to allow CAS server elasticity in the form of auto-scaling for SAS Viya 4 ... View more

Stata has a very handy documentation/transparency/reproducibility metadata function that allows users to add custom, verbose notes to a data file (as metadata). See more information here: https://www.stata.com/manuals/dnotes.pdf.   As far as I can tell, SAS doesn't do this (can label a data file, but limited space to do so).  The maximum length of one note is 67,784 for a single note and multiple notes can be added to a data file (e.g., when doing something to/with it and saving).    The notes are numbered sequentially, so can be used as a change log, e.g.,    1. Saved raw data file after downloading from the web.  2. Created recodes for vars X-Z. 3. Copy of data file used in publication.    See other examples in the link above.    Obviously, this information can be listed in a custom log or in code, but what's better than attaching metadata about a data file to the file itself? Thanks for considering! ... View more

For AML8.3, when the user clicks 'View the alert' to access the alert. The alert cannot be claimed (there is no function to claim/Claim is disable). Meanwhile, the user can click disposition to handle the alert.    So, if the purpose of "View the alert", to see detail inside the alert detail only. Disposition button should be grayed out in case that user click "View the alert" to access the alert. ... View more

The calendar control should allows to put the date restriction to display from the current date (VI10.8 Hot Fix6).   Our customer is using SAS AML8.3 with CDD, they specified that on the 'Customer Review' >> 'Review Details' tab, the calendar control in 'Review Time Period' section(in the attached screen) allows user to put the back date which may cause the incorrect date into the system. ... View more

 The system should allow to set the group restriction to view specific active workflow on SAS Visual Investigator Admin according to the data object authorization. ... View more

In SAS AML8.3, While the user create AML case, Case category should be reflected by Case category. ... View more

Hello.  When working with PROC OPTMODEL and PROC IML, we're actually working with a solver.  Between versions of SAS, this solver is constantly changed for various reasons.  When the solver is updated, a problem that works fine with the current version of SAS then no longer works with the new version.  Since this is for multiple clients, it is not possible to optimize the solver and please everyone.  Would it be possible to add a new option to the PROCS so that when we invoke them, we pick which solver we want to be using?  This way, if someone wants a solver optimized, then a new solver would be shipped and they could use it while it would leave all other users stable as they could keep using the solver they were using before.  This of course means that SAS needs to ship several solvers but I'm sure it can be done. ... View more

The subscribe function to send an email notification to user from any actions with their alert, case, customer and report in SAS AML8.3(to be the same with AML6.3) is necessary for our customer.    ... View more

On SAS AML on Viya 3.5 how can we apply a filter in Triage case screen.  This functionality is available on Alerts screen. Can you add it on Triage case screen?   ... View more

In SAS LEI we are using the Tripwire functionality. One of the OOTB fields for this entity is called Generate Email which is a Boolean field.  On the LEI page template that we have designed for our client the end user is required to check the box to either true or false to request the required email.   This field is displayed on the page template as a check box with the pre determined value of false.  The client is requesting that this check box is automatically checked to true from the outset rather than the end user having to check the box.   From conversations with Tech Support and R&D we know that this is not possible within the current solution and have suggested a feature request whereby the person building the SAS LEI configuration can set the Boolean value / check box to either true or false when designing the page template. ... View more

When we copied/paste a file from SAS Viya, the modification date is the creation date of the new file, Is it possible to have at least 'creation date' and 'modification date' Or is possible to not change the date of modification when copied files ?   ... View more

If an external object (f.e. Custom Step) is added to the Flow then it is referenced by the full path. We would like to reference it by a variable or relative path like "../../Prompts.step" instead. This functionality constitutes the Git integrability and allows for a simultaneous work of more than 1 person while keeping the project in the Git.   We would like to see a following set up – each developer works on own local repository. Inside a repository we have number of Flows. Some Flows in a folder contain Custom Steps.        One developer changes something in such Custom Step and commits the changes. Other developer clones the repository and tries to change the same Custom Step. Dev2 is now unable to save it, because the path of the Custom Step points to dev1’s local repository. It means that even though the Flow is in repo2, the object inside (Custom Step) is from repo1. The path to DEV1's repo is visible if we hover over opened inside object from DEV2's Flow.   It is like this:   We want it to be like this:   Now we have to remove the Custom Step from each Flow and attach the new version, then select every custom option inside. It takes a lot of time, since one Custom Step can be in more than one flow. To solve this we could include objects with relative path (f.e. ../../Prompts/1_Prompts.step) or variable (f.e. ${path}/Prompts/1_Prompts.step) so it works across repositories. We don’t want to keep those Custom Steps outside repository as there is no DI’s check-out option and anyone could change the code of the Custom Step anytime. recording - ref: CS0060147 ... View more