Fields: - From Subscription (Product select) - To Subscription (Product select)

We can currently set certain rules to, for example, 'Subscription Payment Count' is 5. Allowing formulas, this could be set to 'Subscription Payment Count' is '(x*3)+1'. This would only trigger when that formula has been met. (not exactly how this may be used) Just overall allowing formulas would give a lot more freedom in how rules can be used.

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 :)

I think it'd be useful to provide a high level option to that users that would prevent all their workflows from running at certain times. I realize you can deactivate workflows on an individual level, but that'd be a pain if you have a lot of workflows. It'd also be a pain if it was something that was recurring, i.e. you needed to prevent a workflow from running every Friday or the last day of every month.

Supporting a membership note would be great. When we issue a membership to someone based on total spend, then it would be nice if a message automatically could appear inside the membership section of their customer account.

Similar to the 'Customer - Order Count' rule, this would be conditional to the customer having a set number of subscriptions, or less than, greater than, etc.

A workflow could be triggered from a webhook

If a customer owns Subscription A and purchases Subscription B, then cancel Subscription A.

Please see GitHub issue: https://github.com/Prospress/automatewoo-subscriptions/issues/3