Hi all, thank so much for your feedback on the RFC. Based on your feedback, I wanted to share the outcomes of this RFC. The discussion will still be unlocked for a few days for any last bits of feedback.
Extension Point Modules
- Based on your feedback, we will not require developers to make Connect app descriptor or Forge manifest updates in order to make their apps using extension point modules appear in Live Docs. That way, customers who are stuck on previous app version will be able to access their apps in Live Docs.
- This means that all apps using extension point modules supported in Live Docs will automatically appear in Live Docs when they are rolled out for general availability (GA).
Timing: We are asking that developers make sure their apps function as desired in Live Docs by May 30, 2025.
API
- The API changes listed in the RFC have already been made available in Developer Canary Program sites.
- Regarding the items that were under consideration:
- We will make sure that subtype is supplied via Forge context as well as AP.context.getContext().
- We will also move forward with a Forge client-side API to get the latest editor content & update it, to allow apps to make instant changes to Live Doc content.
- Timing: For both items above, we are working with the team to understand the work required and will report back with timing.
Connect Webhooks & Forge Events
- The Webhook & Event changes listed in the RFC have already been made available in Developer Canary Program sites.
- Regarding the items that were under consideration:
- We did not hear strong feedback that adding an event / webhook for when a Page is converted to a Live Doc was necessary at this time.
Macros
- Macros will continue to behave as outlined in the RFC.
CQL
- The CQL changes listed in the RFC have already been made available in Developer Canary Program sites.
Other feedback
We also heard other areas of feedback for apps in Live Docs that we do not currently plan to take action on, but will continue to monitor from our developer community.
- Static Content Macros - Desire for output.type to indicate when on a Live Doc & the ability to trigger new renders of a static content macro when editing Live Docs
- Bodied Macros - Desire for a “Done Editing” event & the ability to minimize the size of a container when done editing.