More of a false alarm than anything else - it seems as if the two issues are resolved in APEX 3.0.1. Upgrading to 3.0.1 or the latest release - APEX 3.1 - should fix the two identified issues.
For those running APEX 3.0, 2.2 or earlier, it looks like it's time to take a look at getting up to date!
For those running APEX 3.0, 2.2 or earlier, it looks like it's time to take a look at getting up to date!
Comments