Extending your app with Forge

With your Forge app running, you can now explore what Forge has available.

• Add new Forge modules in your new manifest.yml file.

• Build user interfaces in Forge with custom UI or UI Kit.

• Explore what else you can do with Forge tutorials and guides.

• See Connect/Forge module equivalents to potentially replace existing Connect modules.

Communicating between Connect and Forge

Your app can communicate between the Connect and Forge components through:

1. Apps can share data via entity properties or content properties.

   If you keep both a Connect confluenceContentProperties module and a Forge confluence:contentProperty module in the same app, their CQL aliases share one namespace. Reusing the same alias on both will break CQL search on every tenant that installs the app. Either remove the Connect module when you add the Forge one, or give the Forge aliases different names.

2. Forge apps can communicate with an existing Connect backend through Forge remote. We now have support in:

   • Atlassian Connect Express (ACE)
   • Atlassian Connect Spring Boot (ACSB)

3. Connect apps can call Forge web triggers.

4. Forge apps can access Connect app properties (as long as they are stored against the same app.connect.key).