Create Value with “Descriptions” in Platform Analytics Components

Thomas_Davis
Administrator
Administrator
‎11-25-2019 07:10 AM
find_real_file.png A description is like the marketing copy used to describe a product’s value to a potential customer. A descriptive Description provides customers with details around features, problems it solves and other benefits to help generate value you in its use. A Description is one of the three key elements in fiction, so it holds very strong power in helping someone understand what they are getting with it. And in ServiceNow Performance Analytics, the value is as important as it would be a novel!!! 

Descriptions give you the potential opportunity to have some Governance around what is being created. Encourage people to go and look at what is already available and read the Description. In a lot of situations, something is already out there that will work. What we don’t want is creation to happen, just to happen. Things that are created should have value and be something new. Creating something with a different name, but does the same as something else, is redundant and unnecessary.

 

Here are some examples of places that Descriptions have incredible value.
(Honestly, get in the habit of putting a Description anywhere that allows it)

  • Indicator Sources– Many Indicator Sources come OOTB, look at what is already created before generating something new .
  • Breakdown Sources - Many Breakdown Sources come OOTB, look at what is already created before generating something new.
  • Automated Indicators – “These are generated by default based on settings made within the Automated Indicator setup.” However, if you think it needs more detail, put it in.
  • Formula Indicators- Many Formula Indicators come OOTB, look at what is already created before generating something new.
  • Indicator Groups– Utilize Descriptions to let someone reading know what the Indicator Group consists of.
  • Automated Breakdowns- Many Automated Breakdowns come OOTB, look at what is already created before generating something new.
  • Bucket Groups- Utilize Descriptions to let someone reading know what the Bucket Group consists of.
  • Widgets - Many Widgets come OOTB, look at what is already created before generating something new.
  • Data Collection Jobs – Descriptions are so vital here, you want to maintain how many jobs have been created, which then also maintains how many jobs will be running on your system regularly.

 

The list can go on and on, of where you should use Descriptions. Make a Default Rule, if a Description Field is available, your Organization will maximize its power. Keep your Platform clean with the utilization of Descriptions, everywhere possible.

  • 603 Views