About michaelsysec242

Hey @EnesOzdemir ,   you could set all the details you want to a custom key of your choosing by using the !Set command. Afterwards you can use the  "demisto.get(demisto.context(), 'key_name')" As long as the details you want are in the Context Data you can always access what you need. Use the Try and Except flow to catch errors yet you can test that the field exists and is not empty with other built-in tools.  In regards to the main difference between custom fields and incident fields I cant provide you with an exact difference between them in regards to CommonUserPython.    ... View more

Hello, To be honest it very much depends on how and where you want to use the data. There are quite a few options for dealing with context data dynamically such as "ContextFilter" : Explanation -  Filter context keys by applying one of the various available manipulations and storing in a new context key. Please notice that the resulting context key will not be available automatically as an option but you can still specify it.   From experience however I would recommend to write a custom automation script that will dynamically interact and sort the data from the key "data". This way you can see exactly what you mare working with and provide Attestation for each stage of further interaction. In any case please elaborate on what you plan on doing with the data you have received, perhaps others would be able to provide a more direct solution.    ... View more

Hello,  I have encountered this in the past. You can just skip the warnings, implement your credentials on the integration and then perform "Test". The initial test will take a few moments, at this stage the server will acquire the images it needs automatically. Use the "/docker_images" to verify that the new images are installed. You don't have to check this because it is performed by default.    ... View more