11. Summary and outlook

Rember, this is an alpha-release!

You are not only a developer and/or customer, but also a crash-test dummy.

The API, developer support, limitations and configuration not only may change, but is for sure going to change until the first productive release.

You can help accelerate this process by providing feeback, feature requests or real-world scenario examples.

Recap of this exercise

You have

• Setup a local multi-tenant CAP application
• Subscribed a development tenant
• Created an extension project
• Extended the data model of a CAP application
• Included extensions to the UI, including custom buttons
• Created custom actions and provided implementations for them
• Added custom CRUD event handlers
• Emitted custom events
• Called BADI style exits

Our roadmap

What do we intend to add to CDS-Oyster for the first official release

• Better developer tools support
• More complete documentation
• Ability to configure limits and code validation
• Ability to configure how bad code is sanitized per tenant

What are we hoping to add additionally

• A "plugin" mechanism to supply custom callbacks by application developers
• Expanded QL support - maybe better code completion for queries and where clauses
• Dynamic, annotation driven configuration instead of static in package.json
• A packaged Business Logic Extension Box to provide and mange BADI like, fixed extension points

Thank you for participating!