Go to Scriptcase store

# Application Settings (Blank Application)

## Settings

#### Application Code

Informs the current name of the application and the version in which it was created

#### Application title

Defines the application title, which can be set dynamically using langs or with a fixed text.

> In this option it is also possible to use langs, for a system with multiple languages. Click here and see how to configure the langs

###### Example of the application title

#### Friendly URL

This attribute defines the application’s friendly URL.

Alphanumeric characters and some special characters are allowed, such as: hyphen (-), underscore (_), comma (,), and dot (.).

> The use of accents or spaces is not allowed.

Some recommendations for definition are:

- Use keywords for identification.
- Use hyphens to separate words.
- Use only lowercase letters.
- Avoid using dates.

##### Example of an application using a Friendly URL

> The friendly URL can also be defined in the application list on the project’s initial screen.

###### See the example below

#### Description

Displays the description of the application.

You can edit or add a description also in the Project Explorer interface.

#### Application images

It stores the images that will be used in the application through codes in the events, causing these images to be sent along with the application at the time of publication.

Only images used in codes, such as creating a dynamic menu with icons or creating a bill of exchange using a blank, need to be added.

Images added in HTML Image fields or in the application header, for example, are already sent with the applications.

> The added images will be stored in this directory: ../_lib/img/

How to use the images

When inserting the image in the image manager, its name is changed according to the scope (public, project or user) and the storage directory (background, button, icon, menu or general) following the following pattern.

Scope: It refers to the level of access to the file within Scriptcase, in the development environment.

- Scriptcase__ - Contains preexisting images in the tool, where it is not possible to upload new images.
- Public__ - Images accessible for all projects.
- Project__ - Images accessible only in the project in which it was inserted.
- User__ - Images accessible only to the user who uploaded the image.

Each scope adds a prefix to the image name.

- Public - sys__NM__
- Project - grp__NM__
- User - usr__NM__

Storage Directory: Directory where the image will be added. Each directory adds one more prefix to the image name.

- background images - bg__NM__
- button images - btn__NM__
- general images - img__NM__
- icons - ico__NM__
- menu images - menu_img__NM__

This way, an image called _001.jpg, added in the public scope and in the icon directory will be named sys__NM__ico__NM__001.jpg

#### Language

Defines a specific language for the application, overriding the default language defined in the project. If no language is selected, the application will inherit the project’s default language.

> The languages listed in the option are defined in the project properties

#### Use Shared Localization Variable

Defines if the language of the applications will be stored

#### Charset

Defines an application-specific charset.

If no value is selected, the application inherits the project’s default charset.

> Ideally, this charset option, within the application’s settings, does not have a defined value. Different usage of your base charset can cause problems saving information in your tables.

#### Share Theme Variable

When active, this option allows the theme stored in the session to be used by the application.

For example, by selecting theme x at login, all applications in the project will use the selected theme.

If the option is unchecked, the application remains with its original theme.

#### Folder

Folder where the application is stored in Project Explorer.

#### Editing by Project

By disabling this option, only the user who created the application will have access to its settings.

No other project users will be able to access the application.

In the image below, the menu application has the edit by project option disabled.

#### Timeout

Set the session runtime timeout in seconds. If the value is Zero, it assumes the default timeout of the PHP.

## Notifications Settings

#### Use SweetAlert

Activate SweetAlert in the application, replacing the “confirm” and “alert” of the browser.

Confirm Example with SweetAlert Enabled

Confirm Example with SweetAlert Disabled

#### SweetAlert position using Toast

Sets the display position of the message window using toast.

#### 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.

## Global Variables

This screen shows all global variables used 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.

You can define global variables by using square brackets ([variable]). You can pass the parameters to the application through one of the methods: Session, Post, and Get

> IMPORTANT: if you need to use Database Identifiers in your tables, we recommend using the double quotation marks( “ ) instead of the brackets( [ ] ) because of the conflict with the of Global Variables syntax{:target=”_blank”} Scriptcase. Using the brackets as database identifiers may lead to problems in the Scriptcase applications.

Global variables Interface.

Example:

`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 is displaying in the global variables configuration.

Global variables configuration Interface.

#### Attribute

It shows the variable’s name in the application.

#### Value

Defines the behavior of the variables, divided into three blocks, they are:

##### Scope

Defines how the application receives the variable. A variable defined as the POST method in the app does not receive value if it comes with the GET method. Those are the methods available:

- Session: Defines that 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 an HTML form.

  ##### Settings

- Optional: Check it to don’t validate the variable at runtime.

##### Type (In / Out)

Defines whether the variable comes from another application (In), or it is starting in the current app (Out).

#### Description

Indicates where the application is using the variable.