These requests require a structured JSON file that for example can be inferred from a SQL database. The server part returns generated documents upon receiving HTTP POST requests. The APEX Office Print package consists of a server component, an Oracle APEX plug-in, and the PL/SQL API. The browser doesn't need to have access to the AOP server. The template together with the data is sent in JSON format to the AOP Server. It's the database (APEX Plug-in, PL/SQL API, REST Webservice) that is doing a request to the AOP Server (either on-premises or on our cloud). Great design with finest details to enhance your business productivity.ĪPEX Office Print is a print server allowing you to create templates in Word, Excel, and PowerPoint for any type of data. It gives you the ability to run and retrieve reports from the AOP server directly from your PL/SQL code. Text, images, barcodes, formulas... it is easy to merge your data with any template you create.ĪPEX Office Print is a scalable and secure product that fits your every printing requirement. Simply Import the APEX Plug-in in your application. For example, you can print or export your Interactive Reports and Grids data in a second. It's the only solution on the market that is fully integrated with APEX. Built on in-depth technical expertise, our company provides custom-made IT services for managing business data and processes. We are an experienced partner that helps you facilitate, improve, and accelerate your business through new and innovative solutions. It saves you time and effort by creating templates in which you can easily integrate your data.ĪPEX Office Print (AOP) is a product of APEX R&D, located in Leuven, Belgium. You can easily print PDFs, Office documents, HTML or Markdown in no time. Make a template in Office, HTML or Markdown, choose data from your database and merge them into one. I also think this quote is telling: " This is extremely useful for async success/failure, because you're less interested in the exact time something became available, and more interested in reacting to the outcome.Last update: December 2021 About APEX Office Print GoalĪPEX Office Print makes printing and exporting (docx, xlsx, pptx, pdf, html, md, txt, csv, ics and more) in Oracle Application Express (APEX) or just in PL/SQL a lot easier. And extremely new, unsupported by even IE11. ha.īut they are just the native implementation of deferred objects. anything here will run before plsql finishedĮddie suggested using "promises", which sounded promising. ("CB_AJAX" // this is just => htp.p('X') If that hurts your head a little, welcome to JavaScript mechanics. " javascript return result from callback" is an obscenely googled phrase, with a fair response of: " This is impossible as you cannot use an asynchronous call inside a synchronous method." The next example uses 'deferred objects', which is jQuery's updated method for handling "success", but we can't access the callback values outside that scope, so we can't return true or false. This works, is completely synchronous, but will only work in browsers for a finite time thanks to the highlighted row ( async:false).Ĭonsole.log('success:'+ (result.length)) CB_AJAX is an AJAX callback (PL/SQL) defined on the page and returns a number as a text string. A common sentiment on from MDN.īelow are the examples we attempted for the JavaScript to return true or false, hence triggering the appropriate true/false dynamic actions. The web isn't built for it, and the specifications are making it harder for us to do so.We're in an optimistic world now: try it, work it out once it's done. We're calling the db twice, when we just need to do it once.This is what we were attempting this afternoon, and sounded good in my head but there are a few things wrong. On click -> test javascript condition, which actually calls a synchronous function to test existence in database
In revising this post, I think perhaps he set the message to some JavaScript container, which in turn is sent to the database using APP_AJAX_X01. Tom Petrus suggested a more elegant alternative (with one less step and/or didn't involve a page item?), but it was in transit time at kscope and it was a hard topic to explore without code. We need to shake it up a little to provide different colour message - success/failure etc. Notification: Display message based on item. PL/SQL: try insert, set result to page item (eg: P0_SIGNAL) I've played with this, thought about it, and I think we're already on a good wicket with another pattern. On 8 October 2015 at 09:05, Scott Wesley wrote: Imagine a button on a screen to add a record that may already exist. There was a more detailed discussion in a forum post that I'd need to dig up. The following post is slightly modified from an email conversation considering workflow from a browser based system.