Release 5.6
Improved Security for Interface Scripting Language (ISL) Scripts
This release improves security for importing and running Interface Scripting Language (ISL) scripts. If you are upgrading to this version of RES, the installation wizard automatically imports scripts from the local directory. Starting with this release, use the ISL Files menu in the POS Configurator to add .ISL files containing the scripts:
1.In the POS Configurator, click the Devices tab, and then click ISL Files.
2.To change the folder containing the custom script files, click Dir and select the folder. By default, the POS Configurator is set to look in \MICROS\Res\Pos\Etc3.To import and create a database entry for all .ISL script files in the selected folder, click Auto Load All ISL Files.
4.To import a single script, click New, and then click the Browse button to select the .ISL file.
5.To change the file for an existing database entry, select an entry, click the Browse button next to the File Name field, and then select the new script.
6.To make changes to an imported .ISL file, click Enable Developer Mode, and then make changes in the text field. Click Cancel Developer Mode after making changes. See below for more information.
ISL Security Developer Mode
ISL developers can enable Development Mode, which allows local changes to an ISL file to be implemented by the POS immediately during the development cycle. Developer Mode can be set to the following states:
•Active Developer Mode: The developer can make changes to the local file and to be effective immediately at the POS. The system will not load and override the file content from the RES server. By default, Active Developer Mode is enabled for one hour, after which RES expires developer mode and stops loading changes to the file. You can renew developer mode if more time is needed.
•Expired Developer Mode: The developer can use the last loaded version of the file, but subsequent changes to the local file will be ignored. The system will not load the file from the RES server to avoid overwriting the changes made to the local file until the developer is ready.
Cancel Development Mode allows the file to be pulled down again from the database to the workstations.
Important:
To allow files to be altered without being overwritten, the system will not download information from the micros.isl_file_def table for files that have been placed in development mode until Cancel Development Mode is clicked. The system overwrites the local file with content from the micros.isl_file_def table immediately when development mode is canceled. To preserve file changes, you must load the file into the database before clicking Cancel Development Mode.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.