Artificial Intelligence is changing how we interact with databases. What once required complex SQL can now be expressed in plain English — “Show me my Q1 revenue”, “Summarize customer expenses”, or “List anomalies in spending”.

With Oracle Select AI, built directly into Oracle Autonomous Database (23ai and later), these natural-language prompts are instantly transformed into grounded, secure SQL queries. Better yet, the results can be executed, explained, or narrated into human-friendly summaries.

But raw AI is dangerous without guardrails. Hallucinations, unauthorized table access, or incorrect financial summaries can lead to compliance issues. That’s why AI Profiles exist — configurable blueprints that govern exactly how your AI interacts with your data.

This guide walks you through end-to-end Select AI implementation using OpenAI, including:

• Required privileges

• Creating secure OpenAI credentials

• Building production-grade AI profiles

• Using SELECT AI to generate SQL

• APEX integration

• Real financial query use cases

• Best practices to eliminate hallucinations

Whether you're an APEX developer, a data engineer, or a DBA, this tutorial equips you with everything needed to build safe and intelligent AI-driven financial analytics.

Why AI Profiles Matter in Select AI

Select AI may feel magical, but it is far from a black box. Each natural-language query goes through three controlled stages:

1. Understanding: The prompt is sent to an LLM (OpenAI, OCI, Cohere, Azure OpenAI).

2. SQL Generation: The LLM converts the intent into SQL using schema knowledge.

3. Execution or Narration: The SQL is executed, explained, or summarized.

Without profiles, this process is open-ended — which is risky.

AI Profiles solve this by enforcing strong rules:

Grounding

Tell the model exactly what tables it is allowed to use.

Model governance

Choose the right model (e.g., gpt-4o-mini) with the right temperature.

Cost control

Limit tokens, output size, and creativity.

Security & Compliance

Block access to sensitive schemas, restrict objects, and enforce constraints.

Repeatability

Ensure the same prompt always results in consistent SQL.

This is especially critical for finance, where a miscalculated revenue total can trigger audits.

Step 1: Grant Required Access

Run as ADMIN:

GRANT EXECUTE ON DBMS_CLOUD_AI TO WKSP_TESTING;
GRANT EXECUTE ON DBMS_CLOUD TO WKSP_TESTING;

-- Replace WKSP_TESTING with your APEX workspace schema.

Step 2: Create OpenAI Credentials

BEGIN
  DBMS_CLOUD.CREATE_CREDENTIAL(
    credential_name => 'OPENAI_CRED',
    username        => 'OPENAI',
    password        => 'sk-proj-xxxxxxxxxxxxxxxx'
  );
END;
/

-- Verify
SELECT credential_name FROM user_credentials;

Step 3: Create a Financial Demo Table

   CREATE TABLE financial_records (
    transaction_id NUMBER PRIMARY KEY,
    transaction_date DATE,
    amount NUMBER(10,2),
    category VARCHAR2(50),
    description VARCHAR2(255),
    customer_id NUMBER
);

Insert data:

INSERT INTO financial_records VALUES (1, TO_DATE('2025-01-15', 'YYYY-MM-DD'), 1500.50, 'Revenue', 'Q1 Sales Invoice', 101);
INSERT INTO financial_records VALUES (2, TO_DATE('2025-02-20', 'YYYY-MM-DD'), -750.00, 'Expense', 'Office Supplies Purchase', 101);
INSERT INTO financial_records VALUES (3, TO_DATE('2025-03-10', 'YYYY-MM-DD'), 2000.00, 'Revenue', 'Client Payment', 102);
INSERT INTO financial_records VALUES (4, TO_DATE('2025-04-05', 'YYYY-MM-DD'), -1200.00, 'Expense', 'Travel Reimbursement', 102);
INSERT INTO financial_records VALUES (5, TO_DATE('2025-05-25', 'YYYY-MM-DD'), 3000.00, 'Investment', 'Stock Dividend', 101);

COMMIT;

This dataset powers all use cases in this guide.

Step 4: Create a Production-Ready AI Profile

This is the most important section.

The profile below forces the model to:

• Use OpenAI models

• Never access unauthorized tables

• Generate deterministic SQL (temperature = 0.1)

• Always include schema constraints

• Limit its world to one table

BEGIN
  DBMS_CLOUD_AI.CREATE_PROFILE(
    profile_name => 'FIN_AI_PROFILE',
    attributes   => '{
      "provider": "openai",
      "credential_name": "OPENAI_CRED",
      "model": "gpt-4o-mini",
      "temperature": 0.1,
      "max_tokens": 2048,
      "comments": "true",
      "constraints": "true",
      "enforce_object_list": "true",
      "object_list": [
        {"owner": "WKSP_TESTING", "name": "FINANCIAL_RECORDS"}
      ]
    }',
    description => 'Constrained AI for financial SQL queries'
  );
END;
/

Your AI assistant is now securely grounded.

Step 5: Run Natural Language Queries Using SELECT AI - Testing the AI Connection

This is where the magic happens.

SELECT DBMS_CLOUD_AI.GENERATE(
  prompt        => 'how many customers',
  profile_name  => 'FIN_AI_PROFILE',
  action        => 'narrate'
) 
FROM DUAL;

Using SELECT AI Over Financial Data

Now let’s move into finance-focused real-world use cases.

Example 1 — Summaries of Monthly Revenue

SELECT DBMS_CLOUD_AI.GENERATE(
  profile_name => 'FIN_AI_PROFILE',
  action       => 'narrate',
  prompt       => 'summarize monthly revenue trend from our records'
)
FROM dual;

Expected output example:

Example 2 — Detect Unusual Expenses

SELECT DBMS_CLOUD_AI.GENERATE(
  prompt       => 'identify unusual expenses from transactions table. look at amounts above average',
  profile_name => 'FIN_AI_PROFILE',
  action       => 'narrate'
)
FROM DUAL;

Expected output example:

Example 3 — Cashflow Insights From Multiple Tables

SELECT DBMS_CLOUD_AI.GENERATE(
  prompt       => 'explain overall cashflow combining inflow from payments and outflow from expenses',
  profile_name => 'FIN_AI_PROFILE',
  action       => 'narrate'
)
FROM DUAL;

This allows accountants or managers to query the system conversationally—without writing SQL.

Expected output example:

Example 4 — Natural-Language SQL Generation

SELECT DBMS_CLOUD_AI.GENERATE(
  action       => 'showsql',
  prompt       => 'write sql to calculate total outstanding invoices grouped by client',
  profile_name => 'FIN_AI_PROFILE'
)
FROM DUAL;

The model returns runnable SQL.

Expected output example:

SELECT "CUSTOMER_ID" AS client_id, SUM("AMOUNT") AS total_outstanding_invoices FROM "WKSP_TESTING"."FINANCIAL_RECORDS" GROUP BY "CUSTOMER_ID"

Example 5 — Natural-Language SQL Explanation

Useful for understanding SQL queries.

SELECT DBMS_CLOUD_AI.GENERATE(
  action       => 'explainsql',
  prompt       => 'write sql to calculate total outstanding invoices grouped by client',
  profile_name => 'FIN_AI_PROFILE'
)
FROM DUAL;

Expected output example:

To calculate the total outstanding invoices grouped by client, you can use the following SQL query: ```sql SELECT "CUSTOMER_ID", SUM("AMOUNT") AS "TOTAL_OUTSTANDING_INVOICES" FROM "WKSP_TESTING"."FINANCIAL_RECORDS" GROUP BY "CUSTOMER_ID"; ``` In this query: - We are selecting the `CUSTOMER_ID` column to identify each client. - Using the `SUM` function to calculate the total outstanding amount for each client by summing up the `AMOUNT` column. - Grouping the results by the `CUSTOMER_ID` column to get the total outstanding invoices for each client.

Example 6 — Using runsql to Count Customers

SELECT DBMS_CLOUD_AI.GENERATE(
  prompt       => 'how many customers',
  profile_name => 'FIN_AI_PROFILE',
  action       => 'runsql'
)
FROM dual;

The model receives the prompt “how many customers”

It generates SQL such as:

SELECT COUNT(*) AS total_customers FROM customers;

It immediately executes that SQL

It returns the result set—for example:

[ { "Total_Customers" : 2 } ]

Best Practices for Finance + AI in Oracle

Restrict AI profile usage

Limit to read-only schemas or views.

Don’t send sensitive data in prompts

Mask or anonymize customer names, account numbers, or ID numbers.

Log all AI requests

For auditing and governance.

Wrap prompts inside PL/SQL packages

So developers use predefined prompts rather than free text.

APEX Integration (Optional)

Automation ideas:

AI-Powered Financial Assistant Page

