Oracle APEX Development Process/Flow

user_4520244 0
Viewed 240

These are more high level questions, but our team is new to developing with APEX. We are currently a team of 3. We are using APEX 19.2, but are planning to upgrade up to 21.1

  1. How do others handle the development flow, versioning, and releases of their projects when working in APEX?

We put majority of the business logic (validations, source sql, and process handling) in packages. So I feel it is pretty easy to version those files as they are outside of the APEX UI and can version in Git accordingly, but how do others version control all the APEX UI changes (pages, regions, items, DAs, etc...)?

I've searched and haven't really stumbled upon best practices of how teams, that use APEX, conduct their development process. One thing I'm nervous about is branching changes inside APEX UI. Sometimes we are given a requirement (say A) and we are asked to hold that release, but start working on requirement B. We may even release B before A gets final approval.

  1. Are there any best practices, to ensure that developers working in the same workspace do not collide with others work? Luckily most of our project tasks do not overlap, but curious how others handle this

Any links or tips to this would be appreciated as we are new to APEX and trying to work these things out up front.

oracle-apex oracle
2 Answers

I'm probably not the right person to answer as my Apex team consists of 1 (one) member - me.

However:

We put majority of the business logic (validations, source sql, and process handling) in packages.

Me too, I found that to be the best option. Keep as little code on pages themselves as possible.

As of team development, did you read Managing the Application Life Cycle with Team Development?

Tracking Features might be particularly interesting for you. For example, it contains

Approval status of the feature. Indicates if the feature is to be implemented and the current progress.

which sounds like what you asked for.

I hope that someone - who really works in a team - will see your question and answer; I'd be interested in reading about their experiences and suggestions as well.

user_90979060

When we export application as zip , we can see there is folder structure. So in git we have to follow the same directory structure so it is easy to review and for versioning.

Thanks, Nagaraju P

user_181365230
Related