Trigger Rules in Buttons as an Action / Vice Versa

[RonMakesSystems]

I have a “Send to Accountant” function that should be triggered automatically, and can also be triggered by button.

Currently there are two solutions:

1. Same rule logic and setup both on button and on rules. (Not ideal due to maintainance)
2. Trigger when a checkbox is checked, and button checks a checkbox. Then the button just checks the checkbox. (Not ideal as the rule turns off after 5 errors, and also errors from the rule are not seen by users.)

A solution to this could be the ability to trigger actions from each other.
Discussed: Click Action Buttons with an Action Button? - #8 by Oleg

[Chr1sG]

@RonMakesSystems

Not ideal as the rule turns off after 5 errors

Why are there errors?

[RonMakesSystems]

In this particular case it’s that the pdf is too large to send via email. But it can be relevant for other errors too.

[Chr1sG]

Click Action Buttons with an Action Button?

Just for the sake of logic organisation (and not having the same code in several places) – is it possible to “click” an Action Button from the script of another Action Button? Call it like a method? Since it is created like a field, I figured it should also be accessible from the script like one? Simple use case: suppose both tasks and subtasks have an “Assign to me” button. By clicking “Assign to me” on a task can I auto-click “Assign to me” on every connected subtask? If yes, please help me …

I think this would solve it (your automation could ‘press’ the button).
If you use the network inspector, you can probably reverse engineer the (unofficial and not guaranteed to remain stable) API call that causes a button to be pressed

[RonMakesSystems]

It could solve the maintenance, but it wouldn’t solve the core issue.

I need people to press the button, then get the error if the email doesn’t go through.

[Chr1sG]

This is what I meant:

• set up the the actions as a button
• set up an automation rule with the appropriate trigger, where the only action in the automation is to press the button

If a user presses the button, and an error in the action occurs, they should see a warning.
If the automation presses the button, and an error occurs, then there is no-one to see the error anyway(!)

If the error is something downstream (like your email service rejecting large files) then I don’t think Fibery can catch this error no matter what.

[RonMakesSystems]

Ooh interesting! Now I see.

In this scenario I would need to make three buttons, two of which hidden and conditionally “pressed” when the first one is pressed. But this could indeed solve it!!

(just bc of complexity of the “reply” vs non-reply email to keep things in the same thread)

Thanks Chris!

[Chr1sG]

@RonMakesSystems

I would need to make three buttons, two of which hidden and conditionally “pressed” when the first one is pressed.

I guess this is because buttons don’t have flow control (if .. then … else) right?

[RonMakesSystems]

Yup. Exactly.