Users can ask:

• “How much did we spend on marketing last quarter?”

• “What is our profit margin trend?”

• “What is the forecast for next 3 months?”

Behind the scenes, the APEX page issues the SELECT DBMS_CLOUD_AI.GENERATE call.

Conclusion

Integrating OpenAI with DBMS_CLOUD_AI transforms your Oracle database into an intelligent analytics engine. Finance teams, managers, and executives can ask natural-language questions and receive clear, actionable insights—without writing complex SQL.

This approach brings real AI capability directly into APEX apps and financial data workflows, making your system more interactive, more intuitive, and more valuable.

#HappyAPEXING

As an Oracle APEX dev who's wrangled more low-code beasts than I care to admit, I've hacked together an error-handling system that leverages APEX_AI.CHAT to automate the "what now?" moment. No more frantic Oracle Docs dives or Stack Overflow rabbit holes. This setup logs errors autonomously, queries AI for tailored solutions, and emails you a ready-to-deploy battle plan. Designed specifically for Oracle APEX to demonstrate real-world use cases of the APEX AI APIs.

Let's unpack the code, setup, and why this is your new best friend. Grab your coffee as we're automating the chaos.

The Error Handling Blues: Why We Need AI Now More Than Ever

In APEX, errors lurk everywhere: PL/SQL processes, AJAX callbacks, dynamic reports, you name it. Traditional handling? Wrap in EXCEPTION WHEN OTHERS THEN... and hope for a log. But that's reactive. With APEX_AI (powered by Oracle's generative AI integrations), we go proactive: Analyze the error stack in real-time, generate fixes, and log it all.

Key wins:

• Instant Insights: AI parses DBMS_UTILITY.FORMAT_ERROR_STACK and suggests solutions like divisor is equal to zero (ref: ORA-01476 Docs)".

• Audit Trail: Everything hits a central table for post-mortems.

• Notifications: Email alerts with the full information in real time, no Slack pings at midnight.

• Scalable: Autonomous transactions ensure logs stick, even if the main op rolls back.

This isn't sci-fi; it's PL/SQL + AI, deployable in minutes.

Step 1: The Foundation – Your Error Log Table

Start with a simple audit table. It's your single source of truth for errors, AI responses, and context. I've kept it lean but powerful by utilizing Basic Error Logging Package by Steven Feuerstein. Note: I just added some extra meat to make it spicy for our implementation.

CREATE TABLE error_log (
    log_id NUMBER GENERATED ALWAYS AS IDENTITY PRIMARY KEY,
    created_on TIMESTAMP WITH LOCAL TIME ZONE DEFAULT SYSTIMESTAMP,
    created_by VARCHAR2(100) DEFAULT USER,
    error_code INTEGER,
    app_id NUMBER,
    page_id NUMBER,
    session_id VARCHAR2(255),
    error_info VARCHAR2(4000),
    call_stack VARCHAR2(4000),
    error_stack VARCHAR2(4000),
    back_trace VARCHAR2(4000),
    ai_fix_suggestion CLOB
);

• Core Fields: Timestamps, user, and raw error message via SQLCODE and DBMS_UTILITY.

• APEX Context: APP_ID, PAGE_ID, etc., for pinpointing exact application.

• AI Columns: Separate CLOBS for explanation and structured responses.

Index on created_on and error_code for quick queries:

CREATE INDEX idx_error_log_date ON error_log(created_on);
CREATE INDEX idx_error_log_code ON error_log(error_code);

Step 2: The Hero Package – ErrorHandler with APEX_AI.CHAT

Meet error_handler_pkg: A spec/body duo that wraps the magic. The star is handle_exception, called from your WHEN OTHERS. It sets an autonomous transaction, chats with AI, logs, and emails.

Package Specification

create or replace PACKAGE error_handler_pkg
AS
    -- Custom exception for bulk errors
    bulk_error EXCEPTION;
    PRAGMA EXCEPTION_INIT(bulk_error, -24381);

    -- Main handler: Call from your exception blocks
    PROCEDURE handle_exception(p_context IN VARCHAR2 DEFAULT NULL);

END error_handler_pkg;
/

Package Body: AI-Powered Explanation Engine

create or replace PACKAGE BODY error_handler_pkg
AS
    PROCEDURE handle_exception(p_context IN VARCHAR2 DEFAULT NULL)
    IS
        PRAGMA AUTONOMOUS_TRANSACTION; -- Logs commit independently

        l_error_code INTEGER := SQLCODE;
        l_ai_messages APEX_AI.T_CHAT_MESSAGES;
        l_ai_response CLOB;
        l_email_body CLOB;
        l_message_id NUMBER;
        l_explanation CLOB;  
        l_fix CLOB;          

        -- Grab APEX session context
        l_app_id NUMBER := V('APP_ID');
        l_page_id NUMBER := V('APP_PAGE_ID');
        l_session_id VARCHAR2(255) := V('APP_SESSION');
        l_user VARCHAR2(100) := NVL(V('APP_USER'), USER);
        l_workspace VARCHAR2(100) := V('WORKSPACE_NAME');

        -- Structured AI prompt for explanation + fix
        l_prompt VARCHAR2(4000) :=
            'Error Stack: ' || DBMS_UTILITY.FORMAT_ERROR_STACK ||
            CHR(10) || 'Context: ' || NVL(p_context, 'No additional info') ||
            CHR(10) || 'Provide: 1) Clear explanation. 2) Step-by-step fix. 3) Oracle doc refs.';

    BEGIN

        APEX_UTIL.SET_SECURITY_GROUP_ID(
            P_SECURITY_GROUP_ID => APEX_UTIL.FIND_SECURITY_GROUP_ID('WKSP_TESTING')
        );

        -- Chat with APEX AI: Get explanation and fix
        l_ai_response := APEX_AI.CHAT(
            P_MESSAGES => l_ai_messages,
            P_SYSTEM_PROMPT => 'You are an elite Oracle APEX and PL/SQL troubleshooter. Respond in structured format: EXPLANATION: [why]. FIX: [steps with code]. REFERENCES: [docs links]. Keep it concise yet actionable.',
            P_PROMPT => l_prompt,
            P_SERVICE_STATIC_ID => 'ai_assistant' 
        );


        DECLARE
            l_pos NUMBER := INSTR(l_ai_response, 'FIX:');
        BEGIN
            l_explanation := SUBSTR(l_ai_response, 1, l_pos - 1);
            l_fix := SUBSTR(l_ai_response, l_pos);

            -- Log to table
            INSERT INTO error_log (
                error_code, app_id, page_id, session_id, error_info,
                call_stack, error_stack, back_trace,
                ai_fix_suggestion
            ) VALUES (
                l_error_code, l_app_id, l_page_id, l_session_id, p_context,
                DBMS_UTILITY.FORMAT_CALL_STACK,
                DBMS_UTILITY.FORMAT_ERROR_STACK,
                DBMS_UTILITY.FORMAT_ERROR_BACKTRACE,
                l_fix
            );
        END;

        -- Send Email to Admin
        l_email_body :=
            'APEX Error Alert' || UTL_TCP.CRLF || UTL_TCP.CRLF ||
            'Timestamp: ' || TO_CHAR(SYSTIMESTAMP, 'YYYY-MM-DD HH24:MI:SS TZH:TZM') || UTL_TCP.CRLF ||
            'App ID/Page: ' || l_app_id || '/' || l_page_id || UTL_TCP.CRLF ||
            'User/Session: ' || l_user || '/' || l_session_id || UTL_TCP.CRLF ||
            'Error Code: ' || l_error_code || UTL_TCP.CRLF || UTL_TCP.CRLF ||
            'AI EXPLANATION:' || UTL_TCP.CRLF || l_explanation || UTL_TCP.CRLF || UTL_TCP.CRLF ||
            'AI FIX SUGGESTION:' || UTL_TCP.CRLF || l_fix || UTL_TCP.CRLF || UTL_TCP.CRLF ||
            'Full Stack: ' || DBMS_UTILITY.FORMAT_ERROR_STACK || UTL_TCP.CRLF ||
            '-- ErrorHandler Bot';

        -- Send via APEX Mail
       l_message_id := apex_mail.send(
          p_to   => 'admin@applicationowner.com',
          p_from => 'test@cloudifyhub.com',
          p_body => l_email_body,
          p_subj =>  'APEX Error: ' || l_error_code || ' - AI Analysis Ready'
      );
        APEX_MAIL.PUSH_QUEUE;

        COMMIT; 

    EXCEPTION
        WHEN OTHERS THEN
            RAISE; 
    END handle_exception;

END error_handler_pkg;
/

Summary of the Package

