10 - Working across Assets 6 and Assets 10

Info: This article is work in progress and subject to change.

The Workflow Assistant supports both WoodWing Assets 6 and WoodWing Assets 10. The Configurator detects which version of Assets your configuration is bound to and uses the matching SDK adapter behind the scenes. As an admin you do not have to choose; the Workflow Assistant adapts.

A small number of behaviours differ between the two versions. This article documents the differences that affect panel design, with notes on what to verify in each version before publishing a panel that supports both.

For a refresher on where the Workflow Assistant fits in Assets, see 01 — Introduction to the Workflow Assistant.

What is the same

Most of what this manual describes applies to both versions identically:

• The four-level structure (tabs → sections → rows → components)
• All thirteen field types
• All Action types and the Lucene-driven Disable, Required, and Display conditions
• All five widgets
• The visibility checklist and asset-kind list
• Tab audience targeting via Assets user groups
• Save, publish, and rollback semantics
• Configurator sign-in and the app selector

If a behaviour appears in this manual without a version qualifier, treat it as identical across Assets 6 and Assets 10.

What differs

The differences fall into three small categories.

1. Plugin entry point

Both entry points use the same configuration. The difference is invisible to admins; it matters only to support staff diagnosing installation issues. See the support manual’s pre-flight chapter for the verification procedure.

2. Asset metadata field availability

The Assets metadata schema differs between versions in small ways. Two cases to be aware of:

• Field naming conventions can differ. assetDomain is consistent across both versions; some custom-field naming traditions changed between Assets 6 and Assets 10. The Field-name autocomplete in the Configurator only shows fields that exist in your current Assets installation, so this is mostly self-policing
• System metadata fields added in Assets 10 are not available in Assets 6. If your panel uses a field that exists only in one version, the panel will work for users on the supported version and error for users on the other

Note: When designing a panel that needs to work across both versions, restrict yourself to fields available in both. The conservative test: confirm in your Assets 6 installation that every Field name used in the panel exists. If a field is missing in Assets 6, the panel will error for Assets 6 users.

3. UI rendering details

The two SDKs render some things slightly differently:

These differences are cosmetic and do not affect what the panel does. They become relevant only when designing tightly to a fixed pixel width — which is rare and not recommended.

Verifying a panel against both versions

When you administer configurations for customers on both Assets 6 and Assets 10, the verification habit is the same as for any panel — sign in as a test user — but performed twice.

Step 1. Maintain a test environment in each Assets version, with a test user account in the Required role for each.

Step 2. When you make a change in the Configurator, save and publish.

Step 3. Verify in the Assets 6 test environment.

Step 4. Verify in the Assets 10 test environment.

Step 5. If a behaviour differs, identify whether it is a metadata-field availability issue, a UI rendering issue, or a genuine bug. The first two are usually covered by the notes above; bugs go to support.

Tip: If your customer base is predominantly on one Assets version, focus your testing there but periodically verify on the other. Most differences are caught the first time you switch environments and never again.

When a customer migrates from Assets 6 to Assets 10

If a customer is migrating their Assets installation from version 6 to version 10, the Workflow Assistant configuration generally moves with them — the same configuration works on both versions, given the field-availability caveat above.

The recommended migration workflow:

Step 1. Before the Assets migration, audit every Field name in the panel against the Assets 10 schema. Identify any field that does not exist in Assets 10.

Step 2. For each missing field, decide:

• Will the field exist in Assets 10 after migration? If yes, no action needed
• Should the field be replaced with a different one in Assets 10? Stage the change in the Configurator behind the migration date

Step 3. During the Assets migration, the panel’s published configuration continues to point at the Assets 6 metadata fields — which are migrated to their Assets 10 equivalents by the Assets migration tooling.

Step 4. After the migration, verify the panel in the new Assets 10 installation. Most things work; any that do not point at metadata fields that did not migrate.

Step 5. If you staged any field replacements in step 2, publish them now.

If you are unsure how the Assets migration handles a particular field, raise a support ticket before the migration date. Field migration questions are easier answered in advance.

Cross-references

• 01 — Introduction to the Workflow Assistant — for where the panel sits in each version of Assets
• 05a — Fields reference — for the Field-name autocomplete behaviour
• 09 — Testing — for the verification habits called out above

Revisions

• 8 May 2026: First publication of the manual