This is a second thing I'll go ahead and submit a bug for. The processes can just pick up a text file with JSON in it.Īlso, Wilson, for creating and updating environment variables via AutomateC, the command or switch is /setev. So that's something else you could consider if you're allowed to. Since then, I've pretty much stopped using Environment Variables, and we use CONFIG files now for each automation. I've never tried using AutomateC to update an environment variable that would contain JSON. I believe it's a bug, and now that I think about it, I should probably submit that as a bug so Blue Prism is aware of it. If I remember right, I had the same issue with certain datatypes such as Date and DateTime when setting Environment Variables via AutomateC. Looks like Eric has already addressed a couple options you have, so I'll just mention what else I can think of. The table of interest would be BPAEnvironmentVar.Ģ) The other option would be to create a UI automation for the actual Interactive Client, so you would create the necessary application model for starting the Interactive Client, navigate to System -> Processes -> Environment Variables or System -> Objects -> Environment Variables and perform the update of the variables via the UI. Then you could use the Data - SQL Server VBO to connect directly to the Blue Prism database and update the specific environment variables using SQL. So it seems you have two options:ġ) You could read your batch file in using regular BP objects such as the Utility - File Management VBO. There's an action available on AutomateC utility for deleting environments variables, but nothing that I see for creating. I don't believe we expose an object or API for setting the value of environment variables.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |