I am trying to edit/change the values in the picklists/status reason
attrubutes values in the Appointment, Case Resolution, E-Mail, Activity, and
Task entities, however all values in the state/reason value fields are greyed
out. Is there any reason why these are blocked from being customised. I have
Administrator plus all roles priveleges, so role security should not be an
issue, unless there is some conflict happening in this situation(defect). Has
anyone encountered this issue, and is there a workaround?

RE: Picklist and Status values Greyed out by jp

jp
Sat Apr 08 03:47:01 CDT 2006

This picklist can be changed in the 'service activitie' entity. I am not sure
why... all I can figure is that this is where the actual attribute originates
and it is has a one to many relationship. I am still digging in here and
trying to figure it all out.

Just remember to change the state drop down to get to the other states...
that kicked my butt for longer then I care to mention. Also, so far as I can
tell, there are NO views you can modify that show anything other then the
state of the status reason field... you will not be able to edit a view and
see the modified status reasons, only open, closed, cancelled and scheduled.
You will need an advanced find for that.

Hope that helps.

RE: Picklist and Status values Greyed out by GrahamSmith

GrahamSmith
Mon Apr 10 08:04:02 CDT 2006

These Entities all have some kind of a parent - child associated relationship
of Activity (Appointment,E-Mail, Task,) Dont know about Case Resolution.
Somehow there must be differences in logic between R1.2 and R3,0. State and
State reason are populated with default values during setup(probably from
1.2). I suspect that some of the rows for these entities (greyed out) are
never accessed in 3.0.

It would be nice to know why the valuse are greyed out.

"jp" wrote:

> This picklist can be changed in the 'service activitie' entity. I am not sure
> why... all I can figure is that this is where the actual attribute originates
> and it is has a one to many relationship. I am still digging in here and
> trying to figure it all out.
>
> Just remember to change the state drop down to get to the other states...
> that kicked my butt for longer then I care to mention. Also, so far as I can
> tell, there are NO views you can modify that show anything other then the
> state of the status reason field... you will not be able to edit a view and
> see the modified status reasons, only open, closed, cancelled and scheduled.
> You will need an advanced find for that.
>
> Hope that helps.

RE: Picklist and Status values Greyed out by Nora

Nora
Thu May 11 17:07:03 CDT 2006

I was unable to change the status for a 'Phone Call' activity. I was hoping
to change the status when I close the Phone Call to 'Completed' instead of
'Sent' like the product does. But, no such luck.

Nora

"Graham Smith" wrote:

> These Entities all have some kind of a parent - child associated relationship
> of Activity (Appointment,E-Mail, Task,) Dont know about Case Resolution.
> Somehow there must be differences in logic between R1.2 and R3,0. State and
> State reason are populated with default values during setup(probably from
> 1.2). I suspect that some of the rows for these entities (greyed out) are
> never accessed in 3.0.
>
> It would be nice to know why the valuse are greyed out.
>
> "jp" wrote:
>
> > This picklist can be changed in the 'service activitie' entity. I am not sure
> > why... all I can figure is that this is where the actual attribute originates
> > and it is has a one to many relationship. I am still digging in here and
> > trying to figure it all out.
> >
> > Just remember to change the state drop down to get to the other states...
> > that kicked my butt for longer then I care to mention. Also, so far as I can
> > tell, there are NO views you can modify that show anything other then the
> > state of the status reason field... you will not be able to edit a view and
> > see the modified status reasons, only open, closed, cancelled and scheduled.
> > You will need an advanced find for that.
> >
> > Hope that helps.