This topic came up in the Grow Track Experience Makers event today
during the Q&A session of the "Calculated Fields Everyone Should Know
(and How to Report in Them!)" segment with Anthony Imgrund. The request
was to change the path of a submitted issue within a request queue. As
you can see it is "Not Planned" with only 590 points, however it got
some buzz during that Q&A so maybe we need to make a little noise to
bring it back up as an idea...?...
I may not be asking the question right, however what I'm trying to find
out is if I can remove a version of the proof (not delete it) with all
it's comments and decisions and make it its own proof... like version 1
of a new proof. Here's what happened.... We had 4 versions of a proof
that was ready to be approved, but then we were told to go in a
different direction with the offer... so version 5 was created and
marked up. After further consideration, it was decided to go back to the
There have been some changes to ProofHQ since this initial idea was
submitted over 4 years ago, however it is still relevant today. We just
started using the proofing tool within WF and being the system admin., I
have access to the proofing dashboard. It is a really nice feature,
however it is by default that only available to admin users unless you
submit a ticket to support to enable it for in your global options
(which will allow worker access level or higher users to see it). This
I like this summary option on the task, however, the "description" field
that appears in the summary on the Home page does not always match the
summary that appears within the project. Sometimes I see the description
and sometimes I don't. Is there a known glitch?
Thanks Kevin... I relayed your response to my user so she went to upload
her docs again, and voila... no issues. I guess she happened to try to
upload her docs at the exact moment one of those "every so often"
glitches was occurring... what luck, eh. Anyhow, we're good and she will
refresh/close/reopen WF window if she ever comes across that error
again, but I'll still keep my fingers crossed that it won't. 😏
Has this mystery been solved? One of our users got the same error today.
I've asked her to tell me what she was doing when it occurred and if she
would be able to replicate it (I'm just waiting for her to respond;
probably Monday). Anyhow, if there is any insight, I would love to get
it. 🙂 Thanks in advance!