Feedback Print

Application

Settings

On this configuration, you can set the common attributes of the applications created by ScriptCase, you can view the attributes below.

Application Configuration Interface Application Configuration Interface

  • Attributes
    • Application Code : Code of the application that is determined at the moment the creation of the application. This code can be renamed in List of Application.
    • Description : This field is reserved for a brief description of the objectives of the application.
    • Documents Path : The absolute path of the application’s documents directory.
    • Image Directory : Base directory of where the application images are stored.
    • Application images : Allows to import images into the application and use them within the application routines, disregarding the macro sc_image.
    • Language : Language of the generated application. All the application’s hints and messages are displayed in the selected language.
    • Use 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.
    • Maximum file size : Set the upload maximum file size of the application.
    • Message title : Message box title.

Error Settings

Error Settings Interface. Error Settings Interface.

  • Attributes
    • Error position : Position of the error messages on the application.
    • Error Position on the field : The position of the error messages when criticizing the field.
    • Show the Error Title in the Application : Show the title line of the error message in the application.
    • Show the Error Title in the Field : Show the title line of the error message in the field.
    • Script Error : Allows to display the information of the Script Line where a error occurred.
    • SQL Error : Allows to display the SQL where a error occurred.
    • Debug Mode : Runs the application in Debug mode, displaying the SQL statements at the moment that they are executed.
    • Ajax Error Output : Enables the use of 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.
    • Return After Inserting : Dont open a new blank record after an insert, instead go to edit mode.
    • Exit Application : The target exit the application after processing the form.

Messages

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.

Messages

Messages Interface Messages.

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

Insertion Messages

Insertion Interface Messages.

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

Update Messages

Update Interface Messages.

  • 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

Delete Interface Messages.

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

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.

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

Synchronize table

This process will performs a comparison between the definitions of application fields and the connected database fields. If there is any change within the connected table, such as adding a new field, exclusion, or a change in the data type, the changes will appear visible like in the image below:

Table synchronization interface. Table synchronization interface.

After accessing the function from the link “Synchronize table” you will see a comparison table between the application fields (left table) and the database table fields (right table), like the image above, the fields highlighted in “red” will be deleted of the application, the highlighted fields in “Green” will be inserted in the form, and the highlighted fields in “orange” will be updated, so data type will be updated.

To rename a field in the database table, the table synchronization effect, by comparison, will be the same as deleting a field that existed in the application and the inclusion of a new field.