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.
Printing debug log information in Edge Encryption Rules - Support and Troubleshooting
  • >
  • Knowledge Base
  • >
  • Support and Troubleshooting (Knowledge Base)
  • >
  • Printing debug log information in Edge Encryption Rules
KB0656940

Printing debug log information in Edge Encryption Rules


799 Views Last updated : Jul 30, 2024 public Copy Permalink
KB Summary by Now Assist

Issue

Printing debug log information in Edge  Encryption Rules



Overview


Edge Encryption provides the ability to encrypt the column data before the data is sent over the Internet to the instance. The data remains encrypted while stored in the instance. The encrypted data is sent back to the proxy application when requested. Finally, the encrypted data is decrypted by the proxy before being sent to the client in company's network. Using Encryption Configurations, the column and the corresponding table can be configured so that the data is encrypted for that column. 

In HTTP requests on the way to the instance, for example creating an incident using Record Producer, it may be necessary to identify and encrypt sensitive information. You can write encryption rules to identify, interpret, and encrypt data in such requests, mapping fields in the request to Glide table-field names on your instance.
 
Encryption rules are scripts executed on the Edge Encryption proxy server to map fields in a request to fields in a table on your ServiceNow instance. An encryption rule tells the Edge Encryption proxy server how to encrypt data in custom payloads.
 
An Encryption rule contains three parts:
  1. Condition
  2. Action
  3. Order
Without the encryption rule, if an attempt is made to insert the data through HTTP request into the encrypted column even when the call is made from the proxy network, the insert fails.
  
During the creation of the encryption rules it might be necessary to include debug statements in the Condition in order to check if the conditions are met and encryption rules is invoked
 
Since Encryption rules are written in JavaScript and are executed on the client proxy, Server side debug statements(Glide APIs) such as gs.log cannot be used in-order for debugging purpose.

In order to print log statements for debugging purpose in Edge Encryption Rules, print function can be used as shown the the screenshot below.

The log information is printed in the wrapper log in the logs folder  The log folder can be found under the Edge Encryption Server installation folder.

Please note gs.log or gs.print statements does not work inside the edge encryption rules.

The below screenshots demonstrates how to include the print statement and where to check in the logs.

 


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.