The Zurich release has arrived! Interested in new features and functionalities? Click here for more

Knowledge article view count should be always zero

dev_S
Tera Contributor

Hi Team,

 

I have requirement where the view count of the articles should be always zero, the count should not increase how to configure this.
Thanks in advance.

1 ACCEPTED SOLUTION

@dev_S 

 

check this property:

GlideFather_0-1756304315202.png

 

and/or this widget:

https://YOURINSTANCE.service-now.com/sp_config?id=widget_editor&sys_id=a47ea1cb0b9432004ce28ffe15673a5b  

GlideFather_1-1756304715603.png

 

Knowledge Management properties

Number of days (integer, default 30) used when summing article views (glide.knowman.view_age.days)Enter a number of days to consider when calculating view count. The View count field in the Knowledge form will be updated periodically to reflect the view count based on this property. For example, if you enter 60, the view count is the total number of views in the past 60 days. Enter 0 to have ServiceNow consider all views, regardless of date.
Note: If you edit this property, run the Count Knowledge Use scheduled job to see the changes immediately. By default, the Count Knowledge Use scheduled job runs daily and updates the view counts on the knowledge articles. To view the scheduled job, navigate to System Scheduler > Scheduled Jobs > Scheduled Jobs.

New customers as of the Paris release will not have access to the View count property and Count Knowledge scheduled job. Existing customers prior to the Paris release can continue to use the property and scheduled job.

If you set the property value to 0:

  • The Count Knowledge scheduled job does not run.
  • The View count of an article does not have a rolling count, the existing view count gets incremented for every article view
Note: Beginning Vancouver release, glide.knowman.view_age.days and Count Knowledge scheduled job is deprecated. So, set the glide.knowman.view_age.days to zero and do not use it.
 
 
 
 
 
 
 
 

 

 

———
/* If my response wasn’t a total disaster ↙️ drop a Kudos or Accept as Solution ↘️ Cheers! */


View solution in original post

2 REPLIES 2

GlideFather
Tera Patron

Hi @dev_S,

 

wouldn't it make more sense just to hide the count? What is the purpose of showing 0 which wouldn't be true?

———
/* If my response wasn’t a total disaster ↙️ drop a Kudos or Accept as Solution ↘️ Cheers! */


@dev_S 

 

check this property:

GlideFather_0-1756304315202.png

 

and/or this widget:

https://YOURINSTANCE.service-now.com/sp_config?id=widget_editor&sys_id=a47ea1cb0b9432004ce28ffe15673a5b  

GlideFather_1-1756304715603.png

 

Knowledge Management properties

Number of days (integer, default 30) used when summing article views (glide.knowman.view_age.days)Enter a number of days to consider when calculating view count. The View count field in the Knowledge form will be updated periodically to reflect the view count based on this property. For example, if you enter 60, the view count is the total number of views in the past 60 days. Enter 0 to have ServiceNow consider all views, regardless of date.
Note: If you edit this property, run the Count Knowledge Use scheduled job to see the changes immediately. By default, the Count Knowledge Use scheduled job runs daily and updates the view counts on the knowledge articles. To view the scheduled job, navigate to System Scheduler > Scheduled Jobs > Scheduled Jobs.

New customers as of the Paris release will not have access to the View count property and Count Knowledge scheduled job. Existing customers prior to the Paris release can continue to use the property and scheduled job.

If you set the property value to 0:

  • The Count Knowledge scheduled job does not run.
  • The View count of an article does not have a rolling count, the existing view count gets incremented for every article view
Note: Beginning Vancouver release, glide.knowman.view_age.days and Count Knowledge scheduled job is deprecated. So, set the glide.knowman.view_age.days to zero and do not use it.
 
 
 
 
 
 
 
 

 

 

———
/* If my response wasn’t a total disaster ↙️ drop a Kudos or Accept as Solution ↘️ Cheers! */