Рождественские праздники компании
Североамериканская штаб-квартира в Майами, США: 25 декабря 2015, 1 января 2016
Европейская штаб-квартира в г. Мюнстер, Германия: с 21 декабря 2015 по 3 января 2016
Ограниченная поддержка доступна в течение этого периода.
PROVISIO желаем вам веселого Рождества и счастливого Нового Года!

 

Запрос поддержки: Some challenges during evaluttion

Описание

Hello,
I am evaluating SiteKiosk for a hospital application. So far your solution comes the closest to meet all our needs, but I have a few remaining challenges blocking me from making a purchase decision.

My configuration needs to run three applications:

1. Chrome pointed to our cloud hosted solution
2. QZ Print: A java based tray application that allows our web app to send data to a printer connected via USB port
3. A Windows App that handles USB input from a proprietary barcode reader

I am hopping you can help with the following remaining challenges:

A. Surfing Area configuration is blocking my Web application from accessing the QZ-Print tray application

My application issues a request using a custom scheme. The request appears in Chrome debug window and on SiteKiosk debug window as:
qz:launch

Note that the request does not include // after the custom qz: scheme. This behavior is not under my control.

I have tried configuring Surfing Area by allowing:
*://*
and also by adding a entry to the sample-allowed.txt file with the value:
qz:launch

Is there something else I can do to prevent SiteKiosk from raising ERR_UKNOWN_URL_SCHEME?

B. Strange behavior on QZ Tray startup

I have configured QZ Tray to be launch via the SiteKiosk toolbar. Since QZ Tray is a java application, I what SiteKiosk actually launches is .cmd file which launches the application .jar via the java executable.

When I launch the application from the SiteKiosk toolbar it launches correctly and appears in the SiteKiosk replacement shell Tray area, but the cmd.exe window that launched the java process remains visible. It needs to be manually minimized, and even then, it can be seen in the SiteKiosk programs toolbar.

BUG?: Sometimes I cannot manually close the cmd.exe window. The mouse movement is blocked so that I cannot reach the minimize window icon.
Could this be related to trial 30 second mouse blocks?


Is there a better way to launch a java tray app or to avoid the visible cmd window?

C. QZ Tray Access to the USB port

Once my application can communicate with QZ tray, will it be able to list system printers and get access to the USB port?
Does that require any additional configuration on SiteKiosk?

D. Minimizing the Barcode Reader App

The barcode reader app launches as expected from the SiteKiosk programs toolbar and functions correctly. The application becomes visible when clicking the button on the toolbar and can be hidden by minimizing the application window.

Is it possible to minimize a Windows app launched from the toolbar by clicking on the toolbar button?

I have a requirement that the user should not be able to terminate the barcode reader app. Currently the user can do so by clicking the X on the application Window.

Can SiteKiosk help with preventing the closing of the app, or ensure it is restarted if the user closes it?

E. Trial Limitations
The fact that user can exit from SiteKiosk trial without password is very reasonable, but the repeated 30 second blocker is very frustrating for someone really trying to evaluate your software. Is there a way to bypass or get a temp eval key?

Ответ: (1)

Re: Some challenges during evaluttion 08.09.2020 15:50
Hello,

Thank you for your enquiry. Addressing the issues with your project, you can review these suggestions:

>>>A. Surfing Area configuration is blocking my Web application from accessing the QZ-Print tray application<<<
- SiteKiosk is a secure browser and will not allow all protocols by default (SiteKiosk only allows certain protocols / schemes by default).
But you can allow that protocol by editing the SiteKiosk configuration file. See example in this post: https://www.provisio.com/en-GB/CustomerSupportCenter/ArticleDetails.aspx?ArticleID=24475

>>>B. Is there a better way to launch a java tray app or to avoid the visible cmd window?<<<
- Alternatively, you could test executing your Java Application directly in the Application List(e.g. with using “java –jar YourApp.jar” or "C:/WINDOWS/system32/javaw.exe -jar YourApp.jar”). See example post: http://www.provisio.com/en-US/CustomerSupportCenter/ArticleDetails.aspx?ArticleID=8335

Usually the CMD window is blocked by default with the Windows & Dialogs management:
https://www.provisio.com/en-US/CustomerSupportCenter/ArticleDetails.aspx?ArticleID=5676

Troubleshooting Guidelines for Using External Applications with SiteKiosk Windows:
https://devblog.provisio.com/post/2015/05/15/Troubleshooting-Guidelines-for-Using-External-Applications-with-SiteKiosk.aspx

>>>C. QZ Tray Access to the USB port<<<
-SiteKiosk does not block or deactivate USB ports.

>>D. Can SiteKiosk help with preventing the closing of the app, or ensure it is restarted if the user closes it?<<<
-Yes, but with additional JavaScript coding. Here is a post in our Developer Blog. Please be mindful that articles posted here are considered as-is and further coding customization is not provided.
Dev Blog post: https://devblog.provisio.com/post/2017/12/18/How-to-Build-an-Extended-Script-Watchdog-for-External-Applications.aspx

>>>E. Is there a way to bypass or get a temp eval key?<<<
-An email will be sent to you with further instructions.

Best regards,
Andre.