tag:blogger.com,1999:blog-4818542164384221282.post8535972975565607178..comments2024-02-12T19:54:33.009+08:00Comments on Grassroots Oracle: Calling PL/SQL from JavaScript in APEXScott Wesleyhttp://www.blogger.com/profile/18106937181788036683noreply@blogger.comBlogger7125tag:blogger.com,1999:blog-4818542164384221282.post-33894422369599224672016-03-09T23:05:35.542+08:002016-03-09T23:05:35.542+08:00Stew, I've got a few more posts in mind that e...Stew, I've got a few more posts in mind that explore this further, just a matter of time.Scott Wesleyhttps://www.blogger.com/profile/18106937181788036683noreply@blogger.comtag:blogger.com,1999:blog-4818542164384221282.post-41242470142062640292016-01-09T00:13:25.130+08:002016-01-09T00:13:25.130+08:00Pardon my ignorance on this topic, but would you m...Pardon my ignorance on this topic, but would you mind fleshing this technique out a bit? For example, I don't see anything in the 2 Javascript scripts that push a value to the P0_SIGNAL item. Something closer to a recipe would be incredibly helpful for those of us who don't get the thrill of working with Apex daily.<br /><br />Thanks,<br /><br />StewStewhttps://www.blogger.com/profile/05177922393895344852noreply@blogger.comtag:blogger.com,1999:blog-4818542164384221282.post-25754216269001245822016-01-07T21:51:28.213+08:002016-01-07T21:51:28.213+08:00I used calls to apex.server.process fairly often f...I used calls to apex.server.process fairly often from dynamic actions. Alerts to the user are issued directly from a promise .done() handler rather than by defining another true action. I find that this approach works well.David Lawtonhttps://www.blogger.com/profile/00595144757512688458noreply@blogger.comtag:blogger.com,1999:blog-4818542164384221282.post-47135053911033082282015-12-22T18:55:13.449+08:002015-12-22T18:55:13.449+08:00This comment has been removed by the author.David Lawtonhttps://www.blogger.com/profile/00595144757512688458noreply@blogger.comtag:blogger.com,1999:blog-4818542164384221282.post-65651702760812076942015-12-22T18:52:43.116+08:002015-12-22T18:52:43.116+08:00This comment has been removed by the author.David Lawtonhttps://www.blogger.com/profile/00595144757512688458noreply@blogger.comtag:blogger.com,1999:blog-4818542164384221282.post-29393549913737945872015-12-22T00:23:28.292+08:002015-12-22T00:23:28.292+08:00Hi Andre,
never heard that APEX is a fiddler'...Hi Andre, <br /><br />never heard that APEX is a fiddler's tool. On the contrary 95% you get decleratively. The good part is, that the other 5% - no matter how crazy the requirements are - can be achieved too, because APEX doesn't restrict you on the back end or front end side. The problem posted here is pure JavaScript. I understand only 80%, but it's good to know that I can ask Scott for the other 20% :-)<br /><br />JuergenJuergen Schusterhttps://www.blogger.com/profile/12979566632464799037noreply@blogger.comtag:blogger.com,1999:blog-4818542164384221282.post-18144067311821083662015-12-20T20:15:15.561+08:002015-12-20T20:15:15.561+08:00Hi Scott,
All your investigations in honour!
Howev...Hi Scott,<br />All your investigations in honour!<br />However I absolutely do think that things like this indeed have to be an integrated part of the developement environment. It's elementary. And so I think it's an elementary task of the dev team to prepare the tool to get it into a state ready for use.<br />It doesn't make sence to let lots of people fiddle around to find a more or less good/practical solution. Exacly such things is oil to the fire of people who criticize that Apex is (at least halfway) a fiddler's tool. No one of us want to put oil into the fire.<br />I really hope 5.1 will make also a step forward regarding this issue too.<br />Well, they still have time until end of april...<br />AndreAnonymousnoreply@blogger.com