Dear community,
I saw one of the workflow whereby it store result as cache as per the screenshot below:
May i know normally in what circumstance we need to store the result as cache and could you please advise on this?
Thank you.
Solved! Go to Solution.
@SH_94
One case I can think of is that the increment calculation for a regular basis such as daily, weekly.
The saved yxdb from leg#1 of Block Until Done tool will be served as input for calculation of next increment.
#Leg#2 will read the "old" data, I suppose.
Hi @Qiu ,
I think that is one of the reason the worklfow being set up in this way for the increment calculation.
But curious , why we cant consolidate the file and calculate it? Instead of doing in the workflow that as per screenshot.
Thank you.
@SH_94
We need to consider it as a loop.
The output will be serving as input for next run, so the output shall be saved in where as "Cache".