How to analyze when inline images crashes in Requests

How to analyze when inline images crashes in Requests

If any image on the Request description is crashed like the below image, you can follow the below steps to analyze the issue. 


Steps to analyze:
Right click on the image in the request description and click on Inspect, and there will be an IMG html tag (as per the screenshot below). Check the 'src' attribute in which the file path of the image will be given,



-> It will be similar to '/inlineimages/WorkOrder/1200000002/03a918363e3f4ecc990ea475854d58f5.jpg'.

-> You can right click on the tab and select edit as HTML to view the full path, if it is trimmed.



 -> The path defined will be under <Application Folder-> Inline Images>.

-> Check whether the same image of the Request description exists in that path.

-> Now check if that is the same image that has to be in the conversation with that 'src' attribute. repeat the same steps to verify the same with the image in the Conversation as well.

If the path is trimmed the image happens to break in the application. By following the above steps the same can be verified.

Note:
If the image files in both the paths exists, then by recreating the issue, logs needs to be analyzed further. 

                  New to ADSelfService Plus?

                    • Related Articles

                    • Inline images broken after SCP Upgrade

                      We suspect that this issue may arise if the migration schedule has not been run post-upgrade. To troubleshoot this issue further, we kindly request the output of the following query. Please connect to the database of the working build and execute the ...
                    • Inline Images are Not Fetched Properly due to the IsInline Property 'false' assignment

                      About : For the customers using Microsoft Graph or EWS, Microsoft API returns isInline as "false" for inline images in some environment. There is no known reasons behind this behaviour from their documentation. One such possible reason for this ...
                    • Exception while Processing Inline Image with incorrect file name extension

                      Reference : #7938623, #8561970 Cause : Inline Images could not be processed with incorrect file name, for example "4d54308871ec465c8233d0f470db0308.do?sys_id=4fdfcb17475c1d50c594c133846d436a" . While constructing the filename in our end, the values ...
                    • Mail Fetching Stopped Due to Inline Image Handling

                      Issue Cause : While fetching a mail, in certain mail servers, cid of inline image is not parsed correctly. Once inline stream is converted to image, cid in src attr will be replaced with image url. cid for uploaded inline image in mail content is not ...
                    • Inline images dropped due to "x-png" image type

                      Issue: The embedded inline images in the mail gets dropped Reason: The embedded inline images in the content has the data uri as "data:image/x-png;base64,xxxx". While processing this embedded image, we generate the inline image file name as ...