topic RE: Resource PC Commands - outputs in Product Forum

Resource PC Commands - outputs

l.kiciak — Wed, 20 Jul 2022 08:19:00 GMT

Hi guys,

does anyone of you was using the outputs command from Ressource PC Commands?
My goal is to get termination reason for a session without accessing database.

From the command description it should be doable, but when I execute it on various session ids, I'm receiving the response: SESSION NOT FOUND. The session id can be found in database though...
The only case, when it worked is when I create and run a session using PC Commands, then output for the session is found.

Is there any limitation for outputs? For example: it's only applicable for sessions created via Resource Commands? Or am I missing something?

Best,
Ł

------------------------------
Łukasz Kiciak
RPA Developer
UI
Europe/London
------------------------------

RE: Resource PC Commands - outputs

hossein.azimi — Tue, 26 Jul 2022 22:54:00 GMT

Hello Łukasz

Thank you for contacting the Blue Prism community.

Can you please provide a sample command you use and also the snapshot?

------------------------------
Hossein Azimi
Customer Support Engineer, APAC
Blue Prism
Sydney NSW
------------------------------

RE: Resource PC Commands - outputs

l.kiciak — Wed, 27 Jul 2022 12:59:00 GMT

Hi Hossein,

sure!
The request looks as follows:
http://{myResource}:8181/user name {myUserName}&password {myPassword}&outputs {mySessionID}

Variables in curly braces are replaced with valid and existing values.

Best,
Ł

------------------------------
Łukasz Kiciak
RPA Developer
UI
Europe/London
------------------------------

RE: Resource PC Commands - outputs

ewilson — Wed, 27 Jul 2022 16:30:00 GMT

This format worked for me:

http://{Resource IP}:8181/user name {USERNAME} password {PASSWORD}&outputs {SESSION ID}

It looks like you have the '&' in the wrong spot - meaning there should not be an ampersand before password.

Cheers,

------------------------------
Eric Wilson
Director, Integrations and Enablement
Blue Prism Digital Exchange
------------------------------

RE: Resource PC Commands - outputs

l.kiciak — Thu, 28 Jul 2022 11:49:00 GMT

Hi Eric,

thanks for your feedback!
Unfortunately it's not the case for me. Without ampersand before password I cannot authenticate the user.
Full response for: http://{myResource}:8181/user name {myUserName}&password {myPassword}&outputs {mySessionID}

USER SET
USER AUTHENTICATED
SESSION NOT FOUND

Full response for: http://{Resource IP}:8181/user name {USERNAME} password {PASSWORD}&outputs {SESSION ID}

USER SET
USER NOT SET

Currently I'm using BP version 6.6.

Best,
Ł

------------------------------
Łukasz Kiciak
RPA Developer
UI
Europe/London
------------------------------

RE: Resource PC Commands - outputs

ewilson — Thu, 28 Jul 2022 13:14:00 GMT

That's interesting. If I run the command w/o the ampersand before password I receive:

USER SET
OUTPUTS:<outputs><output name="Final Loop Count" type="number" value="3" /></outputs>

If I add the ampersand before password then I get this output:

USER SET
USER AUTHENTICATED
OUTPUTS:<outputs><output name="Final Loop Count" type="number" value="3" /></outputs>

Have you tried breaking this up into two separate requests? In other words, send the user name password combination in the first request which should render the USER SET and USER AUTHENTICATED responses. Then immediately send the outputs {session id} request.

Cheers,

------------------------------
Eric Wilson
Director, Integrations and Enablement
Blue Prism Digital Exchange
------------------------------