It is not possible to cancel a program that has been submitted using the Background Submit feature in SAS Viya. There is no Cancel button for individual programs that are submitted using Background Submit. Only an admin can cancel the jobs using workload orchestrator.  ... View more

When processing character in a data step, SAS silently truncates the result when assigning it to a variable with length shorter than the result. I know this is standard, documented behavior and that SAS programmers are generally aware of it. However in even mildly complex data steps, a small oversight can lead to truncations that are difficult to detect at all, let alone quickly find the source problem. So the idea is to add an option to report errors or warnings whenever a DATA step assignment statement truncates the value.   I'd guess that in 99% of these cases, the truncation is clearly undesired behavior, like in this example:     /* definition of shortvar; in practice, this may be imported or heavily processed data, so it isn't obvious what length it has */ data example1; shortvar = "short"; run; data example2; set example1; shortvar = shortvar || ' long'; /* silently truncates */ run; proc print data=example2; run; /* output: obs shortvar 1 short */     This type of truncation is obviously not desired because it happens when we try to add more characters. The result is that the variable appears unchanged and it isn't obvious why. ... View more

Recently, our cloud security team started enforcing the Kubernetes ‘pod security standards’ with the Kyverno tools.  See standard details: https://kubernetes.io/docs/concepts/security/pod-security-standards/#restricted  Most of the SAS VIYA pods are running with ‘no-root’ user security setting, but do not have the explicit restriction on "runAsNonRoot" security context. Kyverno flags and blocks all these pods and breaks down the SAS VIYA application.  The temporary work-around is to write kyverno exception. See below. Since this is the Kubernetes security standard, it is strongly suggested to SAS VIYA platform to consider this and reconfigure the pod security standard.   ... View more

SAS Mirror Manager can upload/push SAS images to some container registries like AWS ECR. I suggest to add an option to allow to delete/remove SAS images in order to be able to cleanup the container registry. For example, if I use SAS Mirror Manager to upload three SAS releases to AWS ECR: Stable 2024.04, 2024.05 and 2024.06. Now I want to delete all SAS images that belong to release Stable 2024.04 to cleanup my AWS ECR but there is no option in SAS Mirror Manager to do it. ... View more

Investigators using Procurement Integrity Visual Investigator Solutions (CMPI) on Viya4 need the ability to manage, assign, and route alerts at the scenario-fired event or incident level, not just at the entity level (e.g., vendor or employee).   Currently, Visual Investigator treats alerts as entities, meaning investigators must handle all scenario-fired events/incidents linked to an entity before closing an alert.   Disposition: Management has difficulty tracking progress because investigators need to address all events linked to an entity before an alert can be closed. Although investigators can manage a subset of events, they cannot disposition of individual scenario-fired events/incidents directly, only assess them.   Assign/Route: Investigators might need to review all incidents related to a specific scenario, such as multiple vendors sharing the same VAT number. Typically, investigator groups need to focus on specific scenarios, but the system currently routes all events associated with an alert together, making it hard to focus on individual scenarios.   Rollup: Incidents cannot be categorised under multiple alert types or strategies, which complicates the disposition and assignment processes.   Bulk Disposition: Users would need to export alerts to Excel, update disposition reasons and productivity ratings, and then upload the results back to Visual Investigator. This process is often faster than using the Visual Investigator interface directly, especially for repetitive tasks. For instance, an auditor reviewing instances where a vendor and an employee share a phone number would find it more efficient to use Excel than navigating through each alert individually.   ROI: Calculating ROI is challenging due to the lengthy implementation process (averaging 6 months) and the time required for system stabilisation and user training. The current process for capturing disposition at the alert level delays ROI reporting, which the sales teams need for end-of-year assessments and contract renewal. In some cases, solution rollouts have been delayed because clients cannot provide ROI figures on time.   These issues have been consistently encountered in all Viya/Visual Investigator implementations. Many of these features were available in the previous SAS Fraud Framework UI, and existing migrations cannot proceed until these issues are resolved, extending support for the older SAS Fraud Framework.   How does R&D receive client feedback and determine what is working or not working with the product? As SAS Partners, we do not have access to internal SAS systems and cannot log feature requests directly. ... View more

Hi,    Context:   Viya implemented in Azure using https://github.com/sassoftware/viya4-iac-azure. SAS admin team stated that Viya 4 does not support the use or configuration of a proxy.   Request:   To improve security posture, it will be beneficial for Viya4 to support the use of a proxy to inspect SSL traffic.   Note: Microsoft has a new feature available  (In Preview) for their Azure Kubernetes Services  which will allow to use custom CA. More information here:  Custom certificate authority (CA) in Azure Kubernetes Service (AKS) (preview) - Azure Kubernetes Service | Microsoft Learn| https://learn.microsoft.com/en-us/azure/aks/custom-certificate-authority     ... View more

There are time series animation available for Bar/Line/Geo-maps on SAS-Viya. This function (Animation) should be made available to any kind of graphs/plots and even Tables too. Particularly, I was looking to make a Custom graph using Butterfly plot adding this animation. I have managed to use bar-graph with animation instead of Butterfly plots but one-side of that graph shows negative values. Thank you in advance.   ... View more

Good morning, I would like to suggest the idea of ​​making aesthetic changes in SAS 9.4 to allow a more friendly transition for users of this platform to SAS Viya 4. It would be good to allow, as in other platforms, a retro and new look for users and administrators of the platform, in view of a progressive adaptation. Thank you, regards ... View more

SAS Viya 4 - IKS Compatibility IBM Cloud Kubernetes Service ... View more

