Closed dwindibank closed 1 year ago
@Stwissel any comments on this one? I have a current version of this that we are using for calling for just custom APEX REST services, but I easily switch it to be more generic.
Either way I can provide a pull request. Thanks!
A pull request will be very much welcome
@Stwissel ... Any preference between implementing it as a "apexrest" node or a generic SF Rest node (or both)?
We have an apexrest node done now and have been using to do thousands of calls against a few custom SF Apex Rest services.
Thanks!
Apex rest would use the Salesforce config Object. I like that
On Tue, 6 Nov 2018 at 22:47, Dustin Windibank notifications@github.com wrote:
@Stwissel https://github.com/Stwissel ... Any preference between implementing it as a "apexrest" node or a generic SF Rest node (or both)?
We have an apexrest node done now and have been using to do thousands of calls against a few custom SF Apex Rest services.
Thanks!
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/Stwissel/node-red-contrib-salesforce/issues/30#issuecomment-436277839, or mute the thread https://github.com/notifications/unsubscribe-auth/AAhHVY4OiORpY1uiO6z5GLNYqIj6Ua7uks5usaD8gaJpZM4WCQc3 .
-- Mobile message, pegged on glass.
Best regards Stephan H. Wissel http://www.wissel.net/
We've been using this for a while now, so I need to finally create a Pull request. Should I do it against the main branch or will the Dev branch be released soon?
Thanks!
@dwindibank -> did you ever get to implement this?
I have some custom APEX REST services that I need to call from Node-Red. It was pretty easy to clone the SOQL node as a starting point and do some very minor changes to create an APEX REST node ... but then as I looked through the nforce api ... it seems like it might be better to just make a generic REST node that can call any of the bits the API that aren't covered by the other nodes (APEX Rest, Invocable Actions, Metadata, etc.).
What do you think makes more sense? i.e. just have specific nodes to wrap the rarer cases like nforce.apexRest, or make a general node that can wrap nforce.getUrl .putUrl .postUrl & .deleteUrl ?
Either way I can provide a pull request for the new node.
Thanks!