Hi Mavis, We also faced this problem - what I ended up doing is created
calculated fields with the if then else logic in them returning cleanup
text if there was a problem. eg: CDQ1: IF(LEN(Commentary Exec
Summary)<=10,'Commentary must be longer than 10 characters','') I found
it useful also to have a calculated field that showed the number of
tests that failed as well so that in the report below I can quickly
filter to the rows to show. And then I created a report that
concatenates all the comm...
Hi, What you can do while waiting for the patch is on the views that are
shared set conditional formatting to turn it bold if % complete greater
than 0% which then makes it readable. If you are sharing your views on
layout templates then can roll this out quickly to your user group.
I am currently unable to grant permission for review users to be able to
view expenses and legacy resource estimates that have been added to a
project. I appreciate that a review user should not be able to edit
these - but they should be able to view them rather than just seeing a
Couldn't agree more - we really need to be able to do this by group in
the same way as status is managed as we have separate groups operating
on the instance who all have slightly different needs. Understand that
we would still need to say what each new condition is equivalent to so
that we Workfront knows how to handle them. Have raised an idea for this
so that it is captured:
Hopefully this is on the roadmap already and imminent...
The changes you have made to allow us to globally change the condition
names away from "At risk" / "In Trouble" are great but need to be able
to define these by group in the same way that statuses are defined so
that different groups can control what conditions they are using (eg
Red, Yellow, Green or Late, At risk, On track).
When a user accidentally uses a corrupt view / grouping (eg we can't rid
of legacy gantt off the subtasks view list) they get presented with a
"oops contact workfriont to sort this out" error message. Help desk
inform us the only way to clear this is to do a /resetUser for a
particular user. The problem with this is that it gets rid of custom
tabs / forgets the defaults for a user on all objects. Ideally you would
be able to specify just the object you wanted to reset (eg Task or
Optask) - eithe...
We have quite a few fields classifying the job roles into a hierarchy
(identifying skills / business area etc) and currently have to maintain
data about the roles in our data warehouse. If we were able to attach
custom forms to job roles then we would be able to add these fields
which could then be used in reporting in the tool.
Agree completely - just need an isactive flag on the role that would
prevent it appearing when users were selecting a role going forwards -
would prevent having to rename them xxArchive.... and then do a check
outside to make sure people are using the right job roles
When creating a single line text custom field I want the ability to say
that the value should be unique and WF flag up an error if a duplicate
value (ie one already in the system for my instance) is entered.
Probably would have to add to the "copy to" dialog boxes so that user
could fix when duplicating. Would save having to do all the uniqueness
tests outside using API and reporting