Collecting data for Cúram Action View Issues

 Collecting data for Cúram Action View issues. 

1. Issue Description

Provide a clear and detailed description of the problem:

• What behaviour are you seeing?

• When did the issue start?

• Is the issue consistent or intermittent?

2. Steps to Reproduce

Please outline step-by-step instructions to reproduce the issue:

• Include all relevant navigation steps

• Specify if the issue occurs in a standard (out-of-the-box) environment  
  

3. Screenshots / Evidence

• Include screenshots clearly showing the issue

• Highlight the relevant sections (e.g. errors, missing data, incorrect values)

 4. Environment Details 

 Please provide:

• Exact version of Cúram the project are running

• Exact version of Cúram Action View the project are running

• Browser type (e.g. Chrome, Edge)

• Browser version
  

 5. HAR file Export

 Cúram Action View has a mix of GraphQL and standard rest APIs. To help analyse backend behaviour, include:

• A HAR file captured when reproducing the issue.

How to capture this:

• Open your browser and navigate to the page where the issue is occurring.

• Right-click anywhere on the page and select Inspect (or press F12).

• Click on the Network tab.

• Look for a record button (a red circle) in the top-left corner of the Network tab to ensure it is actively recording.

• Check the box for Preserve log so it doesn't clear your history when you navigate pages.

• Click the Clear icon (a circle with a diagonal line) to clear out old logs.

• Reproduce the error or issue you are experiencing (e.g., refreshing the page, clicking a broken button).

• Once the issue is captured, click the Export HAR icon (often a download arrow or labeled Export) to save the file to your computer.

 6. Configuration Check

 Confirm the following system configuration: 

• Property: curam.graphql.endpoint.enabled

• Expected value: true

This can be verified in the System Administration section of Cúram.

 7. Logs and Installation Details

 Please attach

• Relevant server-side logs showing errors (if available)

• Install history file:

  • Location:

  • /Installer/Installhistory.txt

 8. Expected vs Actual Behaviour

 Clearly describe:

•  Expected behaviour (what should happen)

• Actual behaviour (what is happening instead)

 9. Issue Severity

Please indicate the severity based on business impact:

•  Severity 1 (Critical)

     User cannot perform the business function or service

• Severity 2 (High)

    User is not blocked but significantly impacted

• Severity 3 / 4 (Medium/Low)

    User can continue working with minor or minimal disruption

 ✅ Tips for Faster Resolution

• Provide as much detail as possible upfront

• Include reproducible steps

•  Attach logs and HAR file wherever applicable