The Scheduled Published Date must be set at least 24 hr after the current If the date value is taken

Rocco K_hling
Tera Contributor

‎12-17-2023 11:33 PM

Hello community,

 

I hope my question about knowledge management is in the right place.

 

I encountered a problem here that we have had since the release upgrade to "Utah Patch 7".

If a date value for "planned publication" is entered or changed for the first time in the draft of a knowledge article, it must be in the future.

 

If the date value is taken to be a value that is less than +24 hours, e.g. 2023-12-14 23:12:27, the error message will be displayed immediately and when saving: "The Scheduled Published Date must be set at least 24 hr after the current date." Strictly speaking, a value must be taken that is +24 hours and + a few minutes above the timestamp of the last update. If the system has accepted this date, the draft can be further edited and saved. The publications will then take place according to the rule either at the specified time or, if this has been exceeded, immediately.


The problem is that once a "planned publication" has been used and saved in the draft, information must always be entered there afterwards. Deletion is not accepted but a value must be used in the future.

If this "mistake" is made, the draft article cannot be published immediately.

 

Has anyone else noticed this and what general solutions are there other than not using “planned publication” or always using a date in the future?


Thanks in advance,

Rocco

0 Helpfuls
  • 1,403 Views
2 REPLIES 2

Eoghan Sinnott
Kilo Sage
Kilo Sage

‎12-18-2023 02:42 AM

Hi Rocco, 

 

We also had this issue post Utah upgrade. Tried some fixes including https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB1515205 but in the end had to have a HI ticket opened with ServiceNow to resolve. 

 

Regards,

Rich F
Tera Contributor

‎12-18-2023 06:43 AM

We ran into this issue with Utah as well.  The problem is that the Business Rule, Client Script and a test within 

KnowledgeUIActionSNC.publish force the error when the field changes to blank.  We prototyped a solution wherein we added a condition requiring the field to be non-blank to the business rule, and overrode KnowledgeUIActionSNC.publish to add a test that the field is not empty.  The Client script  does not appear to care.
 
We have not deployed this fix because, when we were smoke testing the Vancouver Patch 4, we found that ServiceNow had already implemented changes similar to what I have described here (it was not in our previous patch of Vancouver). 
 
We will observe carefully as we move the upgrade through our stack, but, to all appearances, SN has remedied this to accept a blank value without error.