Barry McBride

I'm able to assign articles to editors, no problem. THe issue is there's no way in the workflow system to "unassign" them.

Environment: Invision Community 5.0.19 (Cloud). Pages database "Articles" (database_id 1), Cloud Workflows enabled. Related design discussion in my earlier topic 487566 (Article Approval Flow?). Two separate issues, both in Cloud Workflows on a Pages database. ISSUE 1: an assignment created by the "Assign Item" action can never be closed, is invisible in the UI, but keeps generating reminder emails. Our "Submit for Editing" workflow had three actions: Assign Item to Team: Editors, Notify Members, and Custom Field value (Status to Submitted). Every article submitted through it opened an assignment against the Editors team that nothing can ever close. There is no way to close it by configuration: 1. The complete list of action types is Assign Item, Post a comment, Item Status, Notify Author, Notify Members, Custom Field value. None of them closes or clears an assignment. 2. The Assign Item target picker accepts only a member or a team. There is no "none" option, so a later workflow cannot clear it. 3. Completing the workflow does not close it. Our "Approve and Publish" workflow sets Status to Approved and notifies the author, and the assignment survives. And it cannot be cleared by hand, because it is invisible: 1. ModCP > Assignments shows "There's nothing here yet" on all four filters: All Active, My Assignments, Replied, and No longer assigned. 2. The Site Moderation counter reads "0 Open Assignments". 3. The header flyout reads "You have no open assignments." 4. Because no rows render, the Unassign bulk action cannot reach them. Meanwhile the reminder task still counts them and emails me. On our site: 1. On-site notifications reading "N open assignments are waiting for a reply": 3 on Aug 4 at 5:51 AM ET, 3 on Aug 6 at 10:50 AM, and 2 on Aug 8 at 11:23 AM. Every one of them links to /modcp/assignments/?filter=assign_mine, which renders empty. 2. The Aug 8 "Open Assignments" email named Articles records 18 and 19, both of which had already completed the workflow and published to a public category on Aug 2 and Aug 3. 3. Moderation history for record 18: "Ran workflow Submit for Editing" (Aug 2, 3:30 PM), then "Ran workflow Approve and Publish" (Aug 2, 3:31 PM), then "Moved a Article" (Aug 6, 10:56 AM). No assignment close event anywhere. The workflow finished six days before the reminder that named it. One partial workaround: editing the record as the assignee appears to clear the row. Record 17 was edited by the assignee on Aug 6 at 10:55 AM and dropped out of the count (3 to 2), while record 18, which was only moved one minute later, stayed counted. That is inference from the counts, since no UI ever exposes the rows. What I did as a workaround: I deleted the Assign Item action from "Submit for Editing" so that no new assignments accumulate. The review queue was already covered by the Notify Members action on the same button and a saved Editors view on Status = Submitted, so nothing functional was lost. Expected: completing a workflow should close the assignment it opened. Failing that, please add an unassign or complete-assignment action type, or allow Assign Item with an empty target. Separately, the reminder count and the ModCP list should agree, and anything the reminder counts should render somewhere an admin can clear it. ISSUE 2: the Add Action wizard saves a half-configured action when you click Continue. In ?app=cloud&module=workflow&controller=workflows&database_id=1&id=N&do=addAction, selecting a type and clicking Continue writes the action row immediately, before you have configured it or clicked Save. Abandoning the wizard at that point leaves a live action in the workflow. I reproduced this deliberately. On my Approve and Publish workflow, an interrupted wizard left an Assign Item row described as "Assign Item to" with a blank target. Running the wizard again to the same point created a second one (action IDs 29 and 30). Both then ran as part of the workflow. Expected: do not persist the action until Save, or reject an Assign Item with no target during validation. Requests: 1. Close assignments on workflow completion, or provide some way to clear one. 2. Make ModCP > Assignments render the rows that the reminder task counts. 3. Do not persist wizard actions until Save. 4. Please check my client for orphaned assignment rows against Articles records 18 and 19, and delete any that remain. I cannot see or reach them from the ACP.

Right. We can move categories in the AdminCP, but I really want to keep editors away from that. Having that be part of the workflow would really clean things up. Depending on timing, I may have to go with the "hidden" solution until then.

Thanks, Matt. Maybe our solution here will be reusable for other news-oriented sites that need this workflow.

Still working on this. Since the Articles database doesn't have a single "approve" step that makes an article "live" to the public, I'm considering building it around categories. A "Draft" category for writers that's hidden from the public, which editors can move to the "Published" category and then everyone can view. Another option is to build a workflow that starts with an article "hidden" and then unhides it when approved, but there's no way to default a new article to "hidden" that I can see.

Simply create a system where staff writers (a custom group) can draft an article, submit it to a team of editors, who then can edit, approve, and/or return it to the writer as needing additional work. Normal members and subscribers cannot have access to this, only staff writers and editors.

We have a number of writers and some editors who need to proofread their work before it's published. The workflow capability looks perfect for this, and it's a pretty common scenario, so I figured I would ask if anyone had designed this for their sites before trying to create it from scratch. If there are any recommendations out there, please let me know!

@Jim M Have you heard any more about this? I'd love to use the test environment rather than the workaround of fake checks, etc.

This is awesome. Can't wait!

OK, that clears it up. I guess I can use manual payment methods and just mark them as accepted.

That was it!! I used the live keys and the associated webhook, and it worked. Is there some sort of workaround to get things working in test mode so I can test all the subscription options without charging my card? Barry

It's all USD, and I'm based in the US, using a US billing address. I've checked it a couple of times, and that shouldn't be the issue. Thanks for your help. I'm probably missing something obvious. This is also specifically for Subscription Plans, not subscriptions sold as a Product type. I also tried a Product in the Store with the price of $1 and got the same result.

Hi Jim! Thanks fo the quick reply. I have those as "source.chargeable, charge.succeeded, charge.failed, charge.dispute.created and charge.dispute.closed", and they're all set up in the webhook destination.

Been banging my head against this all afternoon. I have configured a Stripe sandbox account, entered the sk/pk_test API keys, configured Stripe repeatedly, and I continue to get this error message when testing from a variety of accounts. The stripe logs show that nothing is making it through. I've removed all restrictions I could find on member type, renewals, etc. The Payment Method is "Enabled" per Invision. The webhook is the only one that Stripe suggests. Am I missing something obvious?

Brilliant! Thanks for pointing me to the right spot!