About Migrating Individual Account Reconciliation Artifacts
Service Administrators can migrate individual artifacts across environments by using the export and import functionality.
In addition to migration, this functionality can also be used when user errors cause one or more artifacts to be corrupted. You can use import and update only the affected artifacts, without impacting the other artifacts in the application.
The exported individual artifacts can be imported into an environment on a previous release or a future release. This enables you to move artifacts from test to production, when the test environment has been upgraded before the production environment. Note that when you create a snapshot of one or more artifacts, you can import only these artifacts into a target environment.
In the Categories tab of the Migration card, using the Backup option creates a snapshot file containing all information for the three listed categories: Data Management, Financial Close Management, and Groups and Membership. When the Financial Close Management category is expanded fully, the Service Administrator can select individual Account Reconciliation artifacts and then use Export to create an export file containing only the selected artifacts. When using a backup or user-created export, you can:
- Perform a full import
- Import the selected individual artifacts
For information about migrating snapshots, see Migrating Account Reconciliation Snapshots Using Navigator.
Best Practice for Migrating Individual Artifacts
- Migrate individual artifacts only when the artifacts are new or have been updated.
- Ensure that you migrate individual artifacts into a target service that is similar to the source service.
- Avoid migrating artifacts into a newly created service.
The following are use cases for migrating individual artifacts:
- A full snapshot of the production environment is made to a test environment. Subsequently, several artifacts in the test environment are updated. You can then migrate the updated artifacts in the test environment to the production environment.
- Artifacts are updated in the production environment but there are some problems with these updated objects. You can migrate these artifacts from the previous night’s backup snapshot into the production environment.
Artifact Types that Can be Exported and Imported
The artifact types that can be exported and then imported are as follows:
- Account types
- Aging profiles
- Attributes
- Calendars
- Currencies
- Currency buckets
- Email notifications
Only the set of system notifications are included. Notifications created by individual users are not included.
- Filters
- Formats
- Frequencies
- Global integration tokens
- Global settings
- Holiday rules
- Match types
- Organizational units
- Periods
- Power user security
- Processes
- Rate types
- Report groups
- Report queries
- Reports
- Risk ratings
- Saved views
- Teams
Note:
For the following artifact types, when you import a snapshot or backup, existing artifacts are overwritten by the ones in the imported snapshot or backup:- Account types
- Aging profiles
- Currency buckets
- Frequencies
- Global integration tokens
- Global settings
- Processes
- Risk ratings
Note:
When you select Global Settings, only the following settings from Application -> Configuration -> System Settings are exported:
- Governors: Select maximum upload file size (MB)
- Date and Time: Reconciliation Due Reminder
- Data Load: Number of hours to wait for Data Management data load rule to finish
- Reviewer Levels: Reviewer Levels