Forum Discussion

Ksivagurunathan's avatar
Ksivagurunathan
Contributor
7 years ago

Triggered Task node not available

Hello , Our snaplogic nodes are not load balanced currently. Snaplogic tied all of our production triggered task to one node. even though we have more than one node in production. If that nodes goes down or decommissioned for some reason, could we continue to use the task with cloud url instead of on-premises secure url ? Any faced the issue and what is the recommended solution here. Load balancing the nodes is not our first preferred option for short term solution.

8 Replies

    • pavan_gangisett's avatar
      pavan_gangisett
      New Contributor II
      7 years ago

      Hi Ajay,

      it is not working as expected.
      Input Json:
      [
      {department_Id: 1,
      details: [
      { firstname: “a”, lastname: “b”, id: 1},
      { firstname: “c”, lastname: “d”, id: 2}
      ]
      },
      {department_Id: 2,
      details: [
      { firstname: “e”, lastname: “f”, id: 3},
      { firstname: “g”, lastname: “h”, id: 4}
      ]
      }
      ]

      Expected Output Json:
      [
      {department_Id: 1,
      users: [
      { name: “a b”, id: 1},
      { name: “c d”, id: 2}
      ]
      },
      {department_Id: 2,
      users: [
      { name: “e f”, id: 3},
      { name: “g h”, id: 4}
      ]
      }
      ]

      • tlikarish's avatar
        tlikarish
        Employee
        7 years ago

        Think this does what you’re looking for.

        I used the first mapper to re-map the entries in the details array and then the second mapper to rename the details property to users.

        Here is what I was mentioning about using the Mapping Root. This is very helpful for working with nested arrays.

        Here is the complete example for you to try out. Good luck with your work.

        make-users_2019_06_20.slp (5.5 KB)