Step 3: Plug It In – Exception Wrappers Everywhere

Let us use our PL/SQL Package in our application to stimulate our Error Manager Bot:

Our error bot manager will capture the error, provide suggesting on how to fix and send an email to admin.

-- This will raise ORA-01476: divisor is equal to zero
DECLARE
    x NUMBER := :P7_NUMBER_1;
    y NUMBER := :P7_NUMBER_2;
    z NUMBER;
BEGIN
    z := x / y; 

EXCEPTION
   WHEN OTHERS THEN
      ERROR_HANDLER_PKG.handle_exception('Divide by zero test');
      RAISE; 
END;

The form displayed is designed as a demo interface to intentionally trigger the Oracle error ORA-01476: divisor is equal to zero, so the Error Manager Bot can capture it and generate an AI-assisted diagnostic.

This form is a controlled error simulation tool - Test drive

Below is the content of the email received from our Error Manager Bot:

APEX Error Alert

Timestamp: 2025-11-21 08:35:24 +00:00
App ID/Page: 133/7
User/Session: RICHMOND/125038543263639
Error Code: -1476

AI EXPLANATION:


AI FIX SUGGESTION:
### Explanation:
The ORA-01476 error occurs when a SQL operation attempts to divide a number by zero, which is mathematically undefined and disallowed in SQL operations. This error typically arises in SQL queries, PL/SQL code, or inside Oracle APEX applications where division operations are performed without prior checks on the divisor.

### Fix:
To resolve the ORA-01476 error, you can use the following steps:

1. **Identify the division operation causing the error**:
   Locate the SQL query or the specific line of PL/SQL code which attempts the division. Look for any `/` operators or division functions.

2. **Modify the SQL/PL/SQL to check for zero before division**:
   Use a conditional case or decode statement to handle cases where the divisor might be zero. You can either prevent the division when the divisor is zero or substitute it with a valid number.

   For SQL:
   SELECT id,
          CASE
              WHEN divisor != 0 THEN dividend / divisor
              ELSE NULL  -- or another substitute value
          END AS result
   FROM your_table;


   For PL/SQL:
   DECLARE
       l_dividend NUMBER := 10;
       l_divisor NUMBER := 0;  -- example, potentially dynamic
       l_result NUMBER;
   BEGIN
       IF l_divisor != 0 THEN
           l_result := l_dividend / l_divisor;
       ELSE
           l_result := NULL;  -- or another substitute value
       END IF;
       DBMS_OUTPUT.PUT_LINE('Result: ' || TO_CHAR(l_result));
   EXCEPTION
       WHEN OTHERS THEN
           DBMS_OUTPUT.PUT_LINE('Error: ' || SQLERRM);
   END;


3. **Test the changes**:
   Rerun your queries or scripts to ensure the division by zero error is handled and doesn't occur again.

4. **Implement and roll out the fix**:
   After testing, implement the changes in your production environment to prevent future occurrences of ORA-01476.

