How does Celigo decide when to automatically run export previews?
When you are creating input filters on flow steps Celigo will show preview/example data in the input tab of the 'Define input filter'-form.
Sometimes this data is cached, sometimes it is sourced real-time from previous export steps.
How does Celigo decide which of the two options to go for?
My first thought was cached for POST and real-time for GET, but some testing confirms it does not work like that.
And related to this, is there a way to toggle between the two options, and set fixed cached preview-data? For example I've got some transactional POST exports that I never want to trigger as a preview, and some NetSuite saved searches that not always return data, and so are very difficult to map when there is no preview data.
I found these two other requests in the community forums that are related to the same issue.
We refresh the input data when a change has been made in the flow that impacts the input data. For example, if you are viewing the scipts/hooks editor on a lookup, and you previously made a change in the transform editor, or a preceding flow step, then the input data of the scripts editor on the lookup would refresh when you open it, to show the correct input. It only refreshes when needed, so if you made changes that would not impact the input data, then the cached data will display instead.
Hope that answers your question!
Please sign in to leave a comment.