Forum Discussion

mikeandrews's avatar
mikeandrews
New Contributor III
9 years ago

Passing parameters/session variables between nested pipelines/snaps

Early warning - I’m a newbie to the platform… I want to wrap up various bits of logic/lookups/data retrieval in reusable pipelines that mask the underlying complexity (eg finding and reading a part...
dmiller's avatar
dmiller
Former Employee
2 years ago
Copy LinkReport

I'm looking to see if I have a pipeline for this...(think I may have broken it up into several small ones by asset type.)

Short term path, in classic Manager, you can use Asset Search to see where they are working to get a list of projects to work with, you can have a pipeline to find and delete assets by project (searching for their ID using everything before the @ seems to work best for me).

Some things to keep in mind when if you want to build your own pipeline:

  • This would best be used on non-admins users that have left since admins often create shared assets and own those assets by default. You don't want to accidentally delete someone else's project.
  • You would need to delete their assets before you remove them. Once they are deleted, any outstanding assets are reassigned to the admin that removed them.
  • The SnapLogic List Snap is your friend. To find files, use SnapLogic List set to All Assets (with a path to their project to lessen the load), followed by a Filter set to "$asset_type=='File' "
  • mikeandrews's avatar
    mikeandrews
    New Contributor III
    9 years ago
    Copy LinkReport

    thanks a lot Shayne, I will go with parameters and try using the underscore syntax to pass them out and along the workflow. will post again later with an update on how i got on 🙂

    • mikeandrews's avatar
      mikeandrews
      New Contributor III
      9 years ago
      Copy LinkReport

      hmm, snaps vs scripts table could be a bit more prominent in the help/docs… ie Script snap:

      Does not support pipeline _parameters
      Supports only Document input/output
      Does not support Accounts
      Often awkward to debug
      Cannot be unit tested

      I agree the Script snap is awkward to debug… :). And am surprised there’s no feature to pass in/out parameters. Some stuff cant be achieved with the standard Transform snaps, but i have to fake a document as a ScriptHook input to pass in a parameter and then try and work out the syntax with the Mapper to take the subsequent output and write that to a pipeline parameter to be used later in the flow by other snaps. I thought it would be simple/quick to do some basic js/python in a Script but looks like i may have to author a custom Snap with the SDK. Will persevere a few more hours with the Script snap…