1 Reply Latest reply on Jun 25, 2018 5:42 PM by Thad Esser

    $PROCESS$ command adding double quotes to null parameters

    Thad Esser

      Hello,

                     

      Going from ARS 8.1 to 9.1.04, I noticed a change in behavior of the Set Fields action using the $PROCESS$ command.  In 9.1.04.002, if you pass an empty field into the command, the server puts double quotes around the null value, whereas in 8.1 it doesn't.  Is that just the new way it works, or could it be a side effect of something else?

       

      I setup a super-basic test case, where I have a set fields running a process.

       

      My set fields action, setting Char01:

          Char01 = $PROCESS$ D:\test.cmd $Char02$ $Char03$

       

      test.cmd is just a simple "echo %1 %2 %3"

       

      Here are the comparison logs, when $Char02$ equals the literal text "Char2", and $Char03$ is null:

      Logs from ARS 8.1.0:               

      >    --> Passed -- perform actions

      >         0: Set Fields

      >               Status__c (7) = 0

      >                   D:\test.cmd two

      >                   Exit code: 0  Value: two 

      >               Char01 (536870913) = two 

       

      Logs from ARS 9.1.04.002:

      >    --> Passed -- perform actions

      >         0 : Set Fields

      >               Status__c (7) = 0

      > /* Mon Jun 25 2018 11:20:12.5680 */ D:\test.cmd Char2 ""

      > /* Mon Jun 25 2018 11:20:12.6160 */ Exit code: 0  Value: Char2 ""

      >               Char01 (536870913) = Char2 ""

       

      Notice that Char01 ends up with double-quotes in it on version 9.1.04.002.

       

      Thanks,

      Thad

      P.S.  Out of curiosity, in what version (between 8.1 and 9.1.04.002) did that change?