Skip to main content

Reusable Admin Views

Across Multiple Components

Joomla! Component Builder (JCB) empowers developers to define admin views once โ€” and reuse them across multiple components in the same JCB instance. Instead of recreating views, fields, layouts, and logic repeatedly, you can blueprint reusable views that behave like shared templates, keeping your backend UI and logic consistent, DRY (Don't Repeat Yourself), and versionable.

This approach helps streamline large ecosystems where multiple components share the same data structure or UI functionality โ€” such as dashboards, logs, reports, or reusable CRUD interfaces.

What Is a "Reusable Admin View"?

A reusable admin view in JCB is a fully designed backend view that includes:

Fields

Filters

Forms (edit view)

List view layout

Permissions

Custom logic

Templates

Language strings

Once defined, it can be linked into multiple components. This way, any improvements or logic changes to the original view can be reflected across all components that include it.

Benefits of Reusing Views

  • Centralized updates: fix or improve once, apply everywhere
  • Consistent interface and behavior across components
  • Faster prototyping for new components
  • Modular architecture: break down large systems into small, shared view units

Example Use Case

Imagine youโ€™ve built a component for managing support tickets (com\_support) and another for managing customer assets (com\_assets). Both need a "Logs" admin view showing action history.

With JCB, you can:

โœ… Create a reusable admin view called "Action Log"
โœ… Define its fields (date, user, action, context), permissions, and layout
โœ… Link it into both components
โœ… Optionally override certain behavior/context per component if needed

When compiling, JCB will include the "Action Log" view in both components, resolving language strings and links appropriately.

How to Reuse a View

  • In Component A:
    • Create a new Admin View
    • Add fields, layout, filters, and logic as usual
    • Mark it as reusable (by naming convention or tagging it)
  • In Component B:
    • Add a new Admin View
    • Select a Existing View (select from existing blueprints)
    • This will Reuse the view from Component A
  • Customize the link:
    • Set alias if needed
    • Set permissions, menu entry, or view name
    • Apply component-specific layout overrides if required
  • Compile Component B โ€” the reused view will be included and scoped to it.

Whatโ€™s Reused?

The following are included from the source view:
  • Fields and filters
  • Field settings and validation
  • Layouts and templates
  • Custom code blocks
  • Language strings (auto-renamed per component context)
  • View permissions and field ACL
You can override any of these locally if needed without breaking the link to the shared view.

Can You Sync Reused Views?

Yes! If the source view is updated, all components referencing it can recompile and receive the new version. You can even track differences between whatโ€™s compiled and whatโ€™s stored.

Are There Limitations?

View names must remain unique per component (Joomla requirement)

You cannot use views from a component that hasnโ€™t been imported

Reused views cannot span database tables unless specifically designed to do so

Related Features

Summary

Reusable admin views in JCB help you:

  • โœ… Reuse powerful interfaces across components
  • โœ… Avoid duplication of effort
  • โœ… Maintain UI/logic consistency
  • โœ… Scale quickly across projects

Build once. Use everywhere!