Introduction Anyone who has built a recruitment or HR application knows the pain: candidates send resumes as PDFs, and someone has to re-type the name, phone, email, address and education into a form. It is slow and error-prone. In this post I will show how to automate it in Oracle APEX using a Gemini multimodal model. The user uploads a PDF, clicks Parse , and a single PL/SQL process sends the PDF to the AI, receives structured JSON, and populates the page items. No external middleware, no OCR library — just APEX and PL/SQL. What We Are Building The flow is simple: The user uploads a resume PDF using a File Browse item ( P2_RESUME ). On clicking Parse , a PL/SQL process reads the file from APEX temp files. The PDF is Base64-encoded and sent to the Gemini API together with an instruction prompt. Gemini returns a JSON object with the extracted fields. The JSON is parsed and the values are placed in...
Restrict Search Input to Alphanumeric Characters in Oracle APEX Interactive Grid and Interactive Report
Introduction The search box in an Interactive Grid (IG) or Interactive Report (IR) accepts any character by default. In some applications, business rules require end users to enter only letters ( a-z , A-Z ) and numbers ( 0-9 ) when using the All Text Columns search option. Special characters such as @ , # , % or ' should not be allowed. Oracle APEX does not provide a declarative setting — such as an input mask or pattern — for the built-in search field. In this post, we implement the restriction with a small, reusable JavaScript file that applies to every Interactive Grid and Interactive Report in the application automatically. Requirement The search field must accept only a-z , A-Z and 0-9 (spaces allowed, optional). The restriction must work for typing , pasting and drag-and-drop . It must apply to all pages automatically , with no per-page setup. It must cover both Interactive Grid and I...