That's right, you guessed it! It's awesome to see the indicators for incident, change, problem, outages, affected CIs, and vulnerabilities on the CI dependency map, but can we change those or add colors to them? We sure can, with a little image editing!
It has came across my radar a couple of times and until recently haven't given it the attention it really does deserve. Be aware though, that color coding anything we should be mindful of color blindness and take appropriate measures when making these changes.
To start with, let's take a look at this DOC on updating an existing image. For the indicator images, these will begin with the name "indicator-" and you can filter the list down.
***Note: Before editing and creating a new image, you may want to preserve the original by renaming. I decided to append -bu on the original name, save, remove -bu, and do an insert and stay. The original name has to be used for the system to grab the image.
Now that we have preserved our OOTB image, let's start adding some color to our image.
There isn't a good way to export or save the image since right clicking on it saves it as an .iix file type, so what I have found that works is to take a screenshot of the image and edit that as a .png file. You can fully create a new image as well, but for this write up I'm just adding a color to the indicator image. Once I have added my color of choosing to the image, in this case blue to the indicator-change-current.svg file, I select update as shown in the DOC and select my new image I created as a .png file. Once that has been updated I may need to refresh my browsers cache to see the change but the new image will now be used.
If we open a dependency map we should now be able to see the new image/color scheme that we uploaded to the system ui.
*Note: I also had updated the affected-CIs.svg image as well
If you are wondering, "Can this be promoted through an update set?" the answer is Yes, it does get tracked in an update set and can be promoted to your other instances!
7 Comments
