Undo/Redo in Workflow not always working
Maybe this belongs in the Ideas topic, but posting here in case I am missing something that I should have.
I see mixed behavior when I try to undo an action in Workflow designer.
For examples,
- I drop an activity and undo it with button or Ctrl+Z. It stalls for a few seconds and then the activity goes away.
- If I delete an activity, Ctrl+Z does nothing, but the button works.
- In the Workflow Form designer, I see no undo capability except for within text boxes of form elements, assuming I don't click out of it.
-
I don't share most of your behavior, usually. For example Ctrl+Z always runs the undo command for me (or at least attempts to), including undeleting activities.
I do get naughty undo/redo behavior sometimes, most consistently when I've had Designer open for a while (more likely when I've done a lot of things in Designer). Sometimes edit actions are missed, sometimes they are binned together, etc., and it takes longer and longer for updates to take effect.
That said, refreshing Designer usually works very well for me to fix the problem (with the exception of editing large forms), which is why I recommend refreshing the Designer daily anyway. I suspect the editing issue is related to a couple of corrupted WF files I've encountered in the past few years; the corruptions have only ever occurred at the end of a long day of many edits to large WFs.
On rare occasion, I've also seen difficulties in Designer with specific workflows where the un/re-do features become particularly erratic. On close inspection, these workflows always have what I call ghost activities (sPoOkY), which are activities that survive in the Workflow json but are basically inaccessible in the Designer. Usually I see a collection of these activities connected with each other but not the rest of the Workflow, which must cause parser issues for Designer.
These miscellaneous spirits are difficult (and not at all beginner-friendly) to remove and may cause your WFs to misbehave in Designer. The most consistent way I've been able generate this bug is to have a big complicated form with many event subworkflows, then delete an element with SWFs without deleting the SWFs first... sometimes the activities from the the SWF will hang around, connected to one another but not to the outside world, adrift somewhere between the living and the lost. Long-lived WFs which have seen a lot of changes can accrue a lot of this junk, and in my experience such WFs perform perfectly fine at execution but cause headaches in Designer.
The quickest way I've taken care of the issue is to make a new WF and copy-paste everything (Ctrl+A) to it, this doesn't always clear all the ghost activities but it usually at least fixes enough to make Designer happy. You can trade the tedium of updating to the new WF URL with the tedium of editing JSON manually if you prefer, where you will be able to for sure exorcise ghost activities for good but BE CAREFUL doing so. I use AGOL Assistant for that, but I've only done it twice and I'd avoid it when at all possible.
0
Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.
Kommentare
1 Kommentar