Extending OpenDXP

When building solutions with OpenDXP, normally one starts with configuring an object data model, create custom controller, actions and templates, creating documents and so on. Lots of things are possible without extending OpenDXP itself. But depending on the desired result, sometimes it is necessary to extend the default functionality of OpenDXP.

OpenDXP provides several ways for extension for that purpose. Depending on the use case one or the other way may fit best.

Following a list of ways to extend OpenDXP. See detail pages for additional information:

• Add your own Dependencies and Packages for loading external libraries and functionalities to be available in custom code.

• Use Overriding Models to overwrite OpenDXP default models.

• Configuration regarding configuration (e.g. overwriting OpenDXP constants like assets directory, temporary directory etc.)

• Parent Class for Objects to inject additional functionality to OpenDXP object classes.

• Event API and Event Manager for hooking into standard OpenDXP functions like creating, updating, deleting elements etc.

• Use Maintenance Mode to show users a maintenance page when changing system configurations. You also can create a custom maintenance page.

• Use Maintenance Task to register new maintenance task

• Add Custom Persistent Models to save additional information.

• Create Bundles and OpenDXP Bundles when you want to add complex and extensive functionalities to OpenDXP.