wundermatics

Hi @jeff-is and @opicron,

First, we’re sorry that this update has caused issues.

The 1.6 version updates to a new internal representation for how filters/actions are stored. From what you describe it sounds like that process hasn’t worked out as it should.

I’d like to see a screenshot of what your respective workflows look like in the editor right now, perhaps with a focus on the filters and actions.

If you’re comfortable sharing here, that’s fine. If not please reach out via the support page here: https://www.wundermatics.com/support/contact/

Hi @tdrv,

Terribly sorry about not replying sooner. We strive to do our best and reply quick but we’ve simply had too much on our plates lately.

I’ll make sure you get a reply during the day today.

Hi @moolahdigital,

Thanks for letting us know. WunderAutomation has a lot of broad and generic functionality and while we try to cover each imaginable use case we can’t cover everything. Getting feedback like yours is the best way to guide us forward, so we really mean it, thanks.

WunderAutomation already has support for “plucking” individual elements from a data structure, described in some detail here:
https://www.wundermatics.com/2020/12/26/advanced-webhook-usage-with-wunderautomation-and-jsonpath/

But as you have noticed, we never implemented this for Advanced Custom Fields (or standard custom fields either). So before we go and add this functionality to ACF custom fields it would be a great benefit to us if you could confirm that it’s likely to solve your use case.

Looking forward to hearing back from you

Hi @shalarmd,

Looks like you’ve found a bug here. The confirmation link feature was built for a specific use case with a paying client and probably hasn’t got that much testing milage on it.

The good news is that we’re putting in the last piece of QA work for version 1.6 as we speak. I’ll make sure we add a test case for the issue you describe. The new version should be available on March 1st.

Thanks for bringing this to our attention

Hi @tdrv,

Sorry for not replying sooner.

I’d need to get some more details about your case to be able to help you better. Would you mind asking the same question over at https://www.wundermatics.com/support/contact/

When you do please include a screnshot of the workflow configuration, that usually helps a lot to understand what your workflow is meant to do.

Cheers!

Hi Sotnas,

It’s not possible in the current version, but it’s a very interesting idea, and probably quite easy to add. Thanks for a cool idea!

I’m thinking that what we’d do is to add a new filter that just looks at the current time and decides if the workflow should continue or not. Not a huge deal.

Just to set the expectations right. At the moment we’re busy doing the last testing work for version 1.6 that brings some UI improvements, that should be out the door before end of February.

But a filter like you suggest should absolutely make it into the next release after that. If I have to guess I think that would be around mid March.

Cheers!
/Erik

Hey,

Thanks for letting us know what you had in mind, very helpful for planning upcoming features.

Terribly sorry we can’t be of any help for your current project. We’ll go back and update this thread when we have shipped that feature, but that’s probably a few months away.

Hi,

At the moment no but it’s something that a few people have asked for so we’re looking into how we could add this.

Are you interested in adding files from the WordPress media library or are you thinking about files on the server file system?

Hi,

Sorry for not replying sooner. Provided I understand you correctly:

To use the contents of a comment in an action (like sending an email) you can use the {{ comment.content }} parameter.

If I didn’t understand what you mean by “attach comment content as a trigger”, please clarify so that we can help you out.

Thanks,

/Erik

Hi,

At the moment the WooCommerce order object really only exposes the “most obvious” parameters such as order total, date and customer details. We are working on being able to expose more detailed data. But that adds a bit of complexity and we want to make sure we get it at least somewhat right. Short answer, we haven’t got that far yet.

But your use case sounds really interesting, understanding your needs may lead us in the right direction in terms of “getting it right”. If you’re up for sharing we’d be very happy if you want tell us more about it, send us an email at [email protected].

For an example of how to use the request body field in a REST API Call action, have a look at this blog post:
https://www.wundermatics.com/2020/05/21/zapier-and-wunderautomation/

Hi,

Very sorry for the late reply. In short, no. At the moment this plugin is only able to deal with calculations based on fields in the same field group on the same post.

We are looking for ways to expand the functionality to span multiple posts but that’s something for a future release and we can’t really tell if and when.

Sorry.

Hi Loftchaman,

Any more help needed after @nick6352683 suggestion?

Hi Polarracing,

Would you mind open a support ticket over at https://www.wundermatics.com/support/contact/ and include your field group definition?

Hi Dave,

Could you open a support thread over at https://www.wundermatics.com/support/contact/ where you can attach your code and field group definition?

Hi Nexus,

Is the behaviour on the backend or the frontend? If it’s the frontend, how do you render the fields?

Regarding the range field we need to look in to it. The range field probably stores it’s value slightly differently compared to a normal numeric field and if so needs special treatment.