This would be a very convenient option: start a step and not wait for it to finish. For example, I need to wake up the model that will be needed in step 7. It takes 30 minutes to wake up, so I have to start waking up in parallel with step 4.
Hi Golosov!
This idea would be useful for large integrations. It would be great if there was a setting where the developer could specify whether to wait for the step to complete or continue on. 👍️
Hi Razarenov,
Thank for the vote!
I am quite sure this is already somewhere on the roadmap
I'm so looking forward to it and trying to bring the moment closer
Thanks for sharing this feedback! Today the default behavior is that status controls the flow outcome.
The ability to configure when a flow should stop (or continue) based on Cloudworks termination status ("failures", "partial success") is on our roadmap.
Hello all, our recent launch includes the following capabilities (which maybe of interest to this thread):
1. Continuity of the flow can be configured based on a step's status, allowing more flexibility in constructing complex data flows 2. Step count of 20 per flow (increased from 10 per flow) to support longer chains. 3. Re-run flow from any step, allowing for ease of troubleshooting.
More details here:
https://help.anaplan.com/ee054c8c-6eb7-44af-8334-4136a15302fc-Manage-integrations-flow-steps
Hi @AshwinK, thanks for the update!
Bringing this up again as the previous post from "5 years ago" is gettling lost. We need drill to transaction on the New UX, it is stopping us transitioning to the New UX Dashboards, as we use it daily, even hourly in our Supply chain function. Are there any plans to add Drill to Transaction to the new UX Please?
In as much detail as possible, describe the problem or experience related to your idea. Please provide the context of what you were trying to do and include specific examples or workarounds: A dropdown menu / fold option as a UX element would be extremely beneficial for users who want to extract important information or…
Today we can select within our Date dimension Total Year or Quarter. We would expect that the system with apply the calculation on the related months underneath. But this seems not to be the case. Only when we specify a single month the calculation will be applied. During year-end close we have to adjust certain movements…
