Yokohama Missing information Button in SOW

[Michael Parks]

Hello, 

Recently upgraded to Yokohama and it was discovered that when working a catalog task in SOW that a reference I is missing.  We are using a field called Requested for which pulls and references the sys_user table but for this field it is missing.   It was there in Xanadu, but with Yokohama it is now missing.   We have multiple fields that reference the same table with no issues.  

What can be causing this?

[GlideFather]

Hi @Michael Parks,

this is a known error and it will be fixed in Zurich version.

More details: KB2182152 /PRB1877769: I will share it below in case that you don't have access to Support Portal:

Kindly consider marking this as the accepted solution to help others who might face the same issue in the future. I appreciate your support!

_____________________________________________

Info (i) icon for reference catalog variables is missing on RITM & SCTASK form under workspace(Example: SOW)

Description

After upgrading to the Yokohama, the info (i) icon for reference variable is missing under the variable editor of requested item(RITM) form & Catalog Task (SCTASK) form

 

Steps to Reproduce

    1. Hop onto OOB Yokohama instance.
    2. Navigate to sc_cat_item table
    3. Select any Catalog item having variables
    Example: Add/Remove users from group ( this is OOB example catalog'
    4. Click on "Try me" and enter the details on the catalog item and click 'Order Now"
    5. Request number is created
    6. Copy the request number and go that request number  record using global search or go to
    sc_request table and search for the request number
    7. Under the Related list "Requested items",  select the RITM Requested item record
    8. You will see Variables on the form. 
    9. Navigate to SOW and search for this Requested item created in Step 5.
    10.In the Variables editor 'Group Name' variableis not shown with the info(i) button.

Workaround 

This problem has been fixed. If an upgrade is possible, please refer to the Fixed In section to determine the latest version with a permanent fix that the instance can be upgraded to.

Related Problem: PRB1877769

Intended Fix Version: Zurich

Safe Harbor Statement

This "Intended Fix Version" information is meant to outline ServiceNow's general product direction and should not be relied upon in making a purchasing decision. The information provided here is for information purposes only and may not be incorporated into any contract. It is not a commitment, promise, or legal obligation to deliver any material, code, or functionality. The development, release, and timing of any features or functionality described for our products remains at ServiceNow's sole discretion.

[GlideFather]

@Michael Parks 

It’d be cool to get some feedback, please did it answer your question or you need to discuss it further? 
If all's good, please accept my reply as solution for future references, I believe I answered all of your requirements.

Please don't tell me my free time efforts were for nothing... 

Thank you!

[Michael Parks]

Hello, 

So this fix has not been helpful as it would require us to reconfigure from our current settings.  I noticed that in the KB and PRB case that this was to be fixed in a Yokohama patch.  Can you identify what patch?

[GlideFather]

Hi @Michael Parks 

the fix is expected to be delivered in Zurich version as per my comment above

Please did my reply answer your question?