I discovered in my latest tech support track: CS0136992 that client IP Address is only passed to the metadata logs for calls related to: New Client Connections  Redirects for the client in the cluster  AND - it cannot be configured to be added for other logging events! SAS Help Center: X Conversion Character I would like to request the ability to add Client IP Address as a descriptive characteristic to various Metadata Audit logging events such as:  Group/Role Changes Logon/Logoff Role Permissions Changes  Client IT teams often work with Splunk & other tools that query logs using a NoSQL query language. As duplicative as it may be - this allows IT teams to easily comply with security and tracking requirements to be able to easily track and identify cyber security events and get all information in a single query.    Without this - what I'm being told, is security teams would first need to identify the event in question, then using the request ID - track that all throughout the logs until they found the initial new client connection in order to find the source IP. This kind of sub-query is incredibly tedious behavior and creates a significant disconnect that must be manually traversed in order to create the wholistic picture cyber security teams are looking for.    Please include this as a feature in the next release!  ... View more

Hello,   Right now, when administrator wants to give access to a new user (and therefore he needs to revoke rights to some other user) he can revoke rights to a user that has open cases that are assigned to him.   I think it would be very useful for administrators to get a prompt that pops up when he tries to revoke the rights (for entering in SAS) for a user that has open cases.   Some window that will say to the admin that he first has to assign open cases to some other user before revoking rights to the current user.   Similar to prompts that can pop up when user tries to disposition the alert and he has to write disposition reason.   Thanks, David ... View more

Create a custom shortcut in Enterprise Guide 8.4 to "Send to Microsoft Excel"? You have to go to "Share"...Output Data... Send to Microsoft Excel. It would be nice to just use a shortcut or create a custom button to do this. ... View more

We are using SAS94M8 on Linux Grid platform.   As part of a project we would need to connect to  Teradata Vantage on GCP. Part of this migration will change the way clients use to connect to Teradata from LDAP to SAML based federated authentication approach. Can this feature of SAML based federated authentication be enabled or released for SAS94M8?   Documentation for configuring federated authentication on Teradata.   Configuration for Browser Authentication • Security Administration • Reader • Teradata Online Documentation | Quick access to technical manuals   End users would only need to provide the DSN name and the logmech (BROWSER or EXTERNALBROWSER) to connect to the database.  Teradata support the BROWSER mechanism on Windows and Mac OS only. ... View more

There should be an option to visualize data from two different tables into a single plot without having the need to join those tables. It should work by just mapping the connection between the two table. Why not join? Because join may create issues if the data is at a different hierarchy/ granularity level. ... View more

As discussed with the customer, the user need to add/edit some information related to the closed alert. Anyway, in SAS AML8.3 the system does not allowed user to edit the comment of closed alert. Please help to consider to add the function of 'add/edit comment to alert after the alert is closed' into SAS AML8.3   Thanks! ... View more

Refer to SAS AML8.3, the system is only allow the user to perform any actions on the most recent snapshots (SFEs) for the suspicious activity that has been discovered. This is not allowed the user to add/edit the information of the previous alert. This affects the work process of user as below 1) If the user record the wrong investigation or need to re-investigated the information in the previous alert. 2) The user need to see the attachment in alert level   So, the expectation from the customer are 1) When the new Alert is generated, the user should be able to ‘Edit’ some information in ‘the previous Alert’ such as.. ‘Rate productivity’ to put the comment (in Fired Event Level) for that alert 2) The user can distinguish between the attachment of alert level ... View more

This is a suggestion example. ... View more

Hi, I think it would be beneficial to have Generation Data group like dataset in SAS similar to the format used in Mainframe. Generation Data Groups (GDGs) are group of datasets related to each other by a common name. The common name is referred as GDG base and each dataset associated with the base is called a GDG version. You can set the limit of the related files(generations). We can easily keep track of all generation of data sets. Any particular generation can be referred easily. We use lot of datasets which regenerates daily , monthly , yearly etc..   Consider I need to create daily transaction data for the month of May. If Generation Data Group is available, I would define the base like "Tran_May2024".  Then I would just create dataset daily in the below way.   Data Tran_May2024(+1); -- This will create the next available version.  set work_tran_table; run;   If need to point current or earlier version  i would use the dataset below. Tran_May2024(0) - Latest Version  Tran_May2024(-1) - Previous Version  Tran_May2024(-2) - 2 versions back   If I need the whole month data ,  i just refer the base    Data work_tran_may; set Tran_May2024;   --This would all the version available in the base  run;   you can have options like below   LIMIT – To limit the maximum number of generations.   NOEMPTY – Uncatalog only the oldest generation in GDG when the limit is reached. EMPTY – Uncatalog all the generations when a limit is reached. SCRATCH -Physically delete the dataset(generation) which is uncataloged. NOSCRATCH – Don’t Physically delete the dataset(generation) which is uncataloged.   This would help a lot when we create lot of datasets which are created in a repeatable fashion.    Thank Ravi                ... View more

We are currently using SAS Visual Forecasting for a large-scale forecasting project.  In this project we are using the interactive modeling node to develop custom models.  We have observed in this node that there are almost no options for exploring relationships between your dependent variable and exogenous features.  This makes it very hard to determine which factors to add to the models and in what way to transform them while adding (lag/numerator/denominator).  We would like to see additional visualizations added to the product to allow us to experiment with X/Y transformations, view cross series plots, and explore relationships between the data across different points in time (Cross Correlation Function Plots).     SAS Forecast Studio has these capabilities, however that functionality does not appear in the SAS Visual Forecasting product.    We are on the following version of SAS Studio: Stable 2023.12  ... View more