External Commands
The VIS9® allow users to call several external commands.
The basic syntax is:
| 1. | http://localhost/?<external command> |
For example try this at VIS9 developer DEMO system:
| 1. | http://vis9.cz/demo/?about |
(this command will shows info about current VIS9 system)
Resets all local VIS9® settings for your currrent browser. For example it will be cookies for language settings and user session id.
Example:
| 1. | http://vis9.cz/demo/?reset |
As result you will see base app set by your VIS9 administrator:
List info about current system
Example:
| 1. | https://vis9.cz/demo/?about |
The result may be something like this:
| 1. | osSystem:VIS9 |
| 2. | osVersion:Thor's |
| 3. | osRelease:YGU18JTCJCAXAX3VGEWXWGNB |
| 4. | osBuild:9.3.2926 |
| 5. | osUsage:DIRECT |
| 6. | osMode:DEMO |
| 7. | osDateGregorian:20240929074125 |
| 8. | osLicence:HOME |
| 9. | osLicenceId: |
| 10. | osLicenceCompanyLocation: |
| 11. | osLicenceCompanyNumber: |
| 12. | osLicenceCompanyName: |
Returns unique ID for your external projects. This ID may be user for laset use at VIS9 system. This ID will be always unique at your system.
This code will not be repeated ever again
Example:
| 1. | https://vis9.cz/demo/?taskid |
The result may be something like this:
(The VIS9® has internal decoding process which can sort this ID like path. So, you can be sure, there is no same ID in the system).
This can be called internaly in your programs like:
- vis9taskCode();
- vis9taskPath(code);
Trough function vis9taskPath(code) has the VIS9 perfect system for sorting folder structure compatible with this code. You can use freely for more then 1000years since 1970.
Returns unique ID for your external projects. This ID may be user for laset use at VIS9 system. This ID will be always unique at your system.
Syntax:
| 1. | https://vis9.cz/demo/?qrcode&code=<your code> |
Example:
| 1. | https://vis9.cz/demo/?qrcode&code=https://www.vis9.eu/ |
The result may be something like this:
Let capture status of the device for VIS9®Farm monitoring purposes. For more info consider manual for this functionality
here.
Syntax:
| 1. | http://localhost/?capture&id=<id of monitored system>&status=<status number>&name=<additional info for status> |
