Created "LogFailure" method for OmniStudioRemoteAction class to be used by IP TryCatchBlock

[j-fischer]

Created "LogFailure" method for OmniStudioRemoteAction class that should be used when dealing with try-catch blocks in Integration Procedures.

[j-fischer]

Hey @jongpie,

Take a look at this PR. The reason why I created these changes is that I was working on a project with RFLIB and OmniStudio and ran into an issue. During the debugging I noticed that a TryCatchBock in an Integration Procedure did fail but did not create any log message due to the missing attributes that my Omni Logger Action expected. This was the configuration below, but nothing showed up in the logs.

The changes in this PR will make the handling of this scenario more robust, making sure some Log Event is created, whether the existing LogMessage method is used (less ideal) or better, the LogFailure method is used instead (see below). What happens in the try-catch scenario is that the IP just dumps the entire state JSON as an input since it does not allow you to add any additional attributes.

I looked over your code in Nebula and believe that you might have some unexpected behaviour in this situation as well. I am not 100% sure because you look at a lot more input attributes than RFLIB, so I just wanted to point this issue out to you just to be safe. I hope you already got it covered and, if not, that this PR will help you add the appropriate handling in Nebula.

Cheers!

[jongpie]

@j-fischer thanks for the mention! I am still... incredibly new to using OmniStudio (my only real experience with it was when adding support in Nebula Logger 😅 ), so I wasn't even aware of the TryCatchBock in IP - I definitely haven't tested this out in Nebula Logger yet. I'll try to spin up an OmniStudio this weekend to test this & see if I need to fix anything.