I think he means so that the status dropdown would only contain statuses that make sense for the current status of the workflow and the current user modifying the record. That would be pretty cool, but you'd have to have maintain a table with /current-status/valid-status/role for every possible valid combination?

Brien

On 3/25/2010 2:24 PM, John Sundberg wrote:
Not sure what you mean.

-John


On Mar 25, 2010, at 1:21 PM, Guillaume Rheault wrote:

Potentially to validate status transitions based on group or role...
Or to only display the valid status transitions to the end user

Guillaume

________________________________________
From: Action Request System discussion list(ARSList) [[email protected]] on behalf of John Sundberg [[email protected]]
Sent: Thursday, March 25, 2010 1:41 PM
To: [email protected]
Subject: General design question regarding H tables

What would be the purpose of having a seperate table to hold the
status values and not just have it in the orig table?

-John


Sent from my iPhone

_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
attend wwrug10 www.wwrug.com ARSlist: "Where the Answers Are"

_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
attend wwrug10 www.wwrug.com ARSlist: "Where the Answers Are"

--
John Sundberg

Kinetic Data, Inc.
"Building a Better Service Experience"
Recipient of the WWRUG09 Innovator of the Year Award

[email protected]
651.556.0930  I  www.kineticdata.com

_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
attend wwrug10 www.wwrug.com ARSlist: "Where the Answers Are"


_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
attend wwrug10 www.wwrug.com ARSlist: "Where the Answers Are"

Reply via email to