-
Re: Idea on values that can be passed by the interface for plugin.source
Nic Meadows Apr 18, 2013 3:13 PM (in response to Owen Dickenson)1 of 1 people found this helpfulHi Owen,
We have had very little luck using PlugIn,Source in the past, it is more often than not not populated. I have recently found out that it is only likely to be populated by devices that use the EDI call LoginUser2 (available from Uniprint v8.0) Earlier versions of the iMFP software (and even some recent ones) are using LoginUser rather than LoginUser2, which doesn't provide this information. Therefore the PlugIn.Source is not particularly reliable.
Typically the return results are "Keyboard" and "CardReader"
Regards
Nic
-
Re: Idea on values that can be passed by the interface for plugin.source
Paul Klump Apr 18, 2013 3:14 PM (in response to Owen Dickenson)1 of 1 people found this helpfulOwen,
You could add various instances of the IO.PrintLine command throughout your script to determine of the value of the PlugIn.Source interface:
Example:
IO.PrintLine("*** This is the current value of PlugIn.Source: " + PlugIn.Source);
...
... Some other code
...
...
IO.PrintLine("*** This is the current value of PlugIn.Source after my code block: " + PlugIn.Source);
If you have logging turned on, you should see the output turning up in the logs. You could disperse them throught the script to determine as necessary to see if the value of Plugin.Source changes during the login.
Paul
-
Re: Idea on values that can be passed by the interface for plugin.source
Owen Dickenson Apr 18, 2013 3:14 PM (in response to Paul Klump)Hi Nic, Paul
Thanks for your responses. It's a shame those values aren't reliable. I was rather hoping to be able to look at that value to determine the codepath, rather than use a regexp to find usernames/ ID card identifiers.
One to rememeber for future code I guess.
Owen.
-