Migrate from Claims Studio to the Control Panel

What changes when you migrate to the Control Panel

Connected Claims 2.0 replaces the Claims Studio site with the Control Panel, a configuration workspace embedded in the Connected Claims application. Claims administrators who configured claim types, tasking, surveys and questions, policy setup, and email templates in the Claims Studio site perform the same configuration in the Control Panel after upgrade.

Migrating to the Control Panel changes where claims administrators work and how they reach each configuration page. Migrating to the Control Panel does not change the claims data model, and it does not change how claims adjusters and supervisors use Workspace.

This page describes the navigation changes, the configurations that carry over, the configurations that require review, and the effect of the migration on the objects that Claims Studio generated in Appian Designer.

Prerequisites for migrating to the Control Panel

Migrating to the Control Panel requires the following prerequisites in your environment:

• Connected Claims 2.0: Your environment must run Connected Claims 2.0 or later. Earlier versions do not include the Control Panel.
• Supported Appian platform version: Your environment must run the Appian platform version that Connected Claims 2.0 requires. See Connected Claims support and release history for the supported platform version.
• Claims administrator access: You must belong to the group that grants access to the Control Panel. See Permission changes for claims administrators.

Claims Studio to Control Panel navigation mapping

The Control Panel reorganizes the Claims Studio pages into five sections, which you select from the Control Panel navigation pane. Most Claims Studio pages become a tab within one of those sections. The following table maps each Claims Studio location to its Control Panel location.

Claims Studio location	Control Panel location	What to know
CLAIM TYPES > All Claim Types	Claims section > Overview tab	The page is renamed All Claim Categories and Claim Types. Claim categories, claim types, and the drill-down into each claim type work the same way as in Claims Studio.
CLAIM TYPES > Data	Claims section > Data tab	Global data fields shared across all claim types remain on a dedicated tab.
TASKING > Tasks	Tasking section > Tasks tab	Reusable tasks, their group ownership, service level agreements (SLAs), and costs remain unchanged.
TASKING > Task Blocks	Tasking section > Task Blocks tab	Task blocks and their visualizations remain unchanged.
TASKING > Surveys	Questionnaire section > Surveys tab	Surveys move out of Tasking into the new Questionnaire section. They remain assignable as tasks in claim workflows.
TASKING > Questions	Questionnaire section > Questions tab	Questions move out of Tasking into the new Questionnaire section. The question bank and all question types remain unchanged.
POLICY SETUP > Lines of Business	Policy Setup section > Line of Business tab	Policy Setup keeps its name. The tab is renamed from the plural Lines of Business to Line of Business.
POLICY SETUP > Products	Policy Setup section > Products tab	Insurance products are configured on the same dedicated tab.
POLICY SETUP > Cost Categories	Policy Setup section > Cost Categories tab	Cost categories are configured on the same dedicated tab.
ASSIGNMENT RULES	Claims section > Automation Rules tab	The page is renamed Automation Rules and moves under the Claims section. Automated claim assignment and routing rules remain available after migration. Rules are evaluated sequentially based on their order in the list.
EMAIL TEMPLATES	Email Templates section	Email Templates is a section in its own right and has no tabs. Email templates and their supporting documents remain unchanged.

Within a claim type, Claims Studio presented the intake form and the summary page as their own tabs. The Control Panel consolidates both, along with the edit form, onto a single Interfaces tab. The claim type Details, Data, and Workflow tabs keep their names. See Claim type configuration.

Configurations that carry over automatically

Claims configuration created in Claims Studio is stored in Connected Claims record types, not in the Claims Studio site. Because the Control Panel reads the same record types, the following configurations carry over automatically and require no reconfiguration:

• Claim categories and claim types: Every claim category and claim type, including its details, data fields, intake form, workflow, and summary page configuration.
• Tasks and task blocks: Every task and task block, including group ownership, service level agreements (SLAs), costs, and the connections between tasks in a block.
• Surveys and questions: Every survey, every question in the question bank, and the active status of each.
• Lines of business, products, and cost categories: Every line of business, the products linked to each line of business, and the scope of each cost category.
• Email templates: Every email template, including its subject, body, and supporting documents.
• Assignment rules: Every automated claim assignment and routing rule.

