Import Electronic reporting (ER) configurations from Regulatory Configuration Services (RCS)
Important
Regulatory Configuration Service (RCS) will be deprecated. All new RCS provisioning is stopped as of 10.0.39 GA. If provisioning is required, please register a support ticket. We will be providing tools and required support for migration from RCS to the Globalization Studio workspace. We plan to fully shut down RCS by August 1, 2024. For more information about migration to Globalization Studio workspace, see Regulatory Configuration Service merge to the Globalization Studio workspace
You can use Regulatory Configuration Services (RCS) to design Electronic reporting (ER) configurations. The ER tool provides access to the list of configurations that have been configured in each instance of RCS that has been provisioned for your company. You can use this feature to import configurations that you configured in an RCS instance into the current instance. After configurations are imported, they can be used to handle incoming documents or generate outgoing electronic documents.
To learn more about this feature, complete the example in this article. Alternatively, download and play the ER Import configurations from RCS task guide, which is part of the 7.5.4.3 Acquire/Develop IT service/solution components (10677) business process. It walks you through the process of importing ER configurations from an RCS instance into the current instance.
Example: Import an ER configuration from RCS
This example shows how a user in the System Administrator or Electronic Reporting Developer role can import a new version of an ER configuration from RCS. In this example, you select the desired version of the ER configuration that has been configured in an RCS instance, and you import that version into the current instance for a sample company that is named Litware, Inc. These steps can be completed in any company, because ER configurations are shared among companies.
To complete the steps in this example, you must first complete the steps in Create configuration providers and mark them as active. You must also have access to an RCS instance that contains at least one ER configuration that has a status of either Completed or Shared.
- Go to Organization administration > Workspaces > Electronic reporting.
- On the Localization configurations page, in the Configuration providers section, make sure that the configuration provider for the Litware, Inc. sample company is listed, and that it's marked as Active. If you don't see this configuration provider, follow the steps in Create configuration providers and mark them as active.
- If no RCS environment has been provisioned for your company, in the External Links section, select Regulatory services – Configuration. Then follow the instructions to provision an RCS environment.
- In the Related links section, select Electronic reporting parameters.
- On the Electronic reporting parameters page, select the RCS tab.
- Use the URLs on this tab to access the RCS environment has been provisioned for your company.
- Close the Electronic reporting parameters page.
Register a new ER repository
- On the Localization configurations page, select the Litware, Inc. configuration provider in the list.
- Select Repositories.
- Select Add to open the drop-down dialog box.
- Select RCS as the configuration repository type, and then select Create repository.
- In the RCS environment display name field, select the desired RCS instance. Note that you can have several instances.
- Select OK.
Import ER configurations from an RCS-based repository
- On the Configuration repositories page, select the Show filters button on the left side of the window.
- For the Name filter, select begins with as the filter operator, and then enter RCS as the filter value.
- Select the repository, and open it.
- On the Connect to Regulatory Configuration Services page, select the Click here to connect to Regulatory Configuration Services link.
- Select Open.
- Select Close.
- Select the desired version of the ER configuration, and then select Import to import that version.
Additional resource
Feedback
https://aka.ms/ContentUserFeedback.
Coming soon: Throughout 2024 we will be phasing out GitHub Issues as the feedback mechanism for content and replacing it with a new feedback system. For more information see:Submit and view feedback for