The bug number is AM-23637 for this issue. We will let you know once the bug has been corrected and a new release of the software is available.
This isn't possible. The only way to change the value of a variable if from within a task.
Automate supports .pem certificate files which from what I could gather is what is used for mTLS.
Privacy Enhanced Mail Certificate (.pem) - Base64-encoded certificate file, such as a PEM-encoded X509 certificate; used to authenticate a secure website; typically imported from a Unix-based Apache Web server and compatible with OpenSSL applications. PEM certificate files are generated automatically and are not meant to be opened or edited manually.
It's possible to query Excel files. Excel and Automate will need to be the same bit-version and you'll need to install the MS Access Database Engine. You can then use the "SQL Query" action in Automate and select the "Connection String" type option.
You can find connection strings here (look under the "Microsoft ACE OLEDB" section for Excel).
Here's an example step i was able to use to query a XLSX file:
<AMDATABASE ACTIVITY="sql_query" CONNECTIONTYPE="connection_string" CONNECTION="Provider=Microsoft.ACE.OLEDB.12.0;Data Source=C:\Users\dcannon\Desktop\simple.xlsx;Extended Properties="Excel 12.0 Xml;HDR=YES";" RESULTDATASET="ds" SQLQUERY="select * from [Sheet1$]" />
Ok thanks for all the examples. I submitted a bug to our development team for this. I'll get back to you when a bug number is assigned.
I did a quick test in AM 10.7 and 11.5 and 10.7 returned 1 "RowsAffected" from the INSERT statement, but 0 for the UPDATE statement. 11.3 returned 0 for both INSERT and UPDATE.
I'll have to test this more, but this is not what you're seeing, correct? 10 was returning a value greater than 0 for the UPDATE? Which version of 10 are you using?
Wildcards aren't able to be used in the attributes section. There needs to be a specific value for Automate to look for. It's possible to use variables in the attributes, but the variables would need a specific value.
Moving to AWS shouldn't be any different than moving Automate to a different on-prem system. If you need help with the transition, please let us know. You will need to have a new license created for the new Automate installation. You can request a license change here:
There isn't a method to do this with FTP as far as I know. The only solution I can think of would be to setup the task to loop through the folder and then loop through any subfolders. This may not be too feasible if the folders go deep and/or the subfolder depth is unknown.
Sorry, I don't know much with PowerShell scripting. Can you try using the "HTTP (Get/Post)" actions in Automate to make the call. Or there's a popular third-party program called Postman that is used to make calls as well.
I see you turned on and added your user to the API Security. Did you grant your user permission as well in that section? There's permissions that need to be enabled that might require the window to be scrolled down to see.
Are you able to manually run the "LoggingTest" task when logged into Automate as that user as well?