WinStudio

Customizing Deployed WinStudio Applications

A developer can use WinStudio functionality to customize forms and global objects (including creation of new forms) in a deployed application.

Customized objects are tagged in the forms database as versions different from vendor-supplied objects. WinStudio determines the version of a form or global object by using the editing scope of the developer who saves the form or global object.

When a new vendor-supplied version of an application is to be installed, developers use Form Sync to preserve their customizations while updating their forms database with new vendor default versions. For more information, see the online help for Form Sync.

To customize a deployed WinStudio application, developers need Basic, Full User, or Site Developer editing permissions. The application administrator assigns editing permission when the developer's user profile is created.

Editing permissions determine the scope of customizations, including the developer's ability to use all the functions in Design Mode (or only a subset of those available) and the developer's ability to save customizations as a particular version in the forms database.

• Developers with Basic or Full User editing permissions create user versions for their own user IDs only.
• Developers with Site Developer editing permissions can create user versions for any user ID, group versions for an identified group, or site versions that are displayed to all users on the system. Site Developer editing permissions also allow developers to set up public and user folders in the Explorer.

Related Topics

Customizing the Explorer

Developing WinStudio Applications

Editing Permissions

Identify Your Editing Scope

Identify the Version of a Form

Set and Change Editing Scope

Understanding Version Control in the Forms Database

Understanding Which Version Is Displayed

Customizing a Form