Customer Portal

Something like an external dictionary?

Comments 1

  • Avatar
    David Pavlis
    Comment actions Permalink

    Your approach with external lookup table is possible.

    However, a better approach is through dictionary entry and JobFlow graphs. You can use the pair of SetJobOuput & GetJobInput components and the fact that when you call a (sub)graph, then you can map-out dictionary entry which that subgraph changes and use it in the calling graph.
    So you top level JobFlow would first call that graph which performs that REST API call and gets that one value. That value can be stored into dictionary entry, which, after that graph finishes, available to the calling graph. From there, you can pass that unique ID to other transformation graphs.

Please sign in to leave a comment.