Forum Discussion

Santeri's avatar
Santeri
Icon for Contributor rankContributor
27 days ago

Updates to EM7_RESULT handling?

Hi,

During SL1 version update we have noticed that EM7_RESULT variable is going to be re-formatted to different type during snippet execution. For example if we populate the variable with list and with tuple elements, the variable is getting re-formatted to nested list. For example EM7_RESULT = [("test1", "test2")], is re-formatted after snippet execution to [["test1", test2"]] format.

Is this change documented somewhere and in which version this update was implemented?

4 Replies

  • Hi Santeri,

    This is the feedback from engineering.  The change could have been a related to JSON serialization done for Data Pull in 12.1.2 and 12.2.1.

    They would like to know if this is causing a problem.  They said from a code standpoint a list of tuples and a list of lists end up behaving pretty similarly.

    Regards,

    Erick

    • Santeri's avatar
      Santeri
      Icon for Contributor rankContributor

      Hi,

      Thanks for the information. Issue is that we have lot of custom automations which are using this EM7_RESULT variable to pass information between snippet actions in our run book automations. I think that we have relied on that the variable would return data as the same format as we populated it. Now we are going to have to check, update and test those automations to ensure they are working as intended with this new model and it requires lot of work. Would have also hoped that this kind of changes would have documented somewhere and received information about this change beforehand so we could have prepare to it more properly.

      Regards,
      Santeri

  • I would like to also add that we didn't have this issue with 12.1.2 version but it appeared in 12.3.2 version so maybe there is some other changes which can be related to this than this mentioned data pull change?

    • ErickBurgess's avatar
      ErickBurgess
      Icon for Moderator rankModerator

      Hi Santeri,

      Engineering confirmed this is related to JSON serialization, but it wasn't implemented until 12.3.0.  It should have been documented and a ticket has been created for documentation to update this.

      Regards,

      Erick