Design UI Layouts

This program lets you design how the SYSPRO user interface must be displayed for operators at role level, system-wide or industry level.

• This program is accessible from the Ribbon bar:

  SYSPRO Ribbon bar > Administration > Design UI Layouts

• The Role layout design option must be enabled against your operator code (Operator Maintenance).

• While in design mode, the Navigation Pane toolbar buttons are disabled, as well as the ability to add or import customized panes to the Executive View.

• Ensure that the role for which you are designing layouts is configured for design at UI level (Role Management) and has access to the program you are modifying.
• In a client/server environment, ensure UI design is done on the client machine and not the server. When done on the application server, it does not self-heal to the client.

Staging folder

To minimize interference between someone who is designing for a role and operators for that role already logged in (or about to log in) the system follows a specific processing sequence.

When entering design mode for a role:

1. The system deletes all the files for the role from the Role folder on the client.
2. The system copies all files for the role from the server to the client (this ensures that the designer is using the latest set of UI layout files).

3. The files are copied to the Role_### staging folder on the client. This staging folder is created in the \Base\Settings folder.

   If the system exits unexpectedly during design mode, the files in the staging folder remain untouched. When that operator logs back into SYSPRO, the system prompts whether the operator wants to resume editing for that role. The operator will need to enter design mode for the role before the files for the role are copied to the Role_### folder.

When exiting design mode for a role:

1. The system creates a temporary file in the Role_### folder on the server.
2. The file serves as a folder lock for that role (i.e. users will be unable to login using that role until the copy process is complete and the temporary file removed).
3. When self-healing executes, then all files in the Role_### folder are removed and the files are copied from the server to the client.
4. If any file is not successfully copied across from Role_### to the correct Role_ folder on the server, then a message is given and the Role_### folder on the client machine is not removed. If this happens, you should check permissions on the target folder.

• Only programs that have been changed in system-wide design mode are locked down for the user.

  For example: If the administrator only adjusts how the Customer Query program works, then only files for that program will appear in the Role_XXX folder (where xxx indicates the layout code) and only that program cannot be further adjusted by the user. When loading SYSPRO, the system scans the layout and script files stored in the Role_SYS folder to see which programs have been adjusted. An internal table is created containing a list of all the programs for which layout changes have been made. Any program listed is automatically locked down.

• Despite a program being locked down, you can still adjust the overall appearance of the user interface if you have enabled the Save docking layout when using roles operator activity.

  Similarly, you can adjust columns in a list view if you have enabled the Save list view layout when using roles operator activity. In both cases, changes are only applied until the administrator next adjusts the docking or list view layouts in system-wide design mode.

  A version number is stored within the docking and list view layout files and if it doesn't match the version number saved in the user's definition file, then the administrator's changes are re-applied. The user definition files are saved on the client machine and named as follows:

  • For docking layouts: \Settings\Dock_operator_XXX_ARSPENLZ.XML
  • For list view layouts: \Settings\List_operator_XXX_ARSPENLV.XML
• When designing for the Application Builder 1 programs, the application title is saved in the Role_XXX folder.

VBScript considerations

• VBScript files that are created or maintained during design mode are saved in the Role_XXX folder in \Base\Settings (where xxx indicates the layout code). This differs from roles where scripts are saved to the \Work\VBScripts folder. You can create the folder offline and then deploy it at a site.
• You cannot edit VBScripts for tiles or flow graphs while in design mode.

Self healing

• Permissions and activities are never self-healed as they are read from the server.
• UI layouts by role designed on the server are not self-healed to the client.

Toolbars

• You must use the Customize mode to customize a toolbar. Simply removing buttons from the toolbar does not save the changes when done in Design mode. Right-click the toolbar and select Customize from the context menu.
• The Show List view Toolbar option (available from the CTRL+F1 submenu, or right-click the header row of any list view) is saved at operator level, which means that the operator can override the Design mode setting for this option.