Applying Screen Painter to Chains

There are two ways to copy screen painter data to chains: through screen painter templates and by exporting/importing data through OPERA SMT. The most convenient and fastest method is Screen Painter Templates.

Screen Painter Templates

Screen painting can be applied to a chain and multiple chains using a template.

The template name is assigned to the chain by the user through the application setting General>Screen Painter Template. By default, the application setting template name value is set to the chain code of the current property. To create a new template name, enter the name in the Value field. The template name does not have to match an existing chain code. The new template name can be free format, while avoiding special characters. The template is located in the same table as the chain code: dynamic_fields table.
When forms in Configuration>Setup>Screen Design>Screen Painter are screen painted, records are created in the dynamic_fields table and the template applies changes to all properties in the associated chain. Some considerations to remember:
1. A screen painter template is per chain.
2. Screen painting is only applied to properties in the chain with the specified template.
3. The same template can be used for different chains in a schema (when assigned in the application setting General>Screen Painter Template).
4. Different templates can be used for different chains in a schema. (when assigned in the application setting General>Screen Painter Template).
5. When screen painting in ASP Mode, the template name is identified in the title bar of the form being painted.
When migrating chains having screen painted forms into an existing chain or a new chain, using OPERA to Hosting (O2H) Utility, the screen painter template eliminates downtime. The OPERA to Hosting (O2H) User Guide on the ORACLE MICROS Members web site provides more details.

Export/Import Chain Data with OPERA SMT

Screen painter dynamic fields can be imported/exported to/from chains through SMT>Schema Management>Screen Painter Data. This can be done to/from an ASP-Mode chain or a non-ASP Mode chain. This procedure should be done by an OPERA Supervisor or OPERA Support.

Export

In the Schema Management section, select Screen Painter Data to export Screen Painting information.

smt_screen_painter_data_button

This option will extract all the screen painter related data and create a compressed *.scz file.

smt_import_export_fields

To export, select Export Screen Painter Data. The exported data will be written to a file with the format <schema name>screen_data.scz in the folder where the Opera_SMT tool being executed resides.
Example: Connected to V43opera1, screen painter data will be written to V43Opera1screen_data.scz.

Import

To import screen painting data from a *.scz file. Enter the file name or click on [ … ] to browse for a file.
Note: Importing Screen Painting data will overwrite any existing data in the dynamic_fields table. Existing screen painting information will be lost!
When you click on Import Screen Painter Data Opera_SMT will verify that the file exists and is a valid *.scz file. Opera_SMT will also check the file version against the OPERA Schema version. When the versions do not match, Opera_SMT will display a warning message.
On completion of the import you will see the following message "Screen Painter Data imported successfully."
After importing screen painting data, it is necessary to recompile conditions in Screen Painter. Opera_SMT lists all the forms that need to be recompiled.

smt_screenpainter_successful_import