Hey Wrike Community! 🙋🏻♀️
We’re excited to introduce a new Labs release that makes installing templates into existing Spaces smoother and cleaner: Configurations Mapping!
When you add a template to an existing Space, the template may include configurations that already exist in your workspace. Without mapping, this can lead to duplicate configurations, fragmented data, and extra cleanup after installation.
With Configurations Mapping, you can decide which configurations from the template should be added as new, and which should be matched to the ones that already exist in your Space or account.
For this first Labs release, Configurations Mapping supports Custom Fields. Support for Workflows and Custom Item Types will be added shortly.
How to Use Configurations Mapping 🔮
1. Start Installing a Template into an Existing Space
Choose the template you want to install and select an existing Space as the destination.
When choosing the installation process, select Review and choose.
2. Review Configurations from the Template
After selecting Review and choose, you’ll be taken to a mapping step where you can review the configurations used in the template.
In this release, you’ll see the list of Custom Fields included in the template. For each Custom Field you can see:
You can also hover over a field to preview more details.
3. Choose How Each Custom Field Should Be Installed
For every Custom Field in the template, you can choose one of two options:
- Add as new
The Custom Field from the template will be installed as a new field. - Match to…
Select an existing Custom Field from the target Space or account to use instead.
How It Works 👥
- Only Space admins can use Configurations Mapping for their Spaces. When installing a template into an existing Space, Space admins can select Review and choose and decide how Custom Fields from the template should be handled.
- Matching is type-based. You’ll only see compatible fields as mapping options. For example, a Single-select field can only be matched to another Single-select field, and a Currency field can only be matched to another Currency field.
- Matched fields are reused instead of duplicated. If a Custom Field from the template is matched to an existing Custom Field, the original field from the template won’t be installed. All item references from the template will be remapped to the existing field you selected.
This logic ensures you get the complete solution from the template while keeping it aligned with the structure of your Space.
For example, if the template includes an AI Agent with an action that uses Custom Fields, you’ll get that AI Agent set up with your existing matched Custom Fields, not with newly created Custom Fields from the template.
What’s Supported Now? 👀
In this Wrike Labs release, Configurations Mapping supports:
Coming shortly:
- Workflows
- Custom Item Types
This is the first step toward a more flexible template installation experience, where you’ll have more control over how template configurations are added, reused, or matched with what already exists in your workspace.
We’d love to hear how this works for your team and what configuration types you’d like to map next. Try it out in Labs and let us know your feedback below! 👇
