Page 1 of 1

Getting User Profile in Atrium to open a folder

Posted: Mon Jul 30, 2018 2:27 pm
by PaulT
We are using Atrium along with Genie. One Atrium menu option I would like to give the users is the ability to open a network folder that has the same name as their user profile. We place users' ad-hoc reports from the IBM i as PDFs into their folder. So it would be nice to give them an Atrium menu option that will open their folder. What would be the best way to add this functionality?

Re: Getting User Profile in Atrium to open a folder

Posted: Mon Jul 30, 2018 2:33 pm
by PaulT
As a follow-up to this. I am getting an error in the browser when trying to execute a pc Command from Atrium.

"e.runCommand is not a function"

I specify that the option is a 'PC Command' and I enter a very simple command Notepad.exe

Re: Getting User Profile in Atrium to open a folder

Posted: Thu Aug 16, 2018 3:26 pm
by PaulT
I found references to the runCommand error and am implementing the command listener.

Re: Getting User Profile in Atrium to open a folder

Posted: Thu Aug 16, 2018 3:34 pm
by PaulT
This is still an issue.
I am trying to run a PC command from Atrium and I get an error.
For the moment I am just trying to kick off Notepad to do a 'proof of concept'
Action Type: PC Command
PC Command: notepad.exe

When I try to run this in Atrium I get this message in the browser error window (Chrome):
Unable to execute "notepad.exe"
Type Error: e.runCommand is not a function.

Am I being dense?

Re: Getting User Profile in Atrium to open a folder

Posted: Thu Aug 16, 2018 4:55 pm
by Emily
Hi Paul,

Support followed up with you through email on this issue. It looks like you are using quotation marks around your PC Command. This isn't necessary when running the command through Atrium. You should try removing the quotation marks and try running the command again. This should solve the problem that you are having.

Thanks!

Re: Getting User Profile in Atrium to open a folder

Posted: Thu Aug 16, 2018 5:49 pm
by PaulT
Yes, thanks Emily. Your information did the trick:

It's possible that you're seeing this error because you don't have your PC Command Listener configuration options set for your instance. You will need to make sure that you are using the following configuration options in order for this command to work properly:

pui["pc listener port"] (http://www.profoundlogic.com/docs/displ ... tener+Port)
pui["use pc listener"] (http://www.profoundlogic.com/docs/displ ... C+Listener)

If you're using this in Atrium, you'll want to put these configuration settings in a JavaScript file and place the file in the following directory:

/www/InstanceName/htdocs/profoundui/userdata/extension/atrium

Without setting these options, Profound UI will try to use the PC Integration Applet by default (instead of the Command Listener) and could cause the error that you are receiving.