APEX Application lifecycle with feature based deployment

APEX application deployment is mostly done by exporting the application and importing it into the target environment. But what if your team continuously develops (as they should), where do you stop developing to start preparing your release-deployment? You should be able to deploy based on features; without your developers having to halt their development. Using the deployment-method explained in this presentation you will be able to do just that. The method includes things like Code versioning (GIT), Feature-tickets (Jira), Code Review (Quality), Automated Deployment using Jenkins and Flyway. When implemented you will be able to successfully and predictively deploy your APEX applications (including underlying database objects) to the different deployment-environments. With a few modifications you can even upgrade the methodology to be a ""continuous delivery"" methodology.

Cookie Cutter APEX Applications

In a perfect world your APEX SAAS solution would be deployed with a click of a button, have a separate database for each customer, and can a customer choose when they want to upgrade to the next version. In this perfect world, the customer don't have to worry about default lookup data, because the SAAS provider does that. This perfect world can be created with Application Containers and Oracle APEX. In this session you will learn the basics of Application Containers, how data is shared and separated in each container and how a new version is rolled out.

Real life ORDS; REST in pieces

ORDS plays an important role in the APEX architecture. Next to the database and the browser it is a key component to run any APEX application. But on top of "just" running your APEX application, it also opens up the possibilities of using all kind of RESTful services and features to enhance your application with data that comes from or is send to other sources. This session will cover a number of examples that we created in order to build the application landscape we have today.

Play against vulnerability with APEX

Do you know that half of the cyber-attacks are never detected? Can you tell if your APEX application is secured? We CAN!

Do you know why? Because we included in the development lifecycle a process to check vulnerabilities and verify the security of our APEX application. This process can and should be included into your development process as well.

In this session we’ll discuss the type of security risks an APEX application can expose, and how our team is doing the evaluation of these risks.

You will find out about the free tools, paid tools and do-it-yourself tools you can use to verify the vulnerability of the system during the development process or gather information on a running system to identify intruders.

The session is inspired by security-check processes we are using in a few projects. It covers technical details as well as project planning, and it is addressed to developers, team leaders, and project managers.

Understanding auto-rest (ORDS on steroids)

The Oracle Restful Data Services allow to "rest-enable" database objects like Tables, Views, Procedures and Functions. This includes data-retrieval and data-manipulation. Using a few simple directives in the URL you can search for specific records, order the result set or even limit the amount of records retrieved. On top of that the ORDS will automatically show you the resulting JSON The session focuses on the creation and use of autorest enabled services on objects. The creation section (1st half) focuses on the right format of your JSON result. The seconds half covers consuming these services; how to do CRUD operations, how to search the for data, how to paginate etc.

Where it all comes together, secured payments with APEX

Every Oracle release new features are introduced, but when to use them? In this presentation we are not diving deep into one specific feature but make use of a few to implement a payment interface with Oracle APEX. You will see everything you need to know to build an interace like that. I will also share the difficulties you will encounter building an interface like this. So if you want to know more about a real life use case for authentication, REST communication, JSON in the database and Webhooks this presentation will certainly please you. I will use Mollie as a payment provider.

Enemy of the Session State

This session will cover mistakes that are easily made - even by experienced developers - regarding the (mis)use of APEX Session State, database session contexts and caching. Hopefully this will prevent you to fall in a similar pitfall and stop you from being an enemy of the session state!

To V or not to V? or.. using SQL Macros in APEX?

The V function has been around APEX as long as ... let's say very long and that's a long time. The V function allows you to reference item values from session state in your SQL statements. When calling V there would always be a price to pay. With recent releases of the database there is a new way to do something similar; SQL Macro. With SQL Macro you can create parameterized views and this could be very interesting for APEX Developers. In this session I will give you an overview of this new functionality and how you can use it in your APEX applications.