Notifications

86 views

Description

Increasing the max length of sys_user, for example, from 40 to 100, and increasing the user ID to more than 40 characters while sys_updated_by or sys_created_by remain the same (a max length of 40 characters) breaks the activity stream of the Visual Task Board.

Steps to Reproduce

  1. Log in to an instance as ITIL.

  2. Create a new free form Visual Task Board.

  3. Add a task in the To Do column.

  4. Click on the card.

    Note that the activity stream is displayed.

  5. Add a user to the newly created Visual Task Board.

  6. Impersonate the user.

  7. Go to the Visual Task Board and change the card from the To Do lane to the Doing lane.

  8. Open the card.

    Note that the activity stream shows that the user changed the card from lane to lane.

  9. Impersonate maint.

  10. Go to the Visual Task Board and open the card.

    Note that the activity stream shows that the user changed the card from lane to lane.

  11. Go to the user record's user definition and increase the character max length of its user ID from 40 to 100 (that is, the sys_dictionary record for the user_name column for sys_user table.

  12. Change the user's User ID to a string longer than 40 characters.

  13. Impersonate this user and change the card from the Doing lane to the To Do lane.

  14. Open the card.

  15. Note that the activity stream is showing no activity.

    sys_updated_by is now 50 characters compared to the max length in sys_user, which is 40 characters. This causes the Visual Task Board activity stream to fail. This same problem occurs with sys_created_by.

 

Workaround

This issue is under review. To receive notifications when more information is available, subscribe to this Known Error article by clicking the Subscribe button at the top right of the article. If you are able to upgrade, review the Fixed In or Intended Fix Version fields to determine whether any versions have a planned or permanent fix.

 


Related Problem: PRB1089529

Seen In

Istanbul Patch 5 Hot Fix 1

Intended Fix Version

Madrid

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.

Associated Community Threads

There is no data to report.

Article Information

Last Updated:2018-08-10 09:30:11
Published:2018-06-04