Table of Contents

Submitting the action request content in encrypted form

An alternate to registering the data transform is to encrypt the submitted action request content. The developer can write code in a non-auto section or html fragment and include it in the harness

To ensure the action request content is submitted in encrypted form, complete the following procedure:

  1. Use the rule utility function pega_rules_utilities.pzEncryptURLActionString to encrypt the action. This function requires parameters in the following format: pega_rules_utilities.pzEncryptURLActionString(tools, "Thread",pyActivity=activityName&param1=value1&param2=value2")

    pega_rules_utilities.pzEncryptURLActionString(tools, "Thread", pyActivity=pzRunActionWrapper&pzDataTransform=setStockPriceDT")
  2. Enter a code snippet.

    Examples of a specific and a generic code snippet are shown below:
    • generic code snippet: pega_rules_utilities.pzEncryptURLActionString(tools, "Thread", "pyActivity=activityName&param1=value1&param2=value2")
    • specific code snippet: pega_rules_utilities.pzEncryptURLActionString(tools, "Thread", "pyActivity=pzRunActionWrapper&pzDataTransform=setStockPriceDT")
  3. Click Save.

Example from @baseclass.SpellCheckerMoreDialog:var oSafeUrl= SafeURL_createFromURL("<%tools.appendstring(pega_rules_utilities.pzEncryptURLActionString(tools, "Thread", "pyActivity=Data-SpellChecker.Spellcheck"));%>"); var strSpellCheckXML = httpRequestAsynch(oSafeUrl.toURL(), strPost, 50, 100);

    Have a question? Get answers now.

    Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.