![]() ![]() Recently I used Application Express 5.0’s “Group Calendar” packaged app to simulate a scheduling system. We wanted to show how external systems can be launched from within Sales Cloud and then turn around and create meeting appointments via RESTful web service calls back into Fusion, and the packaged app was the quickest way to prototype a 3rd-party “scheduling” system that can make REST calls. Adding Contacts to a meeting are a two-phase REST call.Watch out for too-huge responses in APEX.(tl dr: you can use APEX to do cool REST calls and query/create via Fusion APIs) Here are some random notes picked up during this assignment for refining on future projects: I hijacked the Create Event button procedure that already existed in this packaged app, adding functionality to have the Fusion APIs create a corresponding meeting in Sales Cloud and attaching a contact to the appointment. The new R10 RESTful APIs are documented in a fancy new format, as opposed to the SOAP API format that is available in the OER. There are also some older articles on integrating to Fusion with APEX, and although the Fusion blog entries are mostly SOAP-oriented there is at least one newer one about creating a REST request in PL/SQL (albeit not to Fusion read on for that!).Īnd there’s the monstrously-large Oracle Sales Cloud There are really good R10 RESTful API intro write-ups on the FADevRel blog. Using RESTful Web Services whitepaper available on MOS. I used apex_web_service.make_rest_request to send my requests back to Sales Cloud from a PL/SQL package so that it would fit in with the existing scaffolding in the packaged app. ![]() ![]() I originally wanted to model the Fusion RESTful APIs as Web Service References in Application Express and even got the Fusion API set up as a APEX Shared Component, but ended up rewriting the call as a PL/SQL package to match the existing Group Calendar code. Still, the APEX Web Service References has a nice test harness to let tweak your headers and see the JSON response from your call. It helped me validate that the payload I was creating worked from APEX. It is unclear, however, whether the victims were gay men found dead after having visited gay bars or whether they were connected to the indicted suspects.Click here for a 3.4MB animated GIF of the testing harness proving it could create an appointment in Sales Cloud. The medical examiner’s office confirmed Wednesday that it is investigating “several additional deaths in similar circumstances” to those of Ramirez and Umberger. NBC News has spoken with several gay men who said they survived similar incidents from December 2021 to October. In the months after their deaths, more gay New Yorkers stepped forward with eerily similar accounts. This month - nearly a year after they were found dead - the New York City medical examiner’s office ruled their deaths as homicides caused by a “drug-facilitated theft.” Multiple drugs were found in their systems, including fentanyl, lidocaine and cocaine. Both had left the bars with at least one unknown person before their bank accounts were drained of thousands of dollars using facial recognition access on their phones, family members have said. Umberger and Ramirez were found dead after having visited gay bars in the city’s lively Hell’s Kitchen neighborhood last spring. However, they added that the New York City Police Department’s Hate Crime Task Force is assisting in the investigation. The officials alleged that the suspects were targeting victims for financial gain and not because of their sexual orientation. ![]()
0 Comments
Leave a Reply. |