WorkView has the capability to allow you to import and export applications from one WorkView system to another. This is accomplished through the Import/Export features found in the Home ribbon of the OnBase Studio.
Your export files should be exported using the same version of OnBase that you plan to import the files into. Also, ensure you have rights to the defined System Paths for WorkView. You must have read writes to export and full access rights to import.
Before exporting, it is recommend you run the WorkView Doctor to identify and resolve issues in your configuration.
WorkView Applications and WorkView Classes can be exported. If you choose to export a single class, you will have to map all of its references to items in the destination database. Only the class can be create as new in this scenario. Ensure that what you are mapping to in the destination database supports the newly created items.
Always verify your configuration after the export and import processes.
In order to successfully import, the Application Server must have write rights to the resource directory.
The following are considerations for exporting and importing for WorkView:
-
Any view that has not been updated will not be exported. Views created prior to 18 must be updated before they can be exported or imported.
-
When importing, No Action is not a valid status for a WorkView import.
-
When importing, classes can only be mapped to classes that share the same class type.
-
A default screen cannot be created if the corresponding class is mapped.
-
WorkView applications, and their items, that are password protected cannot be exported via the right-click Export option in the Repositories pane.
-
Icons and bitmaps are automatically decisioned upon import. If an icon or bitmap in the import package matches the name of one that exists in the destination database, that icon or bitmap will be mapped to the existing one in the destination database. If an icon or bitmap does not already exist in the destination database, it is automatically created.
-
When exporting a class with an event that executes a Workflow System Event, the event will not be exported automatically. In order to export this configuration, you must specifically add the specific Workflow System Events item that corresponds to your class' configuration.
-
If you have imported an application that was associated with a Unity Script, you must open the script, set it to active, and publish it.
-
If a data set is replaced, all data set values within it will be replaced as well.
-
If the index type configuration for attributes within an external class are changed and you are updating an application, the external class attribute will not be changed.
-
Composite keys cannot be replaced; they can only be mapped.
-
When importing module associations and WorkView Data Providers do not rename them during the import process.
-
When importing module associations for use with Reporting Dashboards, always import the corresponding WorkView application before performing the Reporting Dashboards import.