Change management baseline reports stuck showing old data pol-2406

ALM Siemens Polarion ALM
, , , , , , , ,
1

Our change management baseline reports are showing data from 3 weeks ago despite multiple baseline publications. We’ve published new baselines for our compliance audit trail, but the LiveDoc widgets and report queries still reference the old snapshot.

We’ve tried:

  • Republishing baselines through the change-mgmt module
  • Clearing browser cache
  • Checking baseline publishing permissions

The report query syntax appears correct, and users have proper LiveDoc permissions. The widget cache might be holding stale data, but we can’t figure out how to force a refresh. This is blocking our quarterly audit compliance review.

Has anyone encountered baseline publishing delays in reporting widgets? We need these reports to reflect current baseline data for our audit next week.

2

We had similar issues last quarter. Our problem was LiveDoc permissions weren’t propagating to the new baseline snapshots. Even though users could view the baseline, the report widgets were still querying against the old one due to permission caching. Try checking the effective permissions on the latest baseline object itself, not just the parent document.

3

Check your Polarion server cache settings. LiveDoc widgets cache aggressively for performance. You might need to restart the Polarion service or clear the server-side cache manually. We’ve had to do this after major baseline publications to force widget refresh in our change-mgmt reporting.

4

Beyond server restart, check if your report queries are using the correct baseline scope. Sometimes the widget configuration references a specific baseline ID that doesn’t auto-update. You might need to edit the LiveDoc page and update the widget’s baseline parameter to point to your new baseline explicitly.

5

Good point about permissions. I checked and the baseline object permissions look correct - all audit users have read access. The query syntax uses explicit baseline IDs, not “latest” resolution. Still seeing old data in the widgets though. Could this be a server-side cache issue rather than browser cache?

6

I encountered this exact issue in pol-2406 and found the root cause. Let me address each focus area systematically:

Baseline Publishing: The baseline itself publishes correctly, but there’s a secondary cache invalidation step that often fails. After publishing, you need to trigger a manual cache clear.

Widget Cache: This is the primary culprit. LiveDoc widgets maintain their own cache layer separate from browser cache. Solution:


// Clear widget cache via REST API
DELETE /polarion/rest/v1/projects/{projectId}/cache/widgets
Authorization: Bearer {admin_token}

Report Query Syntax: Your queries need to use dynamic baseline resolution. Instead of:

SELECT * FROM workitems WHERE baseline_id='BASELINE-123'

Use:

SELECT * FROM workitems WHERE baseline_id IN
  (SELECT id FROM baselines WHERE status='published'
   ORDER BY created DESC LIMIT 1)

This ensures queries always reference the latest published baseline.

LiveDoc Permissions: Verify that the service account running the report engine has explicit read permissions on the baseline object. Go to Administration > Baselines > [Your Baseline] > Permissions and add the polarion service account with read access.

Complete Fix Procedure:

  1. Publish your baseline through change-mgmt module
  2. Call the REST API to clear widget cache (see above)
  3. Update report query syntax to use dynamic baseline resolution
  4. Verify service account permissions on baseline object
  5. Refresh LiveDoc pages (Ctrl+F5)

After implementing these steps, our baseline reports now update within 2 minutes of publication. The key was combining the widget cache clear with dynamic query syntax - neither alone solved it completely.

For your audit next week, I’d recommend setting up a scheduled task to clear widget cache after each baseline publication to prevent this recurring.