Feedback Print



With this interface, you can set the common attributes of the app.

Application Configuration Interface Application Settings Interface

  • Attributes
    • Application Code : It is the name that defines an application. An app can be renamed at the List of Application.
    • Description : This field contains a brief description of the application objectives.
    • Documents Path : The absolute path to store uploaded documents in the application.
    • Image Directory : The filesystem directory to store the application images.
    • Application images : Import images into the application to allows using them in the application.
    • Language : Set the default language of the application. Display all the application hints and messages in the selected language.
    • Share Location Variable : Define if the app shares the regional settings with other applications through a session variable.
    • Charset : Define a specific charset to use in the application.
    • Share Theme Variable : Define if the app shares the Theme settings with other applications through a session variable.
    • Folder : Define the project folder that contains the app.
    • Edit by Project : Define if other project developers can edit the application.
    • Timeout : Set the session runtime timeout in seconds. If the value is Zero, it assumes the default timeout of the PHP.
    • HelpCase Link : It allows to associate a HelpCase file with the application.

Notification Settings

Notification Settings Interface.

  • Use SweetAlert: Use the SweetAlert to display messages from the application. When this option is active, it will replace the browser’s “confirm” and “alert”.
  • SweetAlert position using Toast : The position to display error messages on the application.

  • Error Position on the field : The position to display error messages when criticizing the field.
  • Show the Error Title in the Application : Define to display the title line of the error message or not.
  • Show the Error Title in the Field : Define to display the title line of the error message in the field or not.

  • Script Error : Allows displaying the line code where there is an error..
  • SQL Error : Allows displaying the SQL statement if it got an error.
  • Debug Mode : Runs the application in Debug mode, showing all SQL statements the application is executing.
  • Ajax Error Output : Enables the Ajax alert for debugging errors.


Defines the attributes of the navigation of one application to another.

Navigation Interface. Navigation Interface.

  • Attributes
    • Exit URL : URL on which the user will be redirected when exiting the application.
    • Close on Exit : When exiting the application, close the browser window.
    • Redirect URL : URL to redirect in case there isn’t any global variables available.
    • Redirect Variable : Name of the variable that’ll be stored the URL of a real application.


On this screen, you can redefine the default application messages to the end-user by customizing the validation messages for Insert, Update, and Delete. You can also define messages for SQL errors and the confirmation outputs.


Messages Interface Messages.

No Records Message

The message displayed when the application has no records.

Primary key violation

The message displayed when there is a violation in the database’s primary key constraint.

Unique key violation

The message displayed when there is a violation in the database’s unique constraint.

Insertion Messages

Insertion Interface Messages.

Message After Insert

The message displayed when inserting a new record.

Message to Confirm Insert

The message displayed if the end-user wants to confirm the inserting of a new record.

Update Messages

Update Interface Messages.

Message After Update

The message displayed when updating a record.

Message to Confirm Update

The message displayed if the end-user wants to confirm the changes of a record.

Messages of delete

Delete Interface Messages.

Message After Delete

The message displayed when deleting a record.

Message to confirm Delete

Displays a customized message asking to confirm the record deletion.

If you make no changes, the application will use the default values for the messages. Those values can be configured in Locales -> Application Language.

Global variables

This screen shows the global variables in the application.

The global variable is an external parameter required for running the application. The application can include global variables in the WHERE clause, field definitions and names, event programming, and so on.

Global variables are defined in brackets ([variable]). These variables must be passed to the application being implemented through one of the methods: Session, Post, and Get

if you need to use Database Identifiers in or tables, we recommend using the double quotation marks( ) instead of the brackets( [ ] ) because of the conflict with the Global Variables syntax of Scriptcase. Using the brackets as database identifiers may lead to problems in the Scriptcase applications.

Global variables Interface. Global variables Interface.


Select CustomerID, CustomerName from Customers WHERE CustomerID = '[v_customerid]'

We do not recommend using session variables (global variables) with the same name as the table fields.

In this case, the variable v_customerid appears in the global variables configuration.

Global variables configuration Interface. Global variables configuration Interface.

Shows all global variables used in the application

  • Attribute : name of the variable in the application.
  • Value : Defines the behavior of the variables, this content is divided in three blocks, they are:
    • Scope : Defines how the variable is received by the application. If a variable has been defined that it’s received by a POST method and has been approved by the GET method, the content is not accepted. Methods of passing variable values:
    • Session : In this option, the variable must be created as a PHP session variable by another application.
    • GET : Defines that the variable must be passed by the URL, that is, visible by the browser.
    • POST : Defines that the variable must be passed through the POST method of a HTML form.
    • Settings : Does not validate (check) the variable at runtime.
    • Type (In / Out) : Defines whether the variable is input or output.
  • Description : Indicates where the variable is being used.