Prerequisites
- Polarion Admin role
- Access to the new solution version package (
.polarion or .zip file)
- Active backup of the project (see Backup and Restore Project)
- All users logged out of the project during the update
Always create a full project backup before updating the solution. Updates may modify custom fields, workflows, and configurations that cannot be easily rolled back. Support ticket patterns show that failed updates without backups result in data loss.
Steps
1. Download the New Solution Version
Obtain the TestAuto2 solution package from Nextedy. The package typically includes:
- Updated work item type definitions
- New or modified RTM domain model configurations
- Updated Risksheet and PowerSheet configurations
- Dashboard and report template updates
- Bug fixes and security patches
2. Review the Changelog
Before applying the update, review the solution changelog to understand:
- Breaking changes to custom fields or link roles
- New features requiring additional configuration
- Deprecated features being removed
- Database migration requirements
3. Access Polarion Administration
- Log in to Polarion as an administrator
- Navigate to Administration ⚙️ → Extensions & Plugins
- Locate TestAuto2 — Automotive Safety Solution in the installed solutions list
4. Upload the New Version
- Click Upload Solution or Update next to the existing TestAuto2 entry
- Select the new solution package file
- Review the update summary showing which components will be modified:
| Component | Modified | New |
|---|
| Work Item Types | 3 | 2 |
| Custom Fields | 5 | 1 |
| Workflows | 1 | — |
| RTM Models | 2 | — |
| Risksheet Configs | 4 | 1 |
| PowerSheet Configs | 3 | — |
| Velocity Macros | 2 | 3 |
- Click Confirm Update
5. Verify Component Activation
After upload completes, verify that all solution components are properly activated:
| Component Type | Verification Method |
|---|
| Work Item Types | Administration → Work Items → Types (check for new types) |
| Custom Fields | Administration → Work Items → Custom Fields (verify new fields) |
| Workflows | Administration → Work Items → Workflows (check updated states) |
| RTM Models | Navigate to any PowerSheet → should load without errors |
| Risksheet Configs | Open any FMEA document → Risksheet should render correctly |
| Dashboards | Visit Home page → widgets should display updated metrics |
For teams with 50+ users, consider updating a test/sandbox project first. Verify the update works correctly before applying to production projects. This allows you to identify configuration conflicts early.
6. Clear Browser Caches
Instruct all users to clear their browser cache or perform a hard refresh (Ctrl+Shift+R / Cmd+Shift+R) to load updated JavaScript modules and CSS:
- Risksheet Tours: Updated Driver.js tours with new feature highlights
- Traffic Lights: Updated completion status indicators
- Dashboard Widgets: New KPI calculations
Browser caching can cause users to see old Risksheet behavior after updates. Support tickets show this is the most common post-update issue. Clear cache server-side in Polarion Administration → System Settings → Clear All Caches if users report inconsistencies.
7. Test Critical Workflows
Perform smoke tests on key workflows to ensure the update did not break existing functionality:
- HARA: Create a new hazard → assess SEC → verify ASIL calculation
- FMEA: Open existing DFMEA → add failure mode → verify Action Priority formula
- Traceability: Open Whole RTM PowerSheet → expand requirements → verify downstream links display
- Reports: Generate Safety Readiness Scorecard → verify all metrics render
- Workflows: Submit a risk specification for review → verify workflow transitions work
8. Review Update Logs
Check Polarion logs for any errors during the update process:
- Navigate to Administration → System Logs
- Filter logs by timestamp matching the update time
- Look for ERROR or WARN level messages related to TestAuto2 components
Common update issues logged:
Custom field 'xxx' already exists with different type → Manual field reconciliation neededWorkflow state 'yyy' not found → Workflow migration incompleteRTM model validation failed → Check for link role mismatches
Verification
You should now see:
- The new version number displayed in Administration → Extensions & Plugins → TestAuto2 — Automotive Safety Solution
- Updated dashboards with new widgets or metrics (if included in the release)
- New Risksheet configurations available when creating FMEA documents
- Updated tour steps when launching the Risksheet intro tour (▶ Intro Tour button in footer)
See Also
