We can duplicate a condition and duplicate an action, but i’m missing the possibility the duplicate the if/then clause.
Could this be added in the near future?
Thanks
This is definitely a feature worth asking for, but I will add that I often just duplicate the entire trigger in these scenarios. Its the exact same amount of overhead, but I find that separating logic across multiple triggers has a key benefit-- I can use the trigger name as a better descriptor.
Perhaps, this is a learned behavior from the missing feature, but worth sharing me thinks!
Hi Bart, thank you for posting this – and Daniel for following up!
Could I ask what your use case is in duplicating both the trigger and the if/then clause? Are you copying the same logic to multiple parts of your app, or possibly also multiple apps?
We are working on the ability to write shared logic - wrapped in a Function call. Very exciting, and hopefully addressing some of the core pain points with copying logic.
- Olga.
I have a use case, where I have 12 Variables to set.
There are three cases:
- Output from connector function contains values for that area:
→ All 12 Variables get a value assigned from the Connector output variables - Output defines actively a default:
→ All 12 Variables get a “0” - No Output for that area available:
→ All twelve get an empty string “”
So it would be neat to copy the if/then and only switch the values un the right side, for the “if” and for all 12 Variables.
E.g.:
If:
Variable “check” is equal to “x”
Then:
Data Manipulation > Store > Variable > “value” > “input”
…
You only have to change “x” and “value” instead of building everything from scratch.
This (shortest possible) sample statement is at least 20 clicks.
copying this if/then would safe 15 of them (copy + 4)
2 Likes
Hi Olga,
To give you an easy example. If entry 1 in a table is not empty, go to step 1. If entry 2 in a table is not empty, go to step 2 etc etc.
If you could copy/paste the if then clause, then you only need to make minor changes to each block.
I know you can copy and paste triggers (with a maximum of 100 triggers), but copy/pasting an if/then clause would be way more efficient.
1 Like
@danielpomeranz I do this same procedure and believe it’s definitely a habit built from the missing duplicate If/Then section feature…and to keep extensive triggers organized with titles/descriptions like you mentioned.
@OlgaStroilova to fully eliminate the need for many separate triggers in addition to duplicating If/Then sections Tulip should also add in the commenting within triggers feature to keep it organized as discussed in many other topics such as: Quality of life: Comments in triggers - Product Suggestions - Tulip Community
Hi @OlgaStroilova, is there any planned release for this feature? Currently it’s a huge effort to manually duplicate if/then clause.
1 Like
Hi @akshay96 , we’ve been monitoring the votes and activity on this thread - we acknowledge that duplicating conditional if/then clauses is a pain point in triggers today.
I brought this up again with the team today, and we’re sizing to see if a quick win on this front is feasible to fit in. We don’t have a timeline yet, and I’ll follow up here when we know more.
More broadly we’ll make it easier to work with duplicated/reused logic via Functions, planned for late summer/early fall
1 Like
I really appreciate this development, but that’s not a solution for duplication of if/then clauses.
usually you want to copy the first case (if/then…) to the second (else/then…) and third and then only adopt the action details.
All together would be one reusable function.
For example, when saving to a table record, you have an action for each column. This can easily be 15 columns or so.
That means you have to add the 15 actions for each case. (3 Cases → 45 actions).
If you can copy that you only have to adjust the case and the data to save…
Reusable functions do not help here…