Issue Summary

When an automation rule changes a JSM Form's state (e.g., from "Locked for edits" to "Open for edits"), the issue view does not automatically reflect the updated form state. Users must manually refresh the browser page to see the change.

Steps to Reproduce

1. A form is set as "Locked for edits"
2. A form submission triggers an automation rule that updates the form status to "Open for edits"
3. The automation executes successfully, and the form is unlocked
4. The issue view continues to display the form as "Locked for edits" until the user manually refreshes the browser
5. After a manual page refresh, the form correctly reflects the unlocked state

Expected Results

Once the automation completes and changes the form lock state, the issue view should automatically update the form panel to reflect the new state without requiring a manual browser refresh.

Users should immediately see that the form is unlocked and available for editing.

Actual Results

The form appears "Locked for edits" until the user manually refreshes the browser page.

Workaround

Currently, users must manually refresh the browser page.