Configurations that require review after upgrade

Migrating to the Control Panel requires you to review the following configurations. Each item involves either a permission model or a customization that the upgrade does not adjust for you.

• Claims administrator group membership: Confirm that the users who administered Claims Studio can access the Control Panel. See Permission changes for claims administrators.
• Record type role maps for custom claim types: Editing a custom claim type or claim category requires membership in that record type's role map. Confirm that your claims administrators remain in the role map for every custom claim type and claim category record type.
• Customized generated interfaces: Confirm that interfaces you customized in Appian Designer render correctly in the Control Panel. See Generated objects and Designer customizations after migration.
• Inbound links and bookmarks: Links and browser bookmarks that point to Claims Studio pages must be repointed to the equivalent Control Panel pages. See Claims Studio to Control Panel navigation mapping.

Permission changes for claims administrators

In Connected Claims 1.2 and earlier, the Studio Editors system group controlled which users could edit objects in the Claims Studio site. Connected Claims 2.0 governs access to the Control Panel through the same group model.

Editing a custom claim type or claim category also requires membership in that record type's role map, which is unchanged from Claims Studio. Object security for generated record types and interfaces continues to use the default role map that Connected Claims applies at generation.

For the full list of Connected Claims groups and the access each group grants, see Configure security.

Generated objects and Designer customizations after migration

Connected Claims generates record types, interfaces, and database scripts in Appian Designer when a claims administrator creates a claim category, a claim type, a choice list data field, a form, or a summary page. Migrating to the Control Panel does not regenerate or replace these objects, and it does not change the data model they define.

Connected Claims continues to package generated objects and their database scripts for deployment. For the package name, the script threshold that triggers an additional package, and deployment guidance, see Low-code configurations.

Functions in customized interfaces

Interfaces that Connected Claims generates use functions specific to Connected Claims, such as the wizard layout function that builds intake and edit forms. If you customized a generated interface in Appian Designer, for example to add a Save Draft button or to add pages before or after a form, then that interface calls these functions directly.

After you upgrade, open each customized interface in Appian Designer and confirm that its function calls and parameters are still valid. For the configurations that rely on these functions, see Low-code configurations.

Verify your Control Panel configuration after upgrade

Verifying your configuration after upgrade confirms that claims administrators can reach the Control Panel and that your existing claims configuration is intact.

To confirm that your Control Panel configuration migrated successfully:

1. Sign in to Connected Claims as a claims administrator.
2. Open the Control Panel and confirm that the Claims, Tasking, Questionnaire, Email Templates, and Policy Setup sections are available.
3. In the Claims section, go to the Overview tab and confirm that every claim category and claim type from Claims Studio appears on the All Claim Categories and Claim Types page.
4. Go to the Data tab and confirm that your global data fields appear.
5. Go to the Automation Rules tab and confirm that your assignment and routing rules appear, in the same order they had in Claims Studio.
6. Open one claim type and confirm that its details, data fields, intake form, workflow, and summary page match the configuration from Claims Studio. The intake form and summary page are on the Interfaces tab.
7. In the Tasking section, confirm that your tasks and task blocks appear on their respective tabs.
8. In the Questionnaire section, confirm that your questions and surveys appear on their respective tabs.
9. In the Policy Setup section, confirm that your lines of business, products, and cost categories appear on their respective tabs.
10. In the Email Templates section, confirm that your email templates appear with their subjects, bodies, and supporting documents.
11. In Workspace, create a test claim of a migrated claim type and confirm that the intake form and workflow behave as they did before the upgrade.

Troubleshoot Control Panel migration

If you encounter issues after migrating to the Control Panel, check the following:

• A claims administrator cannot open the Control Panel: Confirm the user's membership in the group that grants Control Panel access. See Configure security.
• A claims administrator cannot edit a custom claim type: Confirm the user is in the role map for that claim type's record type. See Object security in Connected Claims apps.
• A customized form does not render as expected: Open the generated interface in Appian Designer and confirm the function calls and parameters are valid. See Functions in customized interfaces.
• A Claims Studio link returns an error: Repoint the link to the equivalent Control Panel page. See Claims Studio to Control Panel navigation mapping.

Feedback