Understanding WinStudio customizations

Note: The term "customizations" refers to customizations made using Design Mode in a Windows "smart" client or using Web Designer in a web client.

About customizations

Customizations can affect any or all of these areas of the client tier:

  • Forms and components - Authorized users can add, copy, or alter forms. They can also add, delete, recaption, hide, move, or otherwise alter components on a form.
  • Global objects - Global objects include themes, image files, strings, variables, shortcut menus, validators, scripts, component classes, and property class extensions. These global objects can be used by more than one form or component. Authorized users can add, delete, change, or associate global objects with different forms or components.
  • The Explorer window - Authorized users can customize Public folders. All users can customize the folders in "My Folders". An application can also have customized versions of folders in the Master Explorer.

Customized versions

All customized versions are stored in the forms database. Forms and global objects can be customized for one user (User level), for a group of users (Group level), or for all users (Site level). As a result, the forms database can include more than one version of the same form or global object.

  • The Vendor version of a form or global object is the version originally supplied by your vendor (usually either Infor or one of our business partners). It is unaffected by customizations.
  • A Site version of a form or global object can be a customized version that all users at a particular site can access, unless it is superseded by a Group or User version. Only a user with Site Developer editing permissions can create a Site version.
  • A Group version of a form or global object is a customized version that all users in a particular group of users can access, unless it is superseded by a User version. Only a user with Site Developer editing permissions can create a Group version.
  • A User version of a form or global object is a customized version that only one user can access—either the user who created it or a Site Developer who created it for that user. Users with Basic, Full User, or Site Developer editing permissions can create User versions.

Basic and major customizations

Basic customizations are simple changes to forms and components that do not affect functionality. Users with Basic editing permissions can make only these changes:

Components Forms
Captions

Default Values

Dimensions (size, position)

Show or Hide

Read Only/Disabled

No Clear on New

Default on Copy

Upper or Lower Case

Captions

Dimensions (size)*

Splitter settings*

Grid column sequence*

Grid column width*

Grid column visibility*

*These changes can be made by any end user, regardless of editing permissions, without the system having to save a full User-scope version of the form. If you have set your User Preferences to prompt you to save form, splitter, and grid changes, Mongoose prompts you when closing the form after making such changes. Otherwise, the changes are saved without prompting.

You should be aware, too, that system administrators can override the ability to save run-time form changes like this with the Allow saving form runtime changes process default.

Major customizations are changes other than basic changes and that can affect functionality. Developers with Full User or Site Developer editing permissions can make basic changes as well as these more extensive, major, customizations.