Scott Spendolini's Blog

Well, it's official.  I am no longer a small business owner. Starting today, I will be working for Enkitec , heading up their APEX products division.  Here, Doug Gault and I will be responsible not only for our existing APEX products - the freshly renamed eFramework and eSERT - but charted with bringing several more to market in the next few months. I'm as excited as they are about this acquisition, as the match makes a lot of sense.  A great deal of their business is based on services, so our APEX knowledge will come in to play daily there.  We'll also be able to get some additional resources for our products & training verticals, so expect to see more announcements on that front - some as soon as next week! You can read the official press release here or on our re-skinned site .

Page Zero in APEX is a powerful tool.  For the uninformed, it allows you to put APEX components  on it and have them render on every other page in your application - unless conditionally set to do otherwise.  Components supported on page zero include regions, items, buttons, branches, computations and dynamic actions. For years now, anytime that I needed a region or item or button on more than one page, I would put it on page zero, and if needed set the condition to display as needed.  It saved a lot of time, as I would only need to create the component once, and was a lot easier to manage as there was only one copy for multiple pages.  As you needed that component to render on additional pages, all that was required was a small change to the condition. Dynamic Actions, which were introduced in APEX 4.0, are in my opinion, the best feature to happen to APEX.  In a nutshell, they make JavaScript development - specifically of the jQuery type - declarative.  You can specify a number of