Product documentation Docs
    • English
    • Deutsch
    • 日本語
    • 한국어
    • Français
  • More Sites
    • Now Community
    • Developer Site
    • Knowledge Base
    • Product Information
    • ServiceNow.com
    • Training
    • Customer Success Center
    • ServiceNow Support Videos
  • Log in

Product documentation

  • Home
How search works:
  • Punctuation and capital letters are ignored
  • Special characters like underscores (_) are removed
  • Known synonyms are applied
  • The most relevant topics (based on weighting and matching to search terms) are listed first in search results
Topics are ranked in search results by how closely they match your search terms
  • A match on the entire phrase you typed
  • A match on part of the phrase you typed
  • A match on ALL of the terms in the phrase you typed
  • A match on ANY of the terms in the phrase you typed

Note: Matches in titles are always highly ranked.

  • Release version
    Table of Contents
    • Now Platform capabilities
Table of Contents
Choose your release version
    Home Orlando Now Platform Capabilities Now Platform capabilities Edge Encryption Edge Encryption configuration Encrypt data from a record producer

    Encrypt data from a record producer

    • Save as PDF Selected topic Topic & subtopics All topics in contents
    • Unsubscribe Log in to subscribe to topics and get notified when content changes.
    • Share this page

    Encrypt data from a record producer

    Record producers allow end users to create task-based records, such as incident records, from the Service Catalog and Service Portal. If a record producer attempts to insert data into a field marked for encryption, an invalid insert message displays and the data is not saved to the field. To configure your Edge Encryption proxy server to allow inserts from a record producer, create encryption rules from the record producer record.

    Before you begin

    Role required: security_admin

    Encrypting data from a record producer requires an encryption configuration defined for the target field. Check that you have created an encryption configuration for the target field and table before creating an encryption rule from a record producer. See Create an encryption configuration. To encrypt attachments from a record producer, Configure attachment encryption.

    Procedure

    1. Log in to your instance through the Edge Encryption proxy server.
    2. Navigate to Service Catalog > Catalog Definitions > Record Producers.
    3. Create a record producer record or open an existing record producer record.
    4. Under Related Links, select Create Edge Encryption Rule.
      Two inactive encryption rules are automatically created to encrypt data sent from the record producer to the field marked for encryption.
      Encryption rule Description
      <RecordProducerName> Rule created to process POST parameters from the Service Catalog and map variables to fields in the instance.
      <RecordProducerName>Json Rule created to process a JSON payload from the Service Portal and map variables to fields in the instance.
    5. Activate the necessary encryption rules created by the record producer.
      1. Navigate to Edge Encryption Configuration > Rules > All.
      2. Depending on where the record producer will be used, open the associated encryption rule created by the record producer and select the Active flag.
        If using the record producer in the Service Catalog, activate the <RecordProducerName> encryption rule. If using the record producer in the Service Portal, activate the <RecordProducerName>Json encryption rule.
    6. (Optional) Examine the Encryption rule Action field and add any necessary field names or statements.

      If a record producer directly maps a variable to a field in a table, the encryption rule automatically maps the variable to the correct field. However, if a variable is indirectly mapped through various scripts on the platform, you may need to update the rules to map each variable to the correct field.

      The below encryption rule was created from the Report Outage record producer and processes POST parameters from the Service Catalog to map variables to fields in the instance. Replace 'FILL ME IN' with the target field.

      Edge Encryption Rule: Report Outage

      The below encryption rule was created from the Report Outage record producer and processes a JSON payload from the Service Portal to map variables to fields in the instance. Add additional statements to map any scripted variables to the target fields.

      Edge Encryption Rule: ReportOutageJson

      When the payload from the record producer is examined, the error_message element contains the value for the short_description field. By adding the following statement, you can map the scripted variable error_message to the short_description field.

      if (jsonElement.getName() == 'error_message')
              jsonElement.valueFor(tableName, 'short_description');

      The value of the Action field becomes:

      function ReportOutageJsonAction(request) {
      	var tableName = 'incident';
      	// Some fields are set in script, additional parameter lines may need to be added
      	// current.comments is accessed via script from notes; // assignment to current.comments does NOT replace existing values
      	// current.short_description is accessed via script from short_description;
      	// current.description is accessed via script from current.short_description;
      	// current.caller_id is accessed via script from gs.getUserID();
      	var jsonContent = request.getAsJsonContent();
      	for (var jsonElementItr = jsonContent.getIterator('variables'); jsonElementItr.hasNext();) {
      		var jsonElement = jsonElementItr.next();
      		if (jsonElement.getName() == 'error_message')
      			jsonElement.valueFor(tableName, 'short_description');
                    } else {
      		        jsonElement.valueFor(tableName, jsonElement.getName());
      	}
      }

    Result

    The two encryption rules enable the record producer to insert values into fields marked for encryption from either the Service Catalog or Service Portal.

    Tags:

    Feedback
    On this page

    Previous topic

    Next topic

    • Contact Us
    • Careers
    • Terms of Use
    • Privacy Statement
    • Sitemap
    • © ServiceNow. All rights reserved.

    Release version
    Choose your release version

      Encrypt data from a record producer

      • Save as PDF Selected topic Topic & subtopics All topics in contents
      • Unsubscribe Log in to subscribe to topics and get notified when content changes.
      • Share this page

      Encrypt data from a record producer

      Record producers allow end users to create task-based records, such as incident records, from the Service Catalog and Service Portal. If a record producer attempts to insert data into a field marked for encryption, an invalid insert message displays and the data is not saved to the field. To configure your Edge Encryption proxy server to allow inserts from a record producer, create encryption rules from the record producer record.

      Before you begin

      Role required: security_admin

      Encrypting data from a record producer requires an encryption configuration defined for the target field. Check that you have created an encryption configuration for the target field and table before creating an encryption rule from a record producer. See Create an encryption configuration. To encrypt attachments from a record producer, Configure attachment encryption.

      Procedure

      1. Log in to your instance through the Edge Encryption proxy server.
      2. Navigate to Service Catalog > Catalog Definitions > Record Producers.
      3. Create a record producer record or open an existing record producer record.
      4. Under Related Links, select Create Edge Encryption Rule.
        Two inactive encryption rules are automatically created to encrypt data sent from the record producer to the field marked for encryption.
        Encryption rule Description
        <RecordProducerName> Rule created to process POST parameters from the Service Catalog and map variables to fields in the instance.
        <RecordProducerName>Json Rule created to process a JSON payload from the Service Portal and map variables to fields in the instance.
      5. Activate the necessary encryption rules created by the record producer.
        1. Navigate to Edge Encryption Configuration > Rules > All.
        2. Depending on where the record producer will be used, open the associated encryption rule created by the record producer and select the Active flag.
          If using the record producer in the Service Catalog, activate the <RecordProducerName> encryption rule. If using the record producer in the Service Portal, activate the <RecordProducerName>Json encryption rule.
      6. (Optional) Examine the Encryption rule Action field and add any necessary field names or statements.

        If a record producer directly maps a variable to a field in a table, the encryption rule automatically maps the variable to the correct field. However, if a variable is indirectly mapped through various scripts on the platform, you may need to update the rules to map each variable to the correct field.

        The below encryption rule was created from the Report Outage record producer and processes POST parameters from the Service Catalog to map variables to fields in the instance. Replace 'FILL ME IN' with the target field.

        Edge Encryption Rule: Report Outage

        The below encryption rule was created from the Report Outage record producer and processes a JSON payload from the Service Portal to map variables to fields in the instance. Add additional statements to map any scripted variables to the target fields.

        Edge Encryption Rule: ReportOutageJson

        When the payload from the record producer is examined, the error_message element contains the value for the short_description field. By adding the following statement, you can map the scripted variable error_message to the short_description field.

        if (jsonElement.getName() == 'error_message')
                jsonElement.valueFor(tableName, 'short_description');

        The value of the Action field becomes:

        function ReportOutageJsonAction(request) {
        	var tableName = 'incident';
        	// Some fields are set in script, additional parameter lines may need to be added
        	// current.comments is accessed via script from notes; // assignment to current.comments does NOT replace existing values
        	// current.short_description is accessed via script from short_description;
        	// current.description is accessed via script from current.short_description;
        	// current.caller_id is accessed via script from gs.getUserID();
        	var jsonContent = request.getAsJsonContent();
        	for (var jsonElementItr = jsonContent.getIterator('variables'); jsonElementItr.hasNext();) {
        		var jsonElement = jsonElementItr.next();
        		if (jsonElement.getName() == 'error_message')
        			jsonElement.valueFor(tableName, 'short_description');
                      } else {
        		        jsonElement.valueFor(tableName, jsonElement.getName());
        	}
        }

      Result

      The two encryption rules enable the record producer to insert values into fields marked for encryption from either the Service Catalog or Service Portal.

      Tags:

      Feedback

          Share this page

          Got it! Feel free to add a comment
          To share your product suggestions, visit the Idea Portal.
          Please let us know how to improve this content

          Check any that apply

          To share your product suggestions, visit the Idea Portal.
          Confirm

          We were unable to find "Coaching" in Jakarta. Would you like to search instead?

          No Yes
          • Contact Us
          • Careers
          • Terms of Use
          • Privacy Statement
          • Sitemap
          • © ServiceNow. All rights reserved.

          Subscribe Subscribed Unsubscribe Last updated: Tags: January February March April May June July August September October November December No Results Found Versions Search preferences successfully updated My release version successfully updated My release version successfully deleted An error has occurred. Please try again later. You have been unsubscribed from all topics. You are now subscribed to and will receive notifications if any changes are made to this page. You have been unsubscribed from this content Thank you for your feedback. Form temporarily unavailable. Please try again or contact  docfeedback@servicenow.com  to submit your comments. The topic you requested does not exist in the release. You were redirected to a related topic instead. The available release versions for this topic are listed There is no specific version for this documentation. Explore products Click to go to the page. Release notes and upgrades Click to open the dropdown menu. Delete Remove No selected version Reset This field is required You are already subscribed to this topic Attach screenshot The file you uploaded exceeds the allowed file size of 20MB. Please try again with a smaller file. Please complete the reCAPTCHA step to attach a screenshot
          Log in to personalize your search results and subscribe to topics
          No, thanks Login