I notice that the Update Custom action button has a ‘When’ matching and Run on save checkbox, whereas Convert Records Action button doesn’t have the option to run on save, or will only run once.
The user case is that once a user submits a record I want to automatically run a convert button to create an X-User record and also to archive the record created to preserve it before the x-user subsequently updates it. These are ‘Convert’ buttons and Email buttons that are great manually but how to auto press them?
I know that Zapier can, trigger when new entry created in Ragic Main form, Create Entries in External user and Archive sheets externally to Ragic, and that I can also do this within Ragic with Manually pressed buttons ( and I guess combined buttons) but a user has to press them and they may forget to do so.
I have tried PAD ( power automate desktop) and this can open a Ragic page and ‘press’ multiple action buttons automatically, but was hoping for an internal solution to updating these tables within Ragic itself without needing to use external tools.
I can see that Ragic’s API/Java Post workflow can accomplish this in code but would prefer the versatility of Ragic - with custom action buttons that can ‘fire’ on certain conditions ( when field …) or simply when record is updated or saved.
This is Kate from Ragic Support. You’re right—the Convert Records action doesn’t currently support automatic execution on record creation or save. At this time, the best way to achieve that kind of automation is through our JavaScript workflow engine, which allows you to programmatically trigger conversions and other logic based on your own conditions.
For email automation, Custom Emails can be configured to send automatically when a record is saved. You can refer to this section on setting up auto-send for more details.
We understand the convenience of having more actions that can trigger automatically. While this particular feature isn’t available at the moment, using JavaScript workflows is a flexible option that many users rely on for automating more complex scenarios.
Thanks for sharing your use case, and feel free to reach out to us at support@ragic.com if you run into questions setting up JavaScript.
Thanks Kate - I know its achievable in Javascript but as stated the action button method is better and more easily changed by ‘sysadmin Ragic users’ rather than IT having to hard code…
As the feature is clearly been done in the ‘Update on another sheet’ custom button, would it be possible to request this same code to be added to Convert and Update custom buttons, which should benefit from this functionality and avoid the need for Java?
Jeff’s question answer (15/7)was that the ‘When’ part of functionality could be gained by pre-filtering the source recordset and applying Convert or Update to that subset, but again its a poor workaround for functionality that should be within teh custom button, and which has been implemented in one but not the other two.
Would we have an answer as to if and when this could be a reality?
Ragic is great but could be much better with the custom action buttons being more customisable still with ‘Run on save’ and When this field matches that functionality.
We also tried the possibility of Java calling the creating the autogenerated button script function, but as this autogen id changes with saves, its impossible to predict what this number would be in order to be able to run it from a script, this then means custom javascript replacing action buttons entirely.
It can be done but instaed of a flexible construct easily created button we then have a very rigid javascript routine…
With Multiple buttons in a sheet, all doing different things its easy to modify their behaviour within the buttons themselves, and therefore the action buttons are great for prototyping but then have to be entirely transalated to java when protyping is complete…
All it needs is a 'Run when saved ’ option and a When Field =" function within both Update Custom button and Convert custom button as is the case with teh Update on another sheet custom button already ( see screeenshot above)
Thanks for the follow-up! Just to make sure we’re aligned—originally you mentioned interest in adding a “Run when saved” option for the Convert Records action. In your latest message, it sounds like you’re also requesting support for a “When field =” condition. Could you confirm if both are part of your current request?
Also, regarding the reference to Jeff’s comment on July 15th, we weren’t able to find a related discussion in that session. If it might have been from a different date, feel free to let us know so we can better understand the context.
All good, Rob—no worries, and thanks for the clarification!
Based on the June 17th session, it looks like your discussion with Jeff focused on the “When field =” condition. You can refer back to Jeff’s response here for the details.
As for your request regarding a “Run when saved” option for the Convert Records action, we’re reviewing this internally. Since this type of automation could create records in batch, there are several considerations—such as potential impacts on related records and possible performance risks. We’ll keep you posted as we continue to evaluate the feasibility.
Thanks again for sharing your ideas with us. After internal review, we don’t plan to add a “Run when saved” option to Convert Records as a built-in feature. The main concern is that while this setup can work well in the hands of experienced users like yourself, it could cause serious issues if less familiar users turned it on without fully understanding the impact. For example, automatic conversions on every save could quickly create large volumes of data, trigger loops between sheets, or make it difficult to undo mistakes. In the worst cases, these could affect not only the database itself but even overall server performance.
That’s why we believe this kind of automation is best handled through JavaScript workflows. With JavaScript, advanced users can design the exact logic they need, while keeping control of potential risks. This way, power users still have full flexibility, but we avoid exposing a risky option to everyone as a simple checkbox.
We really appreciate your thoughtful input—it’s clear you’re using Ragic at a very advanced level, and your feedback helps us keep improving while also protecting the broader user community.
For your reference, here’s a summary of the main reasons:
Performance risks: automatically creating new records on every save could quickly generate large amounts of data.
Looping risks: converting back into the same sheet could create infinite loops of record generation.
Hard to undo: unlike updating values, conversions create new records, which are harder to roll back.
Auto-action limit: each sheet can only have one action that runs automatically on save, so adding Convert would complicate that rule.
Thanks for looking at this and the internal review of the request.
I understand that a simple checkbox could cause issues and that less experienced users could enable this without undestanding the consequences, but there is a solution around this, for example the option could first need to be switched on in the Company/Feature Settings part which would and only then allow the run when saved option.
I dont think loops between sheets is likely unless two sheets each had a convert set on each other, something that could easily be prevented by not allowing a convert to a sheet which already has a convert set to it.
Unoing a mistake created by a convert or update is surely the same as one done via java- in teh latter its even more difficult to do.
We have developed the system using convert butons that dont run on save -this allows us to manually press and test convert and update actions ie simulates the expected behaviour of Java so that we can fine tune it, before creating the Java version.
This makes it easier to hand over to our Java Programmer as we can include all fields and expected behaviour and actual results of data within the sheet.
Java does work, but its a LOT more painful to use, more expensive and sometimes painful to debug when expected behavoiour is different from the simple ‘Convert to another sheet’ action button.
Similarly for emails which to run on save also need converting to Java and testing.
Thanks for the detailed follow-up and for outlining how you’re using Convert buttons as a way to prototype before moving to Java — the context is helpful. We also see your point about safeguards like enabling such a feature only in Company Settings.
That said, after internal discussion we believe the best way forward is to handle this as part of our broader enhancement plan for running combined action buttons on save. This approach would allow you to include Convert (or other actions) within a combined button and have it run automatically, while also keeping the feature consistent and safe across different scenarios.
We’ve added you to the notification list, and we’ll update here once there’s progress. We appreciate you continuing to share how you’re working with these features — it helps us shape the roadmap while making sure changes work well for the whole community.
