On this configuration, you can set the common attributes of the applications created by ScriptCase.
Application Configuration Interface
- Application Code : Code of the application that’s determined at the moment the creation of the application, this code can be renamed in the List of Applications.
- Description : This field is reserved for a brief description of the objectives of the application.
- Documents Path : The absolute path to the documents directory of the application.
- Image Directory : Base directory of where the application images are stored.
- Application images : Allows to import images into the application and using them in the application routines, disregarding the macro sc_image.
- Language : Language of the generated application. All the hints and messages are displayed in the selected language.
- Share Location Variable : Shares the Location settings with other applications based on the value of the session variable.
- Charset : Defines the specific charset used in the application.
- Share Theme Variable : Shares the Theme settings with other applications based on the value of the session variable.
- Folder : Folder where the application’s stored in the work group.
- Edit by Project : Allows for the other users of the group to edit the application.
- Timeout : Time of the runtime timeout in seconds. If the value is Zero, it assumes the default timeout of the PHP.
- HelpCase Link : Associate the files of the HelpCase with the application.
Error Settings Interface.
- Script Error : Allows to display the information of the Script Line where the error occurred.
- SQL Error : Allows to display the SQL where the error occurred.
- Debug Mode : Runs the application in Debug mode, displaying the SQL commands the moment that they are executed.
- Ajax Error Output : Open a window of debug with the output of the Ajax.
Defines the attributes of the navigation of one application to another.
- 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 define the messages that will be displayed on each validation type (Insert, Update and Delete). You can also define messages for SQL errors.
- No Records Message: Displays a customized message when the application has no records.
- Primary key violation: Displays a customized message when the database’s primary key constraint is violated.
- Unique key violation: Displays a customized message when the database’s unique constraint is violated.
- Message After Insert: Displays a customized message after a record is inserted.
- Message to Confirm Insert: Displays a customized message asking to confirm the insertion of a record.
- Message After Update: Displays a customized message after a record is updated.
- Message to Confirm Update: Displays a customized message asking to confirm the changes of a record.
Messages of delete
- Message After Delete: Displays a customized message after a record is erased.
- 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 messages. Those values can be configured in Locales -> Application Language.
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.
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.
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.