Skip to page contentSkip to chat
ServiceNow support
    • Community
      Ask questions, give advice, and connect with fellow ServiceNow professionals.
      Developer
      Build, test, and deploy applications
      Documentation
      Find detailed information about ServiceNow products, apps, features, and releases.
      Impact
      Accelerate ROI and amplify your expertise.
      Learning
      Build skills with instructor-led and online training.
      Partner
      Grow your business with promotions, news, and marketing tools
      ServiceNow
      Learn about ServiceNow products & solutions.
      Store
      Download certified apps and integrations that complement ServiceNow.
      Support
      Manage your instances, access self-help, and get technical support.
Requested by (requested_by) and Requested for (u_requested_for) are not copying correctly to the SCTASK record - Support and Troubleshooting
  • >
  • Knowledge Base
  • >
  • Support and Troubleshooting (Knowledge Base)
  • >
  • Requested by (requested_by) and Requested for (u_requested_for) are not copying correctly to the SCTASK record
KB0819357

Requested by (requested_by) and Requested for (u_requested_for) are not copying correctly to the SCTASK record


2120 Views Last updated : Apr 8, 2024 public Copy Permalink
KB Summary by Now Assist

Issue

The user's Requested By and Requested For values weren't transferring correctly to SCTASK records.

Resolution

It was found that there were custom Business Rules which were populating the "requested_for" and "u_requested_by" fields on both the Request (REQ) and Requested Item (RITM), but there was no custom Business Rule which was applied to the Catalog Task (SCTASK) table to perform the same functionality there. What the user was doing was taking the value stored in a variable, entered by an end-user when they ordered an item, and copying the value to the appropriate fields. Again, the user had the customization in place for Requests (sc_request) and Requested Items (sc_req_item), but not for Catalog Tasks (sc_task).

To remedy this, the user created a similar custom Business Rule on the sc_task table. Doing this resolved the issue.


The world works with ServiceNow.

Sign in for more! There's more content available only to authenticated users Sign in for more!
Did this KB article help you?
Did this KB article help you?

How would you rate your Now Support digital experience?

*

Very unsatisfied

Unsatisfied

Neutral

Satisfied

Very satisfied

Very unsatisfied

Unsatisfied

Neutral

Satisfied

Very satisfied

What can we improve? Please select all that apply.

What are we doing well? Please select all that apply.

Tell us more

*

Do you expect a response from this feedback?

  • Terms and conditions
  • Privacy statement
  • GDPR
  • Cookie policy
  • © 2025 ServiceNow. All rights reserved.