Details:

As vendors across the Atlassian ecosystem prepare to migrate Confluence apps from Connect to Forge, a critical gap has been identified in Forge platform capabilities: the inability to programmatically refresh the Confluence byline once it has been rendered.

In Connect, this is achievable using AP.confluence.syncPropertyFromServer, which allows dynamic updates to the byline in response to real-time changes in page state or properties. This functionality is vital to ensure an accurate and responsive user experience, especially in scenarios involving:

• Initial state assignment: When a document is first assigned metadata or a workflow state upon creation or migration.

• Page edits: When users make changes to a page and expect the byline to reflect updated information after returning to view mode.

• Byline-based interactions: When users interact with custom byline dialogs and expect the main byline UI to stay in sync.

Forge currently lacks a mechanism to trigger a re-render or refresh of the byline programmatically. As a result, developers are forced to resort to less optimal solutions such as full-page reloads, which detract from the user experience and introduce UX inconsistencies compared to native Confluence functionality.

Suggestion:

Introduce a Forge-supported API or event mechanism to allow Forge apps to programmatically trigger a refresh of the byline UI in response to changes in app state or storage.

Benefits:

• Enables a seamless and responsive user experience

• Aligns Forge feature parity with existing Connect capabilities

• Facilitates more robust and dynamic app experiences within Confluence

• Eases the migration path for existing apps without compromising on UX