SAP Build Process Automation | Environment Variables

[hrshjrwl]

Hello SAP BPA Experts!

I am trying to use Environment variables in automation. However, while testing it is not showing any value.

Appreciate, if anyone can guide what I am missing here.

Regards

Harsh

[maheshpalavalli]

When this happened to me the last time, I installed the latest bot version on the Windows machine, and it got fixed. You can try that as well.

[hrshjrwl]

My desktop agent version is 3.13.43.

[Dan_Wroblewski]

Sorry I can't think of anything. I just did and it

(1) Create Environment variable

(2) Add Log Message printing out variable

(3) Run test

(4) Enter value

I tried to make it not work but wasn't able to 🙂

[hrshjrwl]

Thanks Daniel and Mahesh for you comments.

I tried updating my Desktop agent and test automation again it failed. So, I capture traces and found some error during agent startup. Could you please suggest what can be reason behind it?

I suspect it has something to do with

"XsWrkMng2.dll in SAPDesktopAgent.exe CxCryptOffEnv::AgentTenantStartup : ImportBlobBase64 failed[w]"

[tatsiana_nikifarava]

I also have the same issue with destination environment variable - its value is not visible during automation test. Environment variables values of other types (like number or string) are passed correctly. Due to that issue I cannot call an action to BTP service from automation.

I've tried to call the same actions from business process - all works fine. I've followed all rules from documentation:

• created an environment variable;
• pass this variable as an input parameter for the action in automation
• during automation test select correct destination from the dropdown list
• using the latest version of desktop agent 3.23.56

archana.shukla and chaitanyapriya.puvvada , could you please help with this?

Kind regards,

Tatsiana.

[Chaitanya_Priya]

Hi Tatsiana Nikifarava

I have checked it and every thing works as expected.

Make sure you have mapped the parameters correctly. The Environment variable is also printed in the LogMessage.