Add a Dependency

You add an extension as a dependency when you want to access the resources in the extension—like service connections, fragments, or Layouts—from your own App UI or fragment.

Note:

Be sure you understand the concepts discussed in What Are Dependencies? before continuing with this topic.

To add an extension as a dependency:

  1. Click Dependencies Dependencies icon in the left Navigator.
  2. Locate the dependency you want in the Dependencies pane, where dependencies are grouped by pillar for easier identification:
    Description of listofdependencies.png follows
    Description of the illustration listofdependencies.png
  3. Click Add next to the extension you want.

    Remember, you don't add an individual App UI or fragment as a dependency, you add the extension containing the App UI.

    Note:

    When you add a dependency, you also implicitly add the dependency's dependencies. For example, if an extension named Extension1 depends on Extension1a, adding Extension1 as a dependency will also implicitly add Extension1a as a dependency. If your extension uses any of the resources in Extension1a, such as fragments or a service connection, it is explicitly added as a dependency.

    To ensure that your extension continues to work, Extension1a will remain a dependency as long as your extension uses its resources, even if Extension1 is removed as a dependency.

After you've added the extension, you'll see it listed under the Installed category on the Dependencies pane. You'll also see it on the App UIs pane under From Dependencies, with its App UIs and fragments listed as child nodes:
Description of extensionaddedasdependency.png follows
Description of the illustration extensionaddedasdependency.png

You can now start configuring the dependent pages or fragments to suit your business needs. When you publish your branch, the changes you make will be laid on top of the base App UI (called personal-information, in this case) at runtime.

Note:

If you look at your extension in Source view, you'll find that dependencies are not listed there until you have actually configured them in some way. In other words, they are not considered part of your extension until you have modified them in your Git repo.