Hi, I am having a lot of trouble getting un-batching to work in process flow. Once I have batched a group of tokens I can't figure out how to un-batch them again and have the tokens retain all their attributes from before batching.
It does not. You would need to use the Label Aggregation options at the bottom of the Batch properties and use the "Make Array" aggregation style.
Something like this:
Would yield this:
Just use your own label names in place of what's in the pictures. The "OldData" labels are just distribution values but this will work with whatever data you have. Also notice that the first element of each array is the data that came from the first token in the batch, which is also the token that remains after the Batch finishes.
You can then access the values with array accessing expressions like:
token.PreservedData[array_index]
As far as "Un-batching" goes, while there is no way to do this with the batch activity you could do it yourself with a Create Tokens Activity like this:
Based on the size of one of the Arrays, you could make that many tokens, and reassign their own data from the aggregation array, base don their creation rank.
Create the new tokens into a separate activity like a Start activity and Sink the original with all the Array data on it, like this:
@Regan Blackett, the batch activity is also able to create tokens, if you set a greater number of tokens leaving the activity than entering. I am not sure if this is intentionally a valid option.
@Jörg Vogel, Sure, you can use the Batch to create multiple tokens from one, that's an intended feature and if the point were to make more tokens then that would be a fine way to go. There isn't, however a good way to do the data preservation that Create Object allows. Which is what @Jenny T was specifically asking about.
If you're aggregating the tokens from many into one, then you can't un-batch that token without creating many new tokens.
If you're using a batch activity and the "release number" is the same as the "batch quantity", then the tokens will already "un-batch" and retain their original attributes upon release.
16 People are following this question.
