regarding the way powershell calls in $COMPLETE_JSON_FILE

This is not the same json object you receive by making an api call to view a request.For instance, any custom $obj.request.udf_fields will not be exposed the same way the $COMPLETE_JSON_FILE is, it looks as if the latter already converts any custom fields to their label names and values, right on the root request object. 

So i am having difficulty in thinking up a way to test my scripts against the actual $COMPLETE_JSON_FILE object that my script will be using... I could manually create a json object to mimic this, but that would get old recreating it over and over, even if i wrote a way to script that creation...

When the script triggers, and you see the JSON file created in the \\serverName\ManageEngine\ServiceDesk\integration\custom_scripts\request folder, it gets cleaned up immediately, too fast to copy and paste elsewhere. 

So im curious as to how some of you all might have figured out a way to work with that initial $COMPLETE_JSON_FILE for testing. Im sure its something simple im missing...