Genome-wide association studies is a statistic technology to detect association between a genetic variant and a trait value (e.g., disease status). For one genetic variant (independent variable x) and one response variable (y), PROC GLIMMIX can do the job needed. But we often have 10 thousands or millions of genetic variants. Lopping over PROC GLIMMIX for all variants is extremely slow. Can we develop a new SAS procedure to scan the entire genome faster than using %macro looping over PRCO GLIMMIX?   ... View more

Our client is not satisfied with the “star-like” layout of diagrams in Visual Investigator. We would appreciate adding more layout types, such as tree-like structure API or another means of control of the layout   ... View more

Would it be possible to release the last version of Amiga SAS/C to the public domain? There are a lot of enthusiasts who want to use it but there is no legal way to acquire or use it without infringing copyright. The agent I spoke with (Katy)recommended I make this suggestion because you don't sell it nor support it any more. ... View more

Copying the format of an object (control object, list table, etc) and applying into another object of same type should be available in VA. Specifying a format and applying this one-by-one on every similar object is crazy. Such a feature would be extremely helpful for VA developers.  ... View more

This is a test to ensure that Risk Management-related intake is going to the correct Jira project (PMIBSM) and assignee (Ron Agresta). ... View more

We would like to have  a filter to the object list in the SAS Information Catalog (Discover Information Assets) to hide selected objects (e.g. CASUSERS objects or SASHELP objects). Right now, to prohibit users from seeing an object , user needs to create a CAS authorization rule that explicitly denies Read/Allows access - it's hard to create and maintain, customers have to understand CAS auth rules, know which one to use and how to find them.   ... View more

Tech Support track # CS0373203   Bank requested for feature on “Alerts -> Alert Detail ->Alerts Grid & Analyst Grid”   1. At Bank Transaction Level Alerting is configured. 2. Bank is looking for an option to assess (adding Call Result through Assessment dropdown) multiple Pending Alerts at one go after taking confirmation on Alerted transactions from end Customers and mark Confirmed Fraud (CF) or genuine accordingly. Refer screenshot below. 3. Bank is not accepting the option to open each Transaction level alert one by one and provide Assessment. 4. As an alternative, Bank is referring if they can open an Entity like “Account” clicking “Displayed Entity” option and mark all recent confirmed transactions appearing in Analyst Grid against selected Entity. 5. In current SFM version, once Entity is selected from “Displayed Entity” dropdown where there’s no Alert on that Entity, SFM doesn’t allow to mark listed recent transactions as CF. Refer screenshot below. ... View more

Tech Support track # CS0373198   Bank requested for feature on “Alerts -> Alert Detail -> Analyst Grid”   1. IDBI Bank is requesting to add an additional “checkbox” similar to CF (Confirmed Fraud) on the Analyst Grid to identify a transaction as Confirmed Genuine (CG). 2. The behavior should be similar to CF. If the transaction marked as Confirmed Genuine (CG) and appearing under another Alert then the transaction must show up with a “Green Flag” similar to “Red Flag” icon representing CF transactions. 3. Bank justified that if Analyst already took confirmation from end customer regarding the transaction which is Confirmed Genuine then there’s no way to mark it. If subsequent Alert shows same transaction again then Analyst will not be able to know that the confirmation is already taken and end up calling same customer for already confirmed transaction. This may impact customer satisfaction for Bank. 4. Also, there’s another observation where clicking “CF” checkbox against a transaction autosaves without clicking on “Update”. This is NOT desired as its prone to mistakes. There’s no audit tracking or logging in Alert Event when “CF” checkbox is clicked. Is there a way to prevent auto saving of “CF” tagging and find out who clicked? Please advise.   Refer screenshot below. ... View more

Tech Support track # CS0379464   Bank raised a concern where an Analyst without access of Strategy can Check out Alerts available under Strategy > Queue. Bank requested a feature request to control visibility & access by restricting Strategy.   1. Bank routed an Alert (refer screenshot) with final assessment i.e. “CONFIRMED FRAUD” to a new Queue “CONFIRMED_FRAUD” under Strategy “CONFIRMED_DECISION”. 2. Analysts “Ashwal T R” is not in “Representative Assignment” list of the Strategy “CONFIRMED_DECISION” and kept Direct Servicing enabled in the Strategy. 3. Now, when Analyst “Ashwal T R” logged in, he can’t see the “CONFIRMED_DECISION” Strategy under Strategies section of Alerts Summary page, and this is expected behavior. 4. However, when he searched for the Alerts using Account Number, he can see the aforementioned Alert tagged in “CONFIRMED_DECISION” Strategy and he was able to Check out the Alert and change the Assessment once again. 5. Bank’s concern is that the Analyst “Ashwal T R” should not be able to view and check out Alerts available under “CONFIRMED_DECISION” (Strategy) > “CONFIRMED_FRAUD” (Queue).   While Bank understand the best practice that the Analyst will not search for Alerts by fetching it from SOR database, but Bank is pointing towards a scenario where, • Analyst “Ashwal T R” may receive a new Alert through Priority or Direct servicing where CONTACT_VALUE (Customer ID) is same as the previous Alert tagged in restricted strategy “CONFIRMED_DECISION”. • Now under “Alerts” dropdown of the CONTACT, the previous Alert tagged in restricted strategy “CONFIRMED_DECISION” will be visible along with new alert and will be available for Check out.   Bank’s ask is if we can restrict Alert visibility or actioning through restricting Strategy access which is not supported as we understand. Alerts placed under the same Contact entity can be actioned irrespective of Alerts placed under restricted Strategy.   Note, Analyst has the access of the Multi-org of the Alert.   Refer screenshot below. ... View more

