Known issues - Automate_Studio_Manager - Latest

Automate Studio Manager Release Notes

Product type
Software
Portfolio
Integrate
Product family
Automate
Product
Automate > Automate Studio Manager
Version
Latest
ft:locale
en-US
Product name
Automate Studio Manager
ft:title
Automate Studio Manager Release Notes
Copyright
2026
First publish date
2018
ft:lastEdition
2026-08-11
ft:lastPublication
2026-08-11T10:01:42.685000
L1_Product_Gateway
Integrate
L2_Product_Segment
Data Integration
L3_Product_Brand
Precisely Automate
L4_Investment_Segment
SAP Automation
L5_Product_Group
Winshuttle Enterprise
L6_Product_Name
Automate Studio Manager
Automate Studio

  • When the SAP server is defined as SAML EIS on Studio Manager, and the User Name field contains {email} instead of an actual email ID, the SAP Data APIs fail to run and return the error: Logon details are incomplete/incorrect. Please enter the logon details to continue with SAP logon.

    Impact: This issue affects both current and legacy releases.

    Workaround: Use a valid email ID in the User Name field to establish a successful connection and enable SAP Data API functionality.

  • A Teamspace user can view the version history of a document via the document link in an assignment email, even when the document is not displayed to the user.
  • Number of records limit set under policy is not enforced for SAP API bulk data posting via API run and Studio run.
  • The SAP API Data file name shown on the API Usage page differs from the one displayed on the Documents page.
  • The Upload Type column displays a blank value for Query scripts in SAP API, however, there is no option to apply filter on it in the grid.
  • The Assign/Revoke AD groups option is not available for License Admin users on the Licenses page.
  • In Automate Studio Manager version 25.0, the control has been updated to WebView2 from the earlier .NET browser control, which enables a horizontal scroll bar to function across different resolutions. However, the scroll bar appears even when not needed.
  • Deleting the API Usage - Detail View report from the Reports page removes the API Metering Usage chart from the homepage. Once removed, the chart cannot be re-enabled even after recreating a new API Usage - Detail View report.
  • When an input payload is sent via V1 and V2 API, such that the payload is associated with a solution other than the solution mentioned in the payload, then, no error will be shown. Also, the response will be incorrect and have an unexpected format.