pbackstrom
Programmer
I am thinking of using a reusable sequence generator for a cycle of 22 sessions in one workflow, each of the 22 using the same mapping.
The sequence generator would tell the mapping which iteration it is on, which I would use for some of my transformations.
I can Cycle it at 22 so it should work OK, but I am nervous that it would get out of synch if for instance one of the sessions failed.
At best I would have a mapping (or something) that would set it to 1 at the beginning of each workflow. Second best would be that production folks could reset it to 1 if we got out of synch.
But doc says you can only reset a non-reusable sequence generator. Any hints?
The sequence generator would tell the mapping which iteration it is on, which I would use for some of my transformations.
I can Cycle it at 22 so it should work OK, but I am nervous that it would get out of synch if for instance one of the sessions failed.
At best I would have a mapping (or something) that would set it to 1 at the beginning of each workflow. Second best would be that production folks could reset it to 1 if we got out of synch.
But doc says you can only reset a non-reusable sequence generator. Any hints?
