Hahaha! Fair, I may or may not have heard that same feedback. 😃
Looks like I spoke too soon anyway. I went back, and it seems that I am smarter than my past self and I just tried a few different string formats for inputs to setting date and date time. Here's a batch script that works for date, datetime, time, timespan, text, number, flag, password:
Ok, so it's super important that you get the strings EXACTLY in the right format when setting these. If you set one of these Date/Time-related environment variables incorrectly, your Environment Variables screen will look like below. Don't worry though. First, don't test this in a shared environment for the first time. Second, if this happens, you can delete the environment variables from the database pretty easily and no harm has been done.
Now that the warning is out of the way. It seems I cannot choose Batch as a language type for this code below. Don't be fooled. It's not VB even though I chose that. 😃 I left the username and password in the script on purpose. If anyone is reading this who isn't familiar with Batch or AutomateC commands, replace the "dave" values with your actual username and passwords if it's Blue Prism Native authentication. If you're using Blue Prism at an enterprise level, then you're probably using SSO. Replace "/user %username% %password%" with "/sso" if you authenticate with SSO.
Example:
AutomateC /sso /setev "Sample Date Env Var" "Date" "2021-10-14" "Test Description"
Anyway, here's the script for anyone who is having issues with setting certain environment variable datatypes by AutomateC. Just copy the text into a text file and rename the file to have a file extension of .bat.
Note that the Date and other formats are possibly a regional thing. I have no idea. But, I believe the best thing for you to do is to create environment variables in the UI first, and then go look at the values in the database using SSMS and that will show you the exact format that the strings need to be in for them to be interpreted correctly.
------------------------------
Dave Morris
Cano Ai
Atlanta, GA
------------------------------
Looks like I spoke too soon anyway. I went back, and it seems that I am smarter than my past self and I just tried a few different string formats for inputs to setting date and date time. Here's a batch script that works for date, datetime, time, timespan, text, number, flag, password:
Ok, so it's super important that you get the strings EXACTLY in the right format when setting these. If you set one of these Date/Time-related environment variables incorrectly, your Environment Variables screen will look like below. Don't worry though. First, don't test this in a shared environment for the first time. Second, if this happens, you can delete the environment variables from the database pretty easily and no harm has been done.
Now that the warning is out of the way. It seems I cannot choose Batch as a language type for this code below. Don't be fooled. It's not VB even though I chose that. 😃 I left the username and password in the script on purpose. If anyone is reading this who isn't familiar with Batch or AutomateC commands, replace the "dave" values with your actual username and passwords if it's Blue Prism Native authentication. If you're using Blue Prism at an enterprise level, then you're probably using SSO. Replace "/user %username% %password%" with "/sso" if you authenticate with SSO.
Example:
AutomateC /sso /setev "Sample Date Env Var" "Date" "2021-10-14" "Test Description"
Anyway, here's the script for anyone who is having issues with setting certain environment variable datatypes by AutomateC. Just copy the text into a text file and rename the file to have a file extension of .bat.
set username=dave
set password=dave
cd /d "C:\Program Files\Blue Prism Limited\Blue Prism Automate"
AutomateC /user %username% %password% /setev "Sample Date Env Var" "Date" "2021/10/14" "Test Description"
AutomateC /user %username% %password% /setev "Sample DateTime Env Var" "DateTime" "2021-10-14 20:59:59Z" "Test Description"
AutomateC /user %username% %password% /setev "Sample Time Env Var" "Time" "23:59:59" "Test Description"
AutomateC /user %username% %password% /setev "Sample TimeSpan Env Var" "TimeSpan" "7.23:59:59" "Test Description"
AutomateC /user %username% %password% /setev "Sample Text Env Var" "Text" "Test Value" "Test Description"
AutomateC /user %username% %password% /setev "Sample Number Env Var" "Number" "42.42" "Test Description"
AutomateC /user %username% %password% /setev "Sample Flag Env Var" "Flag" "True" "Test Description"
AutomateC /user %username% %password% /setev "Sample Password Env Var" "Password" "Secret" "Test Description"
PAUSENote that the Date and other formats are possibly a regional thing. I have no idea. But, I believe the best thing for you to do is to create environment variables in the UI first, and then go look at the values in the database using SSMS and that will show you the exact format that the strings need to be in for them to be interpreted correctly.
------------------------------
Dave Morris
Cano Ai
Atlanta, GA
------------------------------
