Expressions as parameters and other

Unknown

Expressions as parameters and other

Unknown

Hi,\r\nthis is probably more a suggestion than a question.\r\nIn my flows it happens quite frequently that I need to calculate a temporary value and pass it as a parameter.\r\nFor example, I have a loop and I want to use the \"Item index\" to get the corresponding item in an array, but they have a difference of N.\r\nIe.\r\n\titem index in an array = Item index of loop + 3\r\n\r\nThe result is that my flows, that should appear like a clean sequence of macro steps, are instead bloated with \"add\

Unknown

This is a great suggestion that we have in our backlog currently. One way to do this now without needing a new input "type" is to use a converter flow that contains within itself this logic you mention. This can help keep the main diagram clean from these non-business meaningful steps. See this link for how to use converter flows [url=https://documentation.decisions.com/docs/using-converter-flows]https://documentation.decisions.com/docs/using-converter-flows[/url].

Another, less graceful option would be to shrink the size of these steps down to very small icons. We see some customers use this pattern to retain the readability of their flow diagrams without modifying the structure already in place.