TMS:Task disabled fields
I'm pretty well stumped by this. We have a situation where intermittently users will open a task via link in a notification, but it opens with all fields disabled. This looks for all the world like the Default Admin View - Read Only view but I have determined that it isn't. What I did was I made a simple display form with a task I'd field a button and a view field. I made an active link that does an open window action on the specified task I'd in the view field. The active link specifies the Default Admin View and BOOM! It opens with all the fields disabled! I put an active link in to echo $VUI$ in an alert and it IS definitely in the default admin view. So I figured there must be an active link misfiring. So I DISABLED EVERY ACTIVE LINK ON TMS:Task ... And it STILL opens the default admin view with every field locked!! Flushed my cache and watched the active link log ... Nothing fires except my link to load the task! What the heck is locking these fields?! How can this even happen? More to the point I strongly suspect whatever is going on here is also the cause of my users intermittently opening tasks from notifications with all locked fields. Anyone out there run into this before? For what it's worth the exact same thing happens on my 764 test box as my 81sp2 box. - Andy ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Where the Answers Are, and have been for 20 years
Re: TMS:Task disabled fields
We are seeing this too (8.0). One case where this has been a long-term issue for a particular user was just escalated to me late last week. I logged in with that account and opened a task that was reported as having the issue with no problem. I should be talking with him later today to see if we can get to the bottom of it. People are blaming it on his account but his account worked fine for me. I'll report back with what we find. Jason On Mon, Dec 9, 2013 at 10:24 AM, Andrew Hicox and...@hicox.com wrote: ** I'm pretty well stumped by this. We have a situation where intermittently users will open a task via link in a notification, but it opens with all fields disabled. This looks for all the world like the Default Admin View - Read Only view but I have determined that it isn't. What I did was I made a simple display form with a task I'd field a button and a view field. I made an active link that does an open window action on the specified task I'd in the view field. The active link specifies the Default Admin View and BOOM! It opens with all the fields disabled! I put an active link in to echo $VUI$ in an alert and it IS definitely in the default admin view. So I figured there must be an active link misfiring. So I DISABLED EVERY ACTIVE LINK ON TMS:Task ... And it STILL opens the default admin view with every field locked!! Flushed my cache and watched the active link log ... Nothing fires except my link to load the task! What the heck is locking these fields?! How can this even happen? More to the point I strongly suspect whatever is going on here is also the cause of my users intermittently opening tasks from notifications with all locked fields. Anyone out there run into this before? For what it's worth the exact same thing happens on my 764 test box as my 81sp2 box. - Andy _ARSlist: Where the Answers Are and have been for 20 years_ ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Where the Answers Are, and have been for 20 years
Re: TMS:Task disabled fields
I discovered a few things poking at this a little further ...
1) every visible field in the interface is locked. If you create an overlay
and add a completely new field with public write permissions in read/write
display mode, it gets locked on display as well ! Even with every single
active link on TMS:Task disabled (and watching the log to be sure)
2) this isn't a midtier or CSS bug, because if you load it up in windows
aruser it happens there too! (Ya rly)
Either I'm missing something incredibly obvious (hoping someone here will
point that out actually) or this bug goes deeper than the mind of Minolta.
Andy
On Monday, December 9, 2013, Jason Miller wrote:
**
We are seeing this too (8.0). One case where this has been a long-term
issue for a particular user was just escalated to me late last week. I
logged in with that account and opened a task that was reported as having
the issue with no problem. I should be talking with him later today to see
if we can get to the bottom of it. People are blaming it on his account
but his account worked fine for me. I'll report back with what we find.
Jason
On Mon, Dec 9, 2013 at 10:24 AM, Andrew Hicox
and...@hicox.comjavascript:_e({}, 'cvml', 'and...@hicox.com');
wrote:
** I'm pretty well stumped by this.
We have a situation where intermittently users will open a task via link
in a notification, but it opens with all fields disabled.
This looks for all the world like the Default Admin View - Read Only
view but I have determined that it isn't.
What I did was I made a simple display form with a task I'd field a
button and a view field. I made an active link that does an open window
action on the specified task I'd in the view field. The active link
specifies the Default Admin View and BOOM! It opens with all the fields
disabled!
I put an active link in to echo $VUI$ in an alert and it IS definitely in
the default admin view. So I figured there must be an active link
misfiring. So I DISABLED EVERY ACTIVE LINK ON TMS:Task ... And it STILL
opens the default admin view with every field locked!!
Flushed my cache and watched the active link log ... Nothing fires except
my link to load the task!
What the heck is locking these fields?! How can this even happen? More to
the point I strongly suspect whatever is going on here is also the cause of
my users intermittently opening tasks from notifications with all locked
fields.
Anyone out there run into this before? For what it's worth the exact same
thing happens on my 764 test box as my 81sp2 box.
- Andy
_ARSlist: Where the Answers Are and have been for 20 years_
_ARSlist: Where the Answers Are and have been for 20 years_
___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Where the Answers Are, and have been for 20 years
Re: TMS:Task disabled fields
Andrew, The workflow that is opening this form...is it opening it in 'Display' mode?...Display mode, by definition is every field read only On Mon, Dec 9, 2013 at 2:57 PM, Andrew Hicox and...@hicox.com wrote: ** I discovered a few things poking at this a little further ... 1) every visible field in the interface is locked. If you create an overlay and add a completely new field with public write permissions in read/write display mode, it gets locked on display as well ! Even with every single active link on TMS:Task disabled (and watching the log to be sure) 2) this isn't a midtier or CSS bug, because if you load it up in windows aruser it happens there too! (Ya rly) Either I'm missing something incredibly obvious (hoping someone here will point that out actually) or this bug goes deeper than the mind of Minolta. Andy On Monday, December 9, 2013, Jason Miller wrote: ** We are seeing this too (8.0). One case where this has been a long-term issue for a particular user was just escalated to me late last week. I logged in with that account and opened a task that was reported as having the issue with no problem. I should be talking with him later today to see if we can get to the bottom of it. People are blaming it on his account but his account worked fine for me. I'll report back with what we find. Jason On Mon, Dec 9, 2013 at 10:24 AM, Andrew Hicox and...@hicox.com wrote: ** I'm pretty well stumped by this. We have a situation where intermittently users will open a task via link in a notification, but it opens with all fields disabled. This looks for all the world like the Default Admin View - Read Only view but I have determined that it isn't. What I did was I made a simple display form with a task I'd field a button and a view field. I made an active link that does an open window action on the specified task I'd in the view field. The active link specifies the Default Admin View and BOOM! It opens with all the fields disabled! I put an active link in to echo $VUI$ in an alert and it IS definitely in the default admin view. So I figured there must be an active link misfiring. So I DISABLED EVERY ACTIVE LINK ON TMS:Task ... And it STILL opens the default admin view with every field locked!! Flushed my cache and watched the active link log ... Nothing fires except my link to load the task! What the heck is locking these fields?! How can this even happen? More to the point I strongly suspect whatever is going on here is also the cause of my users intermittently opening tasks from notifications with all locked fields. Anyone out there run into this before? For what it's worth the exact same thing happens on my 764 test box as my 81sp2 box. - Andy _ARSlist: Where the Answers Are and have been for 20 years_ _ARSlist: Where the Answers Are and have been for 20 years_ _ARSlist: Where the Answers Are and have been for 20 years_ ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Where the Answers Are, and have been for 20 years
Re: TMS:Task disabled fields
And there it is. Lol
I knew it must have been something obvious and it was :)
Thanks!
Andy
On Monday, December 9, 2013, LJ LongWing wrote:
**
Andrew,
The workflow that is opening this form...is it opening it in 'Display'
mode?...Display mode, by definition is every field read only
On Mon, Dec 9, 2013 at 2:57 PM, Andrew Hicox
and...@hicox.comjavascript:_e({}, 'cvml', 'and...@hicox.com');
wrote:
**
I discovered a few things poking at this a little further ...
1) every visible field in the interface is locked. If you create an
overlay and add a completely new field with public write permissions in
read/write display mode, it gets locked on display as well ! Even with
every single active link on TMS:Task disabled (and watching the log to be
sure)
2) this isn't a midtier or CSS bug, because if you load it up in windows
aruser it happens there too! (Ya rly)
Either I'm missing something incredibly obvious (hoping someone here will
point that out actually) or this bug goes deeper than the mind of Minolta.
Andy
On Monday, December 9, 2013, Jason Miller wrote:
**
We are seeing this too (8.0). One case where this has been a long-term
issue for a particular user was just escalated to me late last week. I
logged in with that account and opened a task that was reported as having
the issue with no problem. I should be talking with him later today to see
if we can get to the bottom of it. People are blaming it on his account
but his account worked fine for me. I'll report back with what we find.
Jason
On Mon, Dec 9, 2013 at 10:24 AM, Andrew Hicox and...@hicox.com wrote:
** I'm pretty well stumped by this.
We have a situation where intermittently users will open a task via
link in a notification, but it opens with all fields disabled.
This looks for all the world like the Default Admin View - Read Only
view but I have determined that it isn't.
What I did was I made a simple display form with a task I'd field a
button and a view field. I made an active link that does an open window
action on the specified task I'd in the view field. The active link
specifies the Default Admin View and BOOM! It opens with all the fields
disabled!
I put an active link in to echo $VUI$ in an alert and it IS definitely
in the default admin view. So I figured there must be an active link
misfiring. So I DISABLED EVERY ACTIVE LINK ON TMS:Task ... And it STILL
opens the default admin view with every field locked!!
Flushed my cache and watched the active link log ... Nothing fires
except my link to load the task!
What the heck is locking these fields?! How can this even happen? More
to the point I strongly suspect whatever is going on here is also the cause
of my users intermittently opening tasks from notifications with all locked
fields.
Anyone out there run into this before? For what it's worth the exact
same thing happens on my 764 test box as my 81sp2 box.
- Andy
_ARSlist: Where the Answers Are and have been for 20 years_
_ARSlist: Where the Answers Are and have been for 20 years_
_ARSlist: Where the Answers Are and have been for 20 years_
_ARSlist: Where the Answers Are and have been for 20 years_
___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Where the Answers Are, and have been for 20 years