### References:
- Oracle SQL Documentation regarding error handling can be found here:
  [Oracle Database Error Messages - 21c](https://docs.oracle.com/en/database/oracle/oracle-database/21/errmg/ORA-01476.html)
- For more on handling conditions in SQL and PL/SQL:
  [Conditional Compilation in PL/SQL](https://docs.oracle.com/database/121/LNPLS/conditional_compilation.htm#LNPLS99979)

These references and guidelines should help you effectively handle and prevent the "divide by zero" error in your Oracle database operations.

Full Stack: ORA-01476: divisor is equal to zero

-- ErrorHandler Bot

Summary

This article introduces a proof-of-concept AI-powered error-handling system for Oracle APEX using APEX_AI.CHAT. Instead of traditional reactive exception blocks, this solution proactively analyzes errors, explains the root cause in plain language, generates actionable fixes, and logs everything automatically.

A custom PL/SQL package (error_handler_pkg) captures Oracle errors, collects APEX session context, sends the error to the AI engine, parses the structured response, stores it in an error_log table, and emails a detailed diagnostic to the admin. A simple divide-by-zero form demonstrates the system in action with AI’s explanation, fix steps, and Oracle documentation references. The result is a smarter, autonomous, self-documenting error management workflow that transforms exceptions into clear, guided solutions in real time.

Happy APEXING in this AI World.

Hello, fellow developers and Oracle enthusiasts! If you're like me, you're always looking for ways to make your applications more interactive and user-friendly. Today, I'm diving into Oracle Application Express (APEX), one of the most powerful low-code platforms out there, and sharing a practical enhancement: adding a microphone button to the APEX chatbox for voice-to-text input. This feature leverages the browser's Speech Recognition API to let users dictate messages instead of typing them—perfect for accessibility, mobile users, or just speeding up interactions.

As someone who writes on Hashnode, I love exploring tools that bridge traditional database-driven apps with modern web features. In this comprehensive guide, we'll cover:

• A quick overview of Oracle APEX and its chat capabilities.

• Why adding voice input matters.

• Step-by-step implementation using JavaScript and CSS.

• Code explanations, potential customizations, and best practices.

• Testing and browser compatibility notes.

By the end, you'll have everything you need to integrate this into your APEX projects. Let's get started!

What is Oracle APEX?

Oracle Application Express (APEX) is a low-code development platform that allows you to build secure, scalable web applications directly on top of an Oracle Database. It's been around since 2004 (originally as HTML DB) and has evolved into a robust tool used by enterprises worldwide for everything from simple data entry forms to complex dashboards and AI-integrated apps.

Key features of APEX include:

• Rapid Development: Drag-and-drop interfaces, pre-built components, and declarative programming reduce coding time.

• Universal Theme: A responsive, customizable UI framework based on Oracle JET, ensuring apps look great on any device.

• Integration Capabilities: Seamless connections to Oracle Database, REST services, and external APIs.

• Security Built-In: Row-level security, authentication schemes, and encryption out of the box.

• Extensibility: While low-code, you can inject custom JavaScript, CSS, and plugins for advanced functionality.

As of August 2025, APEX is on version 24.1 (with 25.1 previews floating around), introducing enhancements like improved AI assistants, better mobile support, and refined components. One such component is the chat interface, often used in conversational apps, support bots, or internal messaging systems.

The Chatbox in Oracle APEX

APEX comes with a prebuilt "chatbox" as a native out-of-the-box Dynamic Action Show AI Assistant component, but you cannot easily modify it as you wish:

However, with the Universal Theme (UT), APEX provides CSS classes and patterns for chat-like UIs, such as .a-ChatInput-actions for input controls and .a-ChatInput-text for the message textarea. These are commonly used in sample apps or plugins like the "Conversational AI" demo in recent APEX versions, where chatbots powered by Oracle's AI services respond to user queries.

Our focus today is enhancing the input area with voice recognition, assuming you have a chat setup using UT classes.

Why Add a Microphone to the Chatbox?

In a world of Siri, Alexa, and Google Assistant, voice input is no longer a luxury—it's expected. Benefits include:

• Accessibility: Helps users with disabilities, like those with motor impairments.

• Efficiency: Faster for long messages or hands-free use (e.g., in warehouses or field services).

• User Experience: Makes your APEX app feel modern and intuitive.

• Browser-Native: Uses the Web Speech API, no external libraries needed.

Potential use cases in APEX:

• Customer support portals where agents dictate responses.

• Data entry apps for mobile field workers.

• AI chatbots for querying databases via voice.

Now, let's implement it!

Implementation: Adding the Microphone Button

We'll use JavaScript to dynamically inject a microphone button into the chat input actions div. It toggles speech recognition on click, transcribing speech to the textarea. CSS ensures it blends with APEX's Universal Theme.

Prerequisites

• An APEX page with a chat interface Show AI Assistant Dynamic Action.

• Browser support: Chrome, Edge, or Safari (Web Speech API availability).

• Add the code to your page's Function and Global Variable Declaration (for JS) and Inline CSS (for styles).

  

JavaScript Code

Here's the consolidated and optimized JS code. It handles dynamic loading (e.g., for dialogs), prevents duplicates, and supports continuous recognition.

function addMicButtonToChatbox() {
  const actionsDiv = document.querySelector(".a-ChatInput-actions");
  const textarea = document.querySelector(".a-ChatInput-text");

  if (!actionsDiv || !textarea) {
    // Retry until chatbox is rendered
    setTimeout(addMicButtonToChatbox, 300);
    return;
  }

  // Avoid duplicates
  if (actionsDiv.querySelector(".mic-btn")) return;

  // 🎤 Create mic button
  const micBtn = document.createElement("button");
  micBtn.className = "a-ChatInput-button mic-btn u-success"; // ✅ idle = success
  micBtn.title = "Record Voice";
  micBtn.setAttribute("aria-label", "Record Voice");

  const micIcon = document.createElement("span");
  micIcon.className = "a-Icon fa fa-microphone"; // default UT icon (mic)
  micBtn.appendChild(micIcon);

  // Insert before Send button
  const sendBtn = actionsDiv.querySelector(".a-ChatInput-button--send");
  if (sendBtn) {
    actionsDiv.insertBefore(micBtn, sendBtn);
  } else {
    actionsDiv.insertBefore(micBtn, actionsDiv.firstChild);
  }

  // 🎙 Speech Recognition setup
  const SpeechRecognition = window.SpeechRecognition || window.webkitSpeechRecognition;
  let recognition;
  let isRecording = false;

  if (SpeechRecognition) {
    recognition = new SpeechRecognition();
    recognition.continuous = true;  // 🔥 keep listening until stopped
    recognition.interimResults = false;
    recognition.lang = "en-US"; // Change to your preferred language

    recognition.onstart = () => {
      micIcon.className = "a-Icon fa fa-stop"; // switch to stop icon
      micBtn.classList.remove("u-success");
      micBtn.classList.add("u-danger"); // 🔴 recording = danger
      isRecording = true;
    };

    recognition.onend = () => {
      micIcon.className = "a-Icon fa fa-microphone"; // back to mic
      micBtn.classList.remove("u-danger");
      micBtn.classList.add("u-success"); // 🟢 idle
      isRecording = false;
    };

    recognition.onresult = (event) => {
      let transcript = "";
      for (let i = event.resultIndex; i < event.results.length; ++i) {
        if (event.results[i].isFinal) {
          transcript += event.results[i][0].transcript;
        }
      }
      if (transcript) {
        textarea.value += (textarea.value ? " " : "") + transcript.trim();
      }
    };

    micBtn.addEventListener("click", (e) => {
      e.preventDefault();
      if (!isRecording) {
        recognition.start();
      } else {
        recognition.stop();
      }
    });
  } else {
    micBtn.disabled = true;
    micIcon.className = "a-Icon fa fa-ban"; // 🚫 not supported
    console.warn("SpeechRecognition not supported in this browser.");
  }
}

// ✅ Run on page load
document.addEventListener("DOMContentLoaded", addMicButtonToChatbox);

// ✅ Run when APEX refreshes or dialog opens (for dynamic chatboxes)
apex.jQuery(document).on("apexafterrefresh", addMicButtonToChatbox);
apex.jQuery(document).on("dialogopen", function (event, ui) {
  if (ui && ui.dialog && ui.dialog.hasClass("a-ChatDialog")) {
    addMicButtonToChatbox();
  }
});

Code Breakdown

• Button Creation: Dynamically adds a button with a microphone icon (using Font Awesome from UT).

• Insertion: Places it before the send button for intuitive placement.

• Speech Recognition:

  • Uses window.SpeechRecognition (or webkit fallback).

  • continuous: true keeps listening until manually stopped.

  • Appends final transcripts to the textarea.

  • Toggles button state (color and icon) for visual feedback.

• Event Handling: Runs on DOM load, APEX refreshes, and dialog opens to handle dynamic UIs.

• Fallback: Disables the button if the API isn't supported.

CSS Code

Add this to style the button as a neat circle, matching APEX's button aesthetics.

.mic-btn {
  border-radius: 50%;
  width: 32px;
  height: 32px;
  padding: 0;
  display: flex;
  align-items: center;
  justify-content: center;
}

This makes the button compact and round, fitting nicely in the actions div.

How It Works in Action

1. Load your APEX page with the chatbox.

2. The script injects the mic button (green with mic icon) when you start typing.

   

3. Click it: Button turns red with a stop icon, and recognition starts.

Speak: Your words are transcribed and appended to the textarea.

• Click again to stop.

  

• Send the message as usual.

If the browser doesn't support it (e.g., Firefox), the button shows a ban icon and is disabled.

Customizations and Best Practices

• Language Support: Change recognition.lang to other codes like "es-ES" for Spanish.

• Interim Results: Set interimResults: true if you want live previews (but it might be noisy).

• Error Handling: Add recognition.onerror to alert users (e.g., "Microphone access denied").

• Permissions: Browsers prompt for mic access—handle denials gracefully.

• APEX Integration: Trigger a dynamic action on transcription to auto-send or process.

• Testing: Use Chrome DevTools to simulate. Test on mobile for real-world use.

• Security: Since this is client-side, ensure sensitive apps use HTTPS (required for Speech API).

• Accessibility: Add ARIA attributes and test with screen readers.

Potential issues:

• Accuracy varies by accent/noise.

• API limits: Some browsers cap session length.

Browser Compatibility

• Supported: Chrome (Android/iOS too), Edge, Safari.

• Not Supported: Firefox, Opera (as of 2025—check updates).

• Polyfills: Consider third-party services like Google Cloud Speech-to-Text for broader support, but that requires API keys and backend integration.

Conclusion

Adding a microphone to your Oracle APEX chatbox is a simple yet impactful way to modernize your apps. With just a bit of JS and CSS, you're tapping into powerful web APIs while staying within APEX's ecosystem. This enhancement not only boosts usability but also showcases how low-code platforms like APEX can be extended for cutting-edge features.

If you try this out, let me know in the comments—did it work seamlessly, or did you tweak it? For more APEX tips, follow me on Hashnode. Happy coding! #orclAPEX

As a freelancer diving into the world of web app development, I needed tools that could deliver fast, scalable solutions without bogging me down in endless setup or infrastructure management. My early projects demanded quick turnarounds, and clients expected robust, secure applications that could handle data efficiently. I explored various frameworks—JavaScript, traditional PHP setups, Python, and even Java—but they often felt overly complex or required significant server-side configuration. That’s when I stumbled upon Oracle Application Express (APEX) whiles reading a newsletter from Caspio, a low-code platform that changed the game for me. With its seamless cloud deployment, deep database integration, and intuitive UI design tools, APEX became my go-to for building data-driven web applications.

Traditional Development vs. Oracle APEX

Traditional web development frameworks, while powerful, come with steep learning curves and time sinks. For example:

• JavaScript Frameworks: These require extensive front-end coding, state management, and often separate backend APIs. Setting up authentication, security, and deployment pipelines can take weeks.

• PHP or Django: These are great for custom logic but demand manual configuration for hosting, database connections, and security protocols. Scaling often means wrestling with server infrastructure.

• Infrastructure Overhead: Most frameworks require managing servers, load balancers, and DevOps pipelines, which can be a nightmare for a solo developer or small team.

In contrast, Oracle APEX is a breath of fresh air:

• Built-in Security: APEX handles authentication, authorization, and session management out of the box. Features like single sign-on (SSO) and role-based access control are preconfigured.

• 

• Cloud Deployment: With Oracle Cloud, I can deploy apps in minutes, no server provisioning required. APEX runs directly on the Oracle Database, so scalability is inherent.

• 

• Low-Code UI: The drag-and-drop interface builder lets me create responsive, professional-grade UIs without writing extensive CSS or JavaScript.

• 

• Database Integration: Since APEX is tightly coupled with Oracle Database, CRUD operations, complex queries, and reporting are seamless—no need for middleware.

• 

This streamlined approach meant I could focus on solving client problems instead of wrestling with boilerplate code or infrastructure.

Features That Made Me Stay

Once I started using APEX, a few standout features hooked me:

• Websheet Applications: For non-technical clients, Websheets allow end-users to manage data via spreadsheet-like interfaces without coding. This was a game-changer for collaborative projects.

• RESTful Services: APEX’s built-in REST API support lets me integrate with external systems effortlessly. I can expose or consume data securely, making it ideal for modern, interconnected apps.

• 

• Calendar Integration: Need a scheduling app? APEX’s calendar components are pre-built and customizable, saving hours of front-end work.

• SQL and PL/SQL Power: As someone comfortable with SQL, I love how APEX leverages PL/SQL for business logic. I can write complex backend logic without juggling separate frameworks.

•   CREATE OR REPLACE TRIGGER "SALES_SYNC_T"
    BEFORE INSERT ON "SALES_SYNC"
    FOR EACH ROW
    DECLARE
       json_data CLOB DEFAULT :new.orderitems;
       l_order_id orders.order_id%TYPE DEFAULT NULL;
    BEGIN
       INSERT INTO orders(ORDER_DATETIME, CUSTOMER_ID, ORDER_STATUS, STORE_ID)
       VALUES(:new.ORDERDATETIME, :new.CUSTOMERID, :new.ORDERSTATUS, :new.STOREID)
       RETURNING order_id INTO l_order_id;
       FOR rec IN (
          SELECT jt.lineitemid, jt.productid, jt.unitprice, jt.quantity
          FROM JSON_TABLE(
             json_data, '$[*]'
             COLUMNS (
                lineitemid NUMBER PATH '$.lineitemid',
                productid NUMBER PATH '$.productid',
                unitprice NUMBER PATH '$.unitprice',
                quantity NUMBER PATH '$.quantity'
             )
          ) jt
       )
       LOOP
          INSERT INTO order_items(ORDER_ID, LINE_ITEM_ID, PRODUCT_ID, UNIT_PRICE, QUANTITY)
          VALUES(l_order_id, rec.lineitemid, rec.productid, rec.unitprice, rec.quantity);
       END LOOP;
    END;
  

• No Front-End Headache: The platform’s declarative UI tools, like Interactive Reports and Forms, handle most front-end rendering. I can customize layouts without diving into JavaScript frameworks or CSS frameworks like Bootstrap.

• 

These features meant I could build feature-rich apps without the usual development sprawl, keeping my projects lean and manageable.

Impact on My Projects

The real proof of APEX’s value came in my project outcomes. Take Cloudify Dental & Eye Care, a cloud-based management system for a chain of clinics:

• 

• Speed: Using APEX, I delivered a fully functional app with patient records, appointment scheduling, and reporting in just three weeks—a timeline that would’ve taken months with React or Django.

• Cost Savings: By leveraging APEX’s built-in tools and Oracle Cloud hosting, I cut development costs by 60% compared to traditional stacks, while delivering comparable functionality.

• Scalability: The app seamlessly handled thousands of patient records and concurrent users, thanks to Oracle Database’s robust backend.

• Client Satisfaction: The intuitive UI and rapid delivery wowed the client, leading to repeat business and referrals.

Across other projects, from inventory systems to dashboards, APEX consistently reduced development time and complexity while maintaining high quality.

Conclusion

If you’re a developer building data-driven web applications and need fast, reliable results, Oracle APEX is a no-brainer. Its low-code environment, tight database integration, and cloud-native deployment make it a powerhouse for rapid development without sacrificing scalability or security. Whether you’re a freelancer like me or part of a larger team, APEX can transform your workflow and deliver results that impress clients.

Stay tuned for my next post: “10 Hidden Gems in Oracle APEX Every Developer Should Know,” where I’ll dive into lesser-known features that can supercharge your productivity!

🔧 Prerequisites

Before diving into code, make sure the following are set up:

1. Oracle APEX Environment (Cloud or On-Premise)

2. AI Services Plugin enabled and configured (apex_ai package)

3. APEX Mail Setup:

   • SMTP settings correctly configured under Manage Instance > Mail Server

   • Valid sender address (p_from)

4. Workspace Name (You’ll use this to get the security_group_id)

🧠 Use Case

We want to automate the generation of monthly economic insight reports (e.g., for May 2025) based on Bank of Ghana's data using APEX AI Chat and send it to our stakeholders via email.

Setting Up APEX AI Services Plugin (apex_ai)

Before using the apex_ai.chat function, you need to ensure that Oracle APEX AI Services is correctly configured in your environment. Follow these steps:

1. Enable AI Services in Your APEX Instance

• Navigate to App Builder > Workspace Utilities > Generative AI.

• Click "Create" to register a new service.

• Choose the appropriate AI Provider (Oracle Cloud or OpenAI) based on your setup.

• Provide your API Key or Oracle AI settings (endpoint, credentials, etc.).

• Assign a Static ID (e.g., financial_assistant) — this ID will be used in your PL/SQL.

• 

Configure SMTP Settings (Admin Task) . Click the link to read about how to set up email delivery in OCI

🪄 The Full PL/SQL Block

create or replace procedure send_financial_summary_email
as
    l_security_group_id number;
    l_messages          apex_ai.t_chat_messages;
    l_response1         clob;
    l_body              clob;
    l_id                number;

    r_month varchar2(20) := to_char(add_months(sysdate, -1), 'MON');
    r_year  varchar2(4)  := to_char(sysdate, 'YYYY');
begin
    -- Set the security group context for APEX workspace
    apex_util.set_security_group_id(apex_util.find_security_group_id(p_workspace => 'WKSP_TESTING'));

    -- AI Chat request to generate financial summary
    l_response1 := apex_ai.chat(
        p_prompt            => 'As a financial and investment analyst, analyze Bank of Ghana economic data and summarize the latest key indicators for Ghana for ' || r_month || ', ' || r_year || '.',
        p_system_prompt     => 'You are a financial analyst reporting economic insights from the Bank of Ghana for publication.',
        p_service_static_id => 'error_assistant',
        p_messages          => l_messages
    );

    -- Compose email body
    l_body := 'Dear User,' || utl_tcp.crlf || utl_tcp.crlf;
    l_body := l_body || 'Here is the analysis of the Bank of Ghana economic data for ' || r_month || ', ' || r_year || ':' || utl_tcp.crlf || utl_tcp.crlf;
    l_body := l_body || l_response1 || utl_tcp.crlf || utl_tcp.crlf;
    l_body := l_body || 'Sincerely,' || utl_tcp.crlf;
    l_body := l_body || 'The Finance Insight Dev Team' || utl_tcp.crlf;

    -- Send the email
    l_id := apex_mail.send(
        p_to   => 'investoremail@outlook.com',
        p_from => 'test@cloudifyhub.com',
        p_body => l_body,
        p_subj => 'Economic Insight: Ghana | ' || r_month || ' ' || r_year || ''
    );

    apex_mail.push_queue;
    commit;

    -- Show in DBMS output (for debug/log)
    dbms_output.put_line('Email Sent. AI Response:');
    dbms_output.put_line(l_response1);
end;
/

🗓️ Automate It with a Scheduler

To make this a daily/monthly automation, use DBMS_SCHEDULER OR APEX AUTOMATIONS to run the PL/SQL block at intervals.

BEGIN
  -- Create the job
  DBMS_SCHEDULER.create_job (
    job_name        => 'send_economic_insight_email',
    job_type        => 'PLSQL_BLOCK',
    job_action      => 'BEGIN send_financial_summary_email(); END;',
    start_date      => SYSTIMESTAMP,
    repeat_interval => 'FREQ=MONTHLY;BYMONTHDAY=1;BYHOUR=8',
    enabled         => TRUE,
    comments        => 'Monthly Economic Insight Email Job'
  );

  -- Run the job immediately once
  DBMS_SCHEDULER.run_job (
    job_name => 'send_economic_insight_email',
    use_current_session => FALSE -- Set to TRUE if you want it to run in the current session
  );

  DBMS_OUTPUT.PUT_LINE('Job "send_economic_insight_email" created and submitted for immediate execution.');
END;
/

or you can create your customize page and pass some parameters.(Depends on you my Oracle APEX Buddy)

Output

✅ Benefits

• 🔁 Hands-Free Reporting — Once set, it runs on autopilot. Agentic report

• 🤖 AI-Powered Insight — Leverages LLM capabilities.

• 📈 Professional Presentation — Clean email format ready to share.

• 📅 Customizable Schedule — Daily, weekly, or monthly.

Caution

AI can hallucinate

💬 Final Thoughts

This approach showcases the powerful synergy between Oracle APEX, AI Services, and automation tools to deliver high-value insights in real-time. Whether for finance, healthcare, or logistics, this pattern can be adapted to fit any domain where timely, intelligent communication matters.

How to configure reverse proxy for Oracle APEX URL using nginx - Detailed blog

Configuration of custom HTTP Logging

Step 1: Define a Custom Log Format

1. Edit the Main NGINX Configuration File: Open the NGINX configuration file for editing:

    sudo nano /etc/nginx/yourdomain.conf
   

2. Add a Custom Log Format: In the http block, define a custom log format:

    http {
        log_format custom_log_format '$remote_addr - $remote_user [$time_local] "$request" '
                                      '$status $body_bytes_sent "$http_referer" "$http_user_agent"';
        access_log /var/log/nginx/http_requests.log custom_log_format;
    }
   

   • $remote_addr: IP address of the client.

   • $remote_user: Authenticated user (if any).

   • $time_local: Local time of the request.

   • $request: The requested resource and HTTP method.

   • $status: HTTP status code of the response.

   • $body_bytes_sent: Size of the response body.

   • $http_referer: The referring URL (if any).

   • $http_user_agent: The user agent string of the client.

Step 2: Configure Access Logs for a Specific Server Block

1. Navigate to Your Server Block Configuration: Edit the server block file for your domain:

    sudo nano /etc/nginx/yourdomain.conf
   

2. Specify the Access Log Location: Add the following line inside the server block:

    server {
        access_log /var/log/nginx/http_requests.log custom_log_format;
        ...
    }
   

3. Save and Exit the File: Save the changes and exit the editor.

Step 3: Test and Reload NGINX

1. Test the Configuration: Verify that the syntax is correct:

    sudo nginx -t
   

2. Reload NGINX: Apply the configuration changes:

    sudo systemctl reload nginx
   

Step 4: Monitor HTTP Logs

1. View Logs in Real-Time: Use the tail command to monitor HTTP requests as they are logged:

    sudo tail -f /var/log/nginx/http_requests.log
   

2. Example Log Entry:

    192.168.1.100 - - [01/Jan/2025:10:00:00 +0000] "GET /ords/r/myapp/ HTTP/1.1" 200 1234 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/90.0.4430.85 Safari/537.36"
   

   This log entry includes the client's IP address, request details, response status, and user agent.

Step 5: Additional Tips

• Rotate Logs: To prevent the log file from growing too large, set up log rotation using a tool like logrotate.

• Secure Log Files: Restrict access to log files to protect sensitive information.

    sudo chmod 640 /var/log/nginx/http_requests.log
    sudo chown root:adm /var/log/nginx/http_requests.log
  

Conclusion

With HTTP logging configured in NGINX, you can track every request made to your server. This setup is essential for debugging, security analysis, and performance monitoring. Remember to regularly review your logs and ensure they are securely stored.

Contact for your custom installation Richmond - richmond@cloudifyhub.com

In a world where healthcare technology is evolving rapidly, Cloudify Digital Solutions has emerged as a trailblazer by building a specialized SaaS platform for the eye and dental care sectors. Leveraging the power of Oracle APEX (Application Express) as its development framework, Cloudify Digital Solutions reached an impressive GH60k in Annual Recurring Revenue (ARR). Here’s how the company harnessed this powerful technology to disrupt the healthcare management space.

Identifying the Market Gap

The journey of Cloudify Digital Solutions began with recognizing a critical need: healthcare management tools designed specifically for niche markets like eye care and dental practices. Traditional healthcare software often lacked the specific functionalities that specialists in these fields required. Cloudify Digital Solutions saw this gap and developed focused solutions that directly addressed the pain points of these industries.

By using Oracle APEX, a low-code platform, Cloudify was able to rapidly develop and deploy Cloudify EyeCare and Cloudify Dental Care—two comprehensive SaaS platforms that streamlined daily operations, improved patient management, and automated administrative tasks.

Why Oracle APEX?

Oracle APEX provided Cloudify Digital Solutions with a versatile and scalable framework, allowing the development team to build powerful, secure applications in a fraction of the time required by traditional coding approaches. Oracle APEX enabled the following key advantages:

• Speed of Development: With its low-code environment, Cloudify was able to iterate quickly, continuously improving and adding new features to the platform based on customer feedback.

• Seamless Integration: Oracle APEX’s ability to integrate smoothly with other Oracle services and third-party applications was essential in building a robust SaaS platform capable of handling complex workflows in eye and dental care.

• Cloud-Based Architecture: APEX allowed Cloudify to host the entire solution in the Oracle Cloud, ensuring security, scalability, and ease of maintenance for its customers.

This development framework was a major factor in Cloudify’s ability to deliver sophisticated solutions to its clients while maintaining cost efficiency, helping them keep the pricing attractive for dental and eye care providers.

Building Tailored Solutions for Eye and Dental Care

Cloudify Digital Solutions recognized that success in the healthcare SaaS space comes down to offering a product that meets the specific needs of the market. With Oracle APEX as the backbone, Cloudify developed features that targeted the unique requirements of each sector.

Cloudify EyeCare

The platform was designed with features such as appointment scheduling, inventory management for optical products, and seamless integration with Electronic Health Records (EHR). Oracle APEX's rich component library allowed for a user-friendly interface, making it easy for clinics to onboard the system and start reaping its benefits immediately.

Cloudify Dental Care

Similarly, Cloudify Dental Care utilized Oracle APEX’s flexibility to build tools for dental practice management, including digital patient records, treatment planning, and insurance claim processing. The scalable nature of APEX meant that the software could grow alongside the dental practices, ensuring long-term client retention.

Leveraging Cloud and Oracle APEX for Maximum Flexibility

By leveraging Oracle APEX's cloud capabilities, Cloudify Digital Solutions offered a fully cloud-based SaaS platform that eliminated the need for clinics to invest in expensive on-premise hardware. The system ensured secure access to data anytime, anywhere, with minimal operational overhead. This approach allowed Cloudify to offer continuous improvements and updates without disrupting client workflows—an essential factor in driving user adoption and reducing churn.

Additionally, the Oracle Cloud infrastructure provided top-tier security and data compliance, which is critical in the healthcare industry. By building on this trusted platform, Cloudify was able to assure its customers that their sensitive patient data was secure and compliant with industry regulations.

Customer-Centric Approach Enabled by Oracle APEX

Cloudify Digital Solutions’ success was built on a customer-first approach. Oracle APEX made it possible for Cloudify to quickly deploy updates and new features based on real-time feedback from its clients. The platform’s low-code capabilities allowed for rapid iteration, making Cloudify highly responsive to the changing needs of its users.

With features like customizable dashboards, real-time reporting, and AI-driven insights, Cloudify helped clinics become more efficient in managing their operations, which in turn drove greater satisfaction among clients.

Strategic Marketing and Community Engagement

While Oracle APEX helped in building a powerful product, Cloudify Digital Solutions also focused on effective marketing and strategic partnerships to drive growth. By positioning its software as a specialized solution for eye care and dental practices, Cloudify attracted customers who were frustrated with generic healthcare management software that didn’t meet their unique needs.

Furthermore, by partnering with industry associations and participating in healthcare conferences, Cloudify built a strong presence in the market. These efforts, combined with targeted digital marketing campaigns, contributed significantly to the company’s revenue growth.

Continuous Innovation Powered by Oracle APEX

One of the reasons Cloudify Digital Solutions was able to hit GH60k ARR is their focus on continuous innovation. With Oracle APEX’s rapid application development capabilities, the team could quickly incorporate emerging technologies such as artificial intelligence and advanced analytics into their platform.

For example, Cloudify introduced AI-powered features like predictive patient reminders and smart scheduling tools that helped clinics optimize their time and reduce no-show rates. These innovations kept the software ahead of competitors and helped retain a loyal customer base.

Conclusion

Cloudify Digital Solutions’ rise to GH60k ARR in the eye and dental care industry illustrates the power of combining niche-focused solutions with a cutting-edge development framework like Oracle APEX. The platform’s low-code environment, cloud capabilities, and seamless integration options allowed Cloudify to deliver high-quality software tailored to its clients’ needs.

By staying true to its customer-first philosophy and continuously innovating, Cloudify Digital Solutions has carved out a strong position in the healthcare SaaS market. As they look ahead, their commitment to leveraging Oracle APEX for rapid, scalable development will continue to drive their growth and success in the industry.

Managing a chapel or church involves various tasks, from tracking membership information to organizing events and managing finances. To streamline these operations, creating a custom Chapel/Church Management Software can be incredibly beneficial. In this blog, we'll explore how to develop such software using Oracle APEX in less than three weeks.

Week 1: Planning and Preparation

Day 1-2: Define the Scope and Requirements

Begin by defining the scope of your Chapel/Church Management Software. Determine what features are essential, such as member management, event scheduling, donation tracking, and communication tools. Collect requirements by meeting with chapel leaders and stakeholders to understand their specific needs.

Day 3-4: Set Up the Development Environment

If you haven't already, install Oracle APEX and Oracle Database in your development environment. Ensure that you have the necessary tools and resources, such as OCI account/APEX Workspace, version control system, and testing environment, ready for use.

Day 5-7: Database Design

Design the database schema for your software. Create tables for members, events, donations, and any other necessary data entities. Establish relationships between these tables, define primary and foreign keys, and set data types and constraints.

Week 2: Development

Day 8-10: Build User Interface

Use Oracle APEX's user-friendly interface builder to create the application's front end. Design a dashboard that provides quick access to key features. Build forms for data entry, tables for data display, and implement navigation menus for easy user interaction.

Day 11-13: Implement Business Logic

Write the backend logic to handle various functionalities of your Chapel/Church Management Software. This includes member registration, event scheduling, donation processing, and communication features. Pay special attention to data validation and error handling.

Day 14-15: Testing and Debugging

Perform comprehensive testing to identify and fix any bugs or issues. Test the software's functionality, security features, and usability. Involve members of the chapel or church in user testing to gather feedback.

Week 3: Deployment and Final Touches

Day 16-17: Integration with Oracle Database

Integrate your Oracle APEX application with the Oracle Database. Ensure data synchronization, security, and access control are properly configured. Conduct data migration if necessary.

Day 18-19: User Training and Documentation

Prepare user manuals and documentation to help administrators and users understand how to use the software effectively. Conduct training sessions to ensure everyone is comfortable with the new system.

Day 20-21: Deployment and Launch

Deploy your Chapel/Church Management Software to a production environment. Monitor the application's performance and security closely during the initial rollout. Be prepared to address any issues that may arise.

Post-Launch Activities

After launching your Chapel/Church Management Software, your work is not over. You'll need to:

• Provide Ongoing Support: Address user inquiries, troubleshoot issues, and continuously improve the software based on user feedback.

• Regularly Update the Software: Keep the software up-to-date by implementing new features and security patches as needed.

• Scale and Customize: As your chapel or church grows, you may need to customize the software to accommodate new requirements and scalability.

• Ensure Data Security: Regularly back up your database and implement security measures to protect sensitive information.

Developing a Chapel/Church Management Software in less than three weeks with Oracle APEX is challenging, but with careful planning, efficient development, and by prioritizing essential features, it's possible to create a functional system that can greatly benefit your chapel or church community. Remember that this timeline may require additional resources and a focus on delivering a minimum viable product initially, with enhancements in subsequent iterations.

In today's fast-paced digital world, businesses and developers rely heavily on efficient data management and collaborative development tools. Oracle Application Express (APEX) and GitHub are two powerful platforms that play crucial roles in streamlining application development and version control. By combining the capabilities of Oracle APEX with the robustness of GitHub, developers can unlock a myriad of benefits, and the integration of DBMS_CLOUD REPO serves as the glue that binds these platforms together, enhancing the development process further. In this blog, we'll explore the advantages of using DBMS_CLOUD REPO in Oracle APEX and GitHub, and how this collaboration can accelerate development and collaboration.

1. Seamless Data Sharing and Management: DBMS_CLOUD REPO is an Oracle Database package that facilitates seamless integration with cloud storage services like Oracle Cloud Infrastructure (OCI) Object Storage. With this integration, developers can easily access and share data files directly from their Oracle APEX applications. This feature ensures a smooth data sharing experience, allowing teams to work with consistent and up-to-date data sets, fostering data integrity and reducing potential errors.

2. Data Security and Compliance: Utilizing DBMS_CLOUD REPO within Oracle APEX and GitHub enables developers to maintain a centralized repository for their data files in a secure and controlled environment. Oracle's advanced security measures combined with GitHub's version control capabilities ensure that sensitive data remains protected, making it easier to comply with data governance regulations and adhere to industry best practices.

3. Efficient Version Control with Git: GitHub's popularity lies in its powerful version control system powered by Git. When integrated with Oracle APEX, developers can effortlessly manage changes to their applications, database objects, and data files. This version control ensures that every modification is tracked, making it easy to revert to previous states if needed. Additionally, collaboration becomes more manageable, as multiple developers can work simultaneously on different branches and merge their changes seamlessly.

4. Improved Collaboration and Teamwork: Both Oracle APEX and GitHub promote collaborative development environments. DBMS_CLOUD REPO further enhances this collaboration by providing a single source of truth for data files used within the application. Team members can easily access shared data and work with the latest files, promoting teamwork, and reducing data silos. Moreover, GitHub's pull request feature allows for code review, ensuring that only high-quality changes are merged into the main repository.

5. Enhanced Continuous Integration and Continuous Deployment (CI/CD): The combination of Oracle APEX, GitHub, and DBMS_CLOUD REPO facilitates a robust CI/CD workflow. As developers commit their changes to GitHub, automated testing and deployment processes can be triggered, pushing the updates to the APEX application. This streamlined CI/CD pipeline ensures faster release cycles and reduces the risk of errors during the deployment process.

6. Scalability and Flexibility: DBMS_CLOUD REPO allows developers to store and manage data files in the cloud, which offers virtually unlimited scalability. This scalability, combined with GitHub's flexibility in accommodating various types of projects, ensures that teams can efficiently handle projects of any size and complexity.

Demo of Sample Use Case Only

Link: https://files.fm/u/qd7uaqyhf#/view/3qksfbrp6

Conclusion:

The integration of DBMS_CLOUD REPO in Oracle APEX and GitHub represents a compelling alliance that empowers developers with advanced data management capabilities, seamless collaboration, and robust version control. The combination of these technologies streamlines the development process, enhances data integrity, and enables teams to work efficiently, ultimately leading to the delivery of high-quality applications. As businesses continue to embrace digital transformation, embracing this powerful combination can provide a competitive advantage and foster innovation in the development landscape. So, if you're looking to supercharge your application development process, consider leveraging the power of DBMS_CLOUD REPO in Oracle APEX and GitHub today.

#orclapex #oraclecloud

1. What is Uptime Robot? Uptime Robot is a cloud-based monitoring service that checks the availability of your websites and web services at regular intervals. It sends alerts when downtime or performance issues are detected, allowing you to take immediate action. Uptime Robot offers a user-friendly interface and supports various monitoring methods, including HTTP, HTTPS, TCP, and more.

2. Setting up Uptime Robot for Oracle APEX Applications: To begin monitoring your Oracle APEX applications with Uptime Robot, follow these steps:

Step 1: Sign up for Uptime Robot: Visit the Uptime Robot website (https://uptimerobot.com/) and create a new account if you haven't already. Uptime Robot offers a free plan that allows monitoring of up to 50 monitors.

Step 2: Add a new monitor: Once logged in, click on the "Add New Monitor" button and choose the appropriate monitor type. For Oracle APEX applications, select the "HTTP(s)" monitor type.

Step 3: Configure monitor settings: Enter the URL of your Oracle APEX application in the "Friendly Name" field and provide the application's URL in the "URL" field. Specify the monitoring interval according to your needs. Additionally, you can set up more advanced settings like custom HTTP headers or response content checks if required.

Step 4: Set up alert contacts: Uptime Robot allows you to receive notifications via email, SMS, or other communication channels when downtime occurs. Configure the alert contacts to ensure you receive timely alerts in case of any issues with your Oracle APEX applications.

Step 5: Save and activate the monitor: After reviewing the settings, click on the "Create Monitor" button to save and activate the monitor. Uptime Robot will start monitoring your Oracle APEX application based on the specified settings.

Benefits of using UpTime Robot

1. Monitoring and Managing Alerts: Uptime Robot continuously monitors the availability of your Oracle APEX application. When downtime or performance issues are detected, it will send alerts to the configured contacts. Here are a few tips for effectively managing alerts:

   

2. Customize alert settings: Uptime Robot provides options to customize the frequency and conditions for sending alerts. You can adjust these settings to avoid unnecessary alerts and ensure you receive alerts only for critical issues.

3. Configure escalation levels: In case of extended downtime, Uptime Robot allows you to configure escalation levels. For example, you can set up alerts to be sent to additional team members or escalate the issue to a higher priority if it persists for a certain duration.

4. Use maintenance windows: When performing planned maintenance or updates on your Oracle APEX applications, it's advisable to set up maintenance windows in Uptime Robot. This prevents unnecessary alerts during those periods.

5. Analyzing Reports and Performance: Uptime Robot provides detailed reports and performance metrics to help you analyze the uptime and performance of your Oracle APEX applications over time. By reviewing these reports, you can identify trends, spot recurring issues, and take proactive measures to improve overall performance.

6. Integrating Uptime Robot with Other Tools: Uptime Robot offers integrations with various third-party tools and services. Consider integrating it with your preferred incident management, collaboration, or monitoring tools to streamline your workflow and enhance the monitoring process. For example:

Best Practices for Monitoring Oracle APEX Applications

To make the most out of Uptime Robot and ensure effective monitoring of your Oracle APEX applications, consider the following best practices:

• Set up multiple monitors: Create separate monitors for different components or critical functionalities of your Oracle APEX application. This allows you to pinpoint specific issues and prioritize troubleshooting efforts.

• Monitor from multiple locations: Uptime Robot offers monitoring from various geographical locations. Configure monitors to check your Oracle APEX application's availability from multiple locations to ensure a comprehensive view of its accessibility worldwide.

• Regularly review reports: Take the time to review Uptime Robot's reports and performance metrics regularly. Look for patterns, trends, and recurring issues to identify areas for improvement and proactively address potential problems.

• Perform load testing: Conduct load testing on your Oracle APEX applications to simulate heavy user traffic and monitor how they handle the increased load. Uptime Robot can help you monitor the performance during load testing and identify any scalability or performance issues.

Conclusion: Using Uptime Robot to monitor your Oracle APEX applications provides valuable insights into their availability and performance. By setting up monitors, configuring alert notifications, and integrating with other tools, you can ensure timely detection of downtime and quickly address any issues that arise. Monitoring your applications with Uptime Robot empowers you to deliver a seamless user experience and maintain the highest levels of uptime for your Oracle APEX applications.

Building a Data Warehouse using Oracle APEX

Oracle APEX provides various tools for building data warehouses. Some of the key features of APEX that can be used for building data warehouses include:

1. Data Upload: APEX allows users to upload data in a variety of formats, including CSV, Excel, and XML. This feature can be used to upload data from various sources into the data warehouse.

2. Data Modeling: APEX provides a powerful data modeling tool that can be used to create data models for the data warehouse. This tool allows users to define entities, attributes, and relationships between data elements.

3. Data Transformation: APEX provides a powerful SQL engine that can be used to transform data into a format that is suitable for analysis. This engine can be used to perform various transformations, such as filtering, sorting, and aggregation.

4. Reporting: APEX provides a powerful reporting tool that can be used to create reports based on the data in the data warehouse. This tool allows users to create charts, tables, and other visualizations based on the data.

Performing ETL using Oracle APEX

ETL is a critical process in building a data warehouse. Oracle APEX provides various tools that can be used for performing ETL operations. Some of the key features of APEX that can be used for ETL include:

1. Data Extraction: APEX provides a powerful data extraction tool that can be used to extract data from various sources. This tool allows users to extract data from databases, flat files, and other sources.

2. Data Transformation: APEX provides a powerful SQL engine that can be used to transform data into a format that is suitable for analysis. This engine can be used to perform various transformations, such as filtering, sorting, and aggregation.

3. Data Loading: APEX provides a powerful data-loading tool that can be used to load data into the data warehouse. This tool allows users to load data from various sources into the data warehouse.

4. Data Validation: APEX provides a powerful data validation tool that can be used to validate the data that is loaded into the data warehouse. This tool allows users to perform various data quality checks, such as checking for missing data and duplicate records.

Creating Data Dimension in Oracle APEX

1. Define the dimension attributes: Identify the dimensions you want to use and the attributes that define them.

2. Create a dimension table: Create a table in Oracle APEX to store the dimension attributes.

3. Populate the dimension table: Insert data into the dimension table.

4. Create the dimension hierarchy: Create a hierarchical structure that defines the relationships between the dimension attributes.

5. Create the dimension view: Create a view that presents the dimension data in a user-friendly way.

6. Link the dimension to fact tables: Connect the dimension table to the fact table(s) using foreign keys.

7. Test the dimension: Verify that the dimension works as intended by querying it and checking for errors.

   Overall, creating a data warehouse dimension in Oracle APEX involves defining the dimension attributes, creating a dimension table, populating the table, creating the dimension hierarchy and view, and linking the dimension to fact tables.

Real demo using sample data from Kaggle

About Dataset

Datasets provide model-specific fuel consumption ratings and estimated carbon dioxide emissions for new light-duty vehicles for retail sale in Canada.

To help you compare vehicles from different model years, the fuel consumption ratings for 2000 to 2022 vehicles have been adjusted to reflect the improved testing that is more representative of everyday driving. Note that these are approximate values that were generated from the original ratings, not from vehicle testing.

Link to dataset --> https://www.kaggle.com/datasets/ahmettyilmazz/fuel-consumption

1. Uploading Data to Oracle APEX

   

2. Creating Data-Dimensional Table

   Vehicle Make Dimension, Vehicle Model Dimension, Vehicle Class Dimension, Date Dimension, Vehicle Fact

   Empty Vehicle Dimension Table

   

Empty Vehicle Fact Table

Load Data to Vehicle Fact to populate dimensions using custom packages

Dimensions

Output of loaded data to vehicle facts and dimensional tables

Link to demo --> https://eywik85fpyrijct-nonproduction.adb.uk-london-1.oraclecloudapps.com/ords/r/vehicle_whouse/vehicle-fact/dashboard?session=104749173648052

In conclusion, Oracle APEX provides a low-code platform for developing data warehouses that can be used to store and analyze large amounts of data. To implement a data warehouse in Oracle APEX, you can create dimension and fact tables, populate them with data, and create views and reports to analyze the data. Oracle APEX also provides tools for data transformation and ETL (extract, transform, load) processes to move data from source systems to the data warehouse. With its user-friendly interface and powerful data analysis features, Oracle APEX can be a useful tool for implementing a data warehouse solution. However, it is important to note that data warehousing can be a complex process that requires careful planning and design to ensure optimal performance and usability.

For your custom data warehouse implementation, you can reach us on

Contact: +233546640723

Website: https://cloudifyhub.com , https://analyticalstack.com

Twitter: https://twitter.com/AnalyticalStack

LinkedIn: https://www.linkedin.com/in/richmond-asamoah-90a451113/

Oracle Application Express (Oracle APEX) is a web-based, low-code development platform for creating web and mobile applications. It is a fully-supported, no-cost feature of the Oracle Database and is included with all editions of the Oracle Database, including Oracle Cloud.

One of the key features of Oracle APEX is its ability to create web applications quickly and easily. It allows developers to create applications with minimal coding, using a drag-and-drop interface and pre-built templates. This makes it accessible to developers with a wide range of skills, and allows for faster development times compared to traditional coding methods.

Oracle APEX also provides a wide range of features for creating interactive and responsive web applications, including charts, interactive reports, and forms. It also includes support for building mobile applications, including a mobile interface, and the ability to create offline-capable applications.

Oracle APEX can be integrated with other Oracle products, such as the Oracle Database, Oracle Business Intelligence, and Oracle E-Business Suite. This allows developers to create applications that can easily access and manipulate data stored in these systems.

Oracle APEX is also highly customizable, allowing developers to create unique, custom applications that meet the specific needs of their organization or industry. The platform is flexible and can be used to create a wide range of applications, including CRM systems, project management systems, inventory management systems, human resource management systems, and financial management systems.

Software as a Service

Software as a Service (SaaS) is a software delivery model where a software application is hosted by a third-party provider and made available to customers over the internet. Instead of purchasing and installing software on individual computers or servers, customers can access the software through a web browser. SaaS is also known as "on-demand software" or "web-based software".

One of the main benefits of SaaS is the ability for customers to access the software from anywhere with an internet connection. This eliminates the need for expensive on-premises infrastructure and allows for greater flexibility and scalability. SaaS also allows for a subscription-based pricing model, where customers pay a monthly or annual fee to access the software, instead of a large upfront cost.

SaaS is also known for its automatic upgrades and updates, which are handled by the provider. This eliminates the need for customers to manually update the software and ensures that they always have the latest version. The provider also takes care of maintenance, security, and backups, which reduces the overall cost and complexity for the customer.

SaaS is widely used across various industries, from small businesses to large enterprises. Some examples of SaaS applications include customer relationship management (CRM), project management, human resources, finance, email marketing, and e-commerce.

SaaS has revolutionized the way software is delivered and consumed, making it more accessible, affordable, and efficient for businesses and organizations of all sizes. It has also allowed for the emergence of new business models and the creation of new software companies, which has led to increased innovation and competition in the software industry.

Practical SaaS application for Oracle APEX

Here are five powerful SaaS applications that can be developed with Oracle APEX:

1. CRM (Customer Relationship Management) systems: Oracle APEX can be used to create a CRM system that can be used to manage customer information, track leads, and manage sales and marketing activities.

2. Project management systems: Oracle APEX can be used to create a project management system that can be used to track tasks, assignments, and project progress.

3. Inventory management systems: Oracle APEX can be used to create an inventory management system that can be used to track stock levels, reorder points, and supplier information.

4. Human resource management systems: Oracle APEX can be used to create a human resource management system that can be used to track employee information, manage payroll and benefits, and handle other HR-related tasks.

5. Financial management systems: Oracle APEX can be used to create a financial management system that can be used to track expenses, manage accounts payable and receivable, and generate financial reports.

It's worth noting that these are just a few examples of the types of applications that can be developed with Oracle APEX, the platform is very flexible and can be used to develop a wide range of applications.

Sample SaaS applications available on the market.

1. Cloudify Eye Care - Cloudify Care provides complete management solutions for Eye care centers around the globe. It digitizes the medical records of patients with the ability of sending automated alerts, invoicing and keeping records. This Eye management software is tailor made considering the feedbacks and suggestions of leading Doctors, healthcare professionsals, clinics and nurses.

   Developed by Cloudify Digital Solutions in Ghana