Creating scripts using Access As and Object Prefix

To create scripts using the Access As and Object Prefix values:

  1. Open the Deployment form.
  2. Click the Export using AccessAs and Object Prefix option.
  3. In the Export Applet section, specify this information:
    Profile Name
    Specify the name the deployment profile.
    Note: You can have multiple deployment profiles for application or applet script packages.
    Access As
    Select the Access As value to use with your applet from these options:
    • To use an existing Access As value, select it from the list of available Access As values.
    • To use a blank Access As value, select (null).
    • To instruct the filter not to consider Access As values, select (ignore).

    When creating a new record, this field is automatically populated with the default Access As value.

    Object Prefix
    Optionally, specify a prefix for the application or applet objects.

    Normally, this value is the same as the Access As value, but not necessarily.

    Note: The system uses both the Access As value and the Object Prefix value to filter for forms, component classes, scripts, strings, and so on. Objects database elements, such as IDO collections, property classes, custom load assemblies, message, and IDO projects are filtered as well. Finally, Application database schemas and User-Defined Data Types (UDTs) are also filtered and included based on these values.
    Script Application Database
    Select this check box to create scripts for database schemas, specifically for custom-created tables and all custom-created UDTs.
    Script Forms Database
    Select this check box to create scripts for all forms metadata and global objects.
    Script Objects Database
    Select this check box to create scripts for all Objects database elements, such as IDO definitions, IDO property classes, and IDO extension class assemblies.

    This database also includes some metadata definitions found in the Application database that use the Access As attribute. This includes all customized Application Event System (AES) metadata and all customized Replication Document metadata.

    Include data
    Select this check box to specify that any data in the app tables must be included in the scripts.
    Scope
    Select the scope type:
    • Vendor: Click this option to create script files that are used by an application vendor.
    • Site: Click this option to create script files that are used by all users.
    Output
    Specify the location in which the zip package with the scripted files is to be created.

    Use the ellipsis (…) button to the right of this field to navigate to and select the location you want.

    Note: The ellipsis button is not available in the web client or in a partial trust situation. However, you can still designate a path and filename for the imported files. Web or partial trust needs a suggested name for download, but you can change it.
  4. Click Create Scripts.
The system creates all the selected script files and packages them into a zip file at the specified location.

To verify that the zip file has been correctly created, perform these actions:

  • Click View Log, and examine the output log for the operation.
  • Go to the designated output location and verify that the zip file is there and that it contains the expected script files.