${task_effective_number} in Paris notifications

Doug Yorke · ‎10-20-2020

I'm noticing that some notifications have been updated to use ${task_effective_number} instead of ${number}

They seem to work in the same exact way (I get the record number) in preview, and I can't find anything in the documentation to say why this changed. Just trying to figure out if we need to update notifications to use this new syntax.

Doug Yorke · ‎11-02-2020

@gml35 @Christine Ekman

I finally for a reply from HI on Friday about this. I'm including the full notes below:

Columns task.universal_request & task.task_effective_number are added as part of a new feature delivered in Paris called "Universal Request" which is part of Limited Availability.

ServiceNow Universal Request application is a comprehensive set of features that support cross-departmental Enterprise Service Management (ESM) or Global Business Services (GBS) service delivery models. It helps to deliver seamless experience to employees by unifying their service delivery efforts.

Universal request (universal_request) column will be populated when a task record is part of Universal Request.

• Effective Number (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.

It is important to have these columns in the instance as they are referred at multiple places in HR and ITSM code.

If you observe task_effective_number is not reflecting on all notifications, it is only reflecting in ESM notification

Here is the Plugin: /nav_to.do?uri=v_plugin.do?sys_id=com.snc.universal_request_core

Here is the fields which got created as new fields: /nav_to.do?uri=sys_dictionary.do?sys_id=1c8c66e9db6310108f33d9f0ce9619c2%26sysparm_view=advanced

So it doesn't matter either it is ${number} or ${task_effective_number} both reflect same numbers, but for ESM we recommend using task_effective_number.

View solution in original post

Doug Yorke · ‎01-25-2021

You could try merging in just that portion, using the Merge Tool:

https://docs.servicenow.com/bundle/paris-application-development/page/build/team-development/concept/diff-merge-tool.html

In our case, we had built completely custom Incident notifications years ago ... so the original ones which the patch was touching are inactive. I merged in all changes but kept it active=false. Just in case we use these in the future, at least we'll have the base code in place when we active them.

Paul Ciarfella · ‎01-25-2021

Agreed - and that is what we do. But I try to understand what we are merging and why.