Help

Interface button to trigger automation- date modified?

Topic Labels: Automations
771 3
cancel
Showing results for 
Search instead for 
Did you mean: 
Pam_Siebert
5 - Automation Enthusiast
5 - Automation Enthusiast

When an interface button is used to trigger an automation, does it leave any kind of trail in terms of date clicked?

I am making an interface for a staff member to generate a draft contract, but she needs to do it only once. Since the button is so easy to click, I am afraid of it being generated multiple times. I thought I could somehow put a field showing below it of the date the automation ran. Thanks!

3 Replies 3

Kind of!  You'd need to create a Date field to contain that information, as well as a formula field with "NOW()", and you'd add a step to the automation to update that Date field with the value from the formula field

Showing the date the automation ran's trickier though.  I think I would handle that by having a new table with a single record in it called "History" or some such that would contain that Date and formula field I mentioned above

The Interface would then have a record picker element that would have that record picked, which would allow us to display the "Date" field from that record, showing the date the automation was last run, does that make sense?

@Pam_Siebert 

You could always just set the automation to not run again if it was already run once in the past. You can do this by simply setting a checkbox field or a date field or any other field.

Dan_Montoya
Community Manager
Community Manager

You could always have a field that has two choices "needs contract generated" and "contract generated".  At the end of your automation set the field to "contract generated".  

OR

You could use a 3rd value "contract generation in process".  Create a field that looks for the last modified time of that state field.  In your interface, you can show the state and the time so that your user will know when the state changed.  This is handy if your contract process isn't quick.  If for example it isn't successful, the "time entered state" might reflect an hour.  If it shows a longer than expected time, your user might want to start the process again by clicking on the generate button.  If the contract was successfully created 2 days ago but needs to be regenerated, the user knows that and can regenerate it.