Loading...
Loading...
Beginning in Paris, the Universal Request Core [com.snc.universal_request_core] plugin is enabled out-of-the-box. As part of this plugin, a new calculated field Task Effective Number [task_effective_number] is added to the Task [task] table. https://docs.servicenow.com/bundle/quebec-employee-service-management/page/product/universal-request/concept/UR-datamodel.html When a task table record is queried for the first time, task_effective_number gets *calculated. Unless a record is "saved", the sys_* fields do not get updated. A "save" would likely be performed after a user/process has changed some fields, and task_effective_number would be part of the same save flow. When the record is subsequently saved, the task_effective_number is saved to the database, along with the other changed fields. At this point, the sys_* fields are updated which is the normal expected platform behavior. From then on, the task_effective_number doesn’t get calculated unless number or universal_request fields change, and hence does not trigger an update of sys_* fields by itself. *task_effective_number is the identifying number that has the UR number if the task has a Universal Request associated with it. If it is not associated with a Universal Request, then the Effective Number holds current task number. The initial calculation is: If there is a UR number, populate task_effective_number with that value. If there isn’t a UR number, populate task_effective_number with the task number. See also: https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0863068 https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0863532 Symptoms: Task table records are updated unexpectedly Task table records’ sys_* fields are updated task_effective_number is populated on task records Old task records are updated Task table dependents are affected Steps to Reproduce 1. Upgrade to a Paris+ release. 2. The Universal Request Core plugin is activated Out Of Box which has a new calculated field Task Effective Number [task_effective_number] added to the Task [task] table. 3. Save a record on a task table 4. task_effective_number field value will be calculated and the other changed fields and sys_* fields will be updated.
If the Universal Request feature is not being used, you may temporarily disable the calculation and remove the calculation script on the task_effective_number Dictionary Entry. Review any custom flows/processes, internal reports, scheduled jobs, performance analytics, archiving, table cleaners, etc. which may be performing a save on task records or have a dependency on the sys_* fields. Please contact Support if additional assistance is needed.
PRB1485046
Click on a version to see all relevant bugs
ServiceNow Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.