Tech Support track # CS0373886 Feature request on “Alerts -> Alert Details page”   1. Bank has requested to show SFM System induced Alert Status like ‘PENDING’, ‘CLOSED’ under “Status” column AS IS in Alerts grid inside Alert Detail page. 2. But for Analyst induced Alert Assessments (Call Results) like “SKIP”, “CONFIRMED FRAUD”, etc are required to be shown under a separate column with header “Assessment” between “Status” and “Serviced At” columns in Alerts grid. 3. Bank’s rationale behind this ask is to have proper clarity on last Assessment given by an Analyst before SFM System changed it to “CLOSED”.   Refer screenshot below. ... View more

CS0373840 -------------- On “Alerts -> Alert Summary page” 1. Bank has requested “Strategies tab -> Strategy -> Queue -> Contents” option to be made available to Analyst for “Direct Servicing”. 2. Bank’s ask here is to navigate to “Contents” of a Queue from Alerts Summary page itself. 3. Bank’s justification is that the Analysts can have visibility of all pending alerts available in a Queue while doing direct servicing by clicking on Strategies from Alert Summary page (other than Priority Servicing) 4. As per OOB product, only one alert attribute from applied from Score (1-4), Amount, Transaction Date to prioritize an alert under a Strategy for Direct servicing. 5. If there’s a need of sorting based on any other Alert attribute (like Amount) from Strategy other than pre-configured sorting option (like Score (1-4)) then Direct Servicing by searching through “Queue -> Contents” would help. Refer screenshot below.   ... View more

Hi Team   Could you enable the option of disabling the search option from the toolbar.    Currently, when we revoke the “Search in Visual Investigator” capability, agents who create a new relationship (task/document form) without this capability are prompted to search for a object, rather than creating a new relationship object. ... View more

Hello,   When a user tries to edit a locked object in SAS VI, the message currently shows the user ID: "The user {user ID} is editing the object {object label}."   Displaying the user ID is not intuitive. Showing the user’s name instead would be clearer and easier to understand. Optionally, allowing configuration of the displayed identifier (name / ID) would also be beneficial.   Thank you for your consideration. Maayan ... View more

H   In Viya 4, not all labels are shown for Piechart. This is a change compared to Viya 3.5, where all labels was shown- Customer and PSD think this is a breaking change and RnD needs to solve this for Viya   Best Regards Håvard Pehrson ... View more

Hello everyone ! As you probably know, since VIYA LTS 2025.09, SAS provides a tool to perform HCP mapping during EGP to FLW conversion. This is a useful feature ! However, the tool always generates the same block of comments related to reference path mapping. These comments are systematically added and end up duplicating the number of HCP references in the flow.   As a result, simple operations such as CTRL+F searches become noisier and longer than necessary, without adding functional value. It would be extremely useful to add an option (checkbox) to enable or disable the automatic generation of these comment blocks. Another solution would be to make the mapping of reference paths optional in the pipeline of conversion, rather than mandatory.   Thank you in advance for considering this enhancement. Best regards, ... View more

CAS authorization slider does not appear to follow SAS best practices : according to SAS documentation, it is recommended to avoid direct denies and instead use “None” (not authorized) to represent the absence of a permission. However, the current behavior of the slider results in a large number of direct denies being applied, which is not desirable. Although it is possible to correct these permissions manually, many SAS Viya users prefer to use the slider for managing authorizations. This creates conflict of permissions especially when users are in two groups.  Such conflicts are difficult to troubleshoot. Therefore, it would be preferable if moving the slider assigned “None” (not authorized) rather than creating direct denies. Using “None” instead of direct denies would align better with best practices. Explicit denies are generally unnecessary because the Authenticated Users group already inherits denials for all permissions by default. Thank you for considering it!@SAS Viya: CAS Authorization Window     ... View more

Many developers on SAS use SAS Steps and Flows, it could be interesting that SAS Workbench allow you to use SAS Studio as IDE for programming with all the benefits of SAS WO ... View more

We are looking to automate a piece of work that would have data exported to excel and then automatically emailed to suppliers. The problem is that the data needs to be password protected and currently there are no SAS procedures that allow you to add a password to an excel. Similarly we investigated adding a password to a zip file as a method of password protection and found no such feature.   Adding the ability to password protect data for consumption by third parties who do not have access to data tools (i.e. excel, csv) would allow for automation and integration.   We suggest that either a password option is added to proc export or creating a new procedure to password protect excel or zip files would be the ideal solution but any solution that achieved the end result would be acceptable. ... View more

Hi,   I would like to create a Feature Request so that SAS Studio integrates a feature present in E.Guide but absent in SAS Studio (LTS 2025.09 or Stable 2025.12): Simultaneously change the type of multiple columns when importing a file   This issue is one of the minor critical points raised by my customer regarding the adoption of SAS Studio : Productivity loss when my customer develops new use cases.   Thank you   BR Pascal ... View more