A manual workflow is defined as a workflow that has no trigger and is instead manually started by a store manager. Existing workflows would be considered 'automatic' workflows in comparison.
A manual workflow would need a primary data type (e.g. order, customer, subscription) which would define which rules, actions and variables could be used in the workflow.
A manual workflow could be started from a related admin page. E.g. an order manual workflow could be initiated from the edit order page. Alternatively, manual workflows could be started from a custom interface that allows selecting a set of items to be triggered. It would be useful to select items by a date range and select multiple items by ID.
This system would be a replacement for the manual order and subscription trigger tools.
If you have any use cases for manual workflows please add them as a comment :)
We've built a custom 'reminder' trigger, which sends an email every week to customers without an active subscription, reminding them to place an order.
We also use it to send ad-hoc emails to customers when new products are launched (replaced mailchimp).
Our implementation is somewhat of a hack (happy to share the code though), so it'd be awesome to see this implemented as an official feature!
excited that this is planned
i look through the idea board and every time i see your ideas i LOVE them
this would be an AMAZING addition......
this can be used for many cases. example when I want to bulk change ALL subscription prices (only based on certain products)
(triggers are limited and pre-loading all customer, subscription data and applying rules and then actions to them would be amazing)
i can probably think of many cases
Another use case:
Manually target all customers that have an active subscription with a specific product when there's an update to the product. This would be perfect to send out notifications about software updates or when there's new additional content for a digital product subscription.