I second Gary as I ahve actually done such things in the past and had the functionality work pretty good.. Joe
----- Original Message ---- From: Gary Opela (Corporate) <[EMAIL PROTECTED]> To: arslist@ARSLIST.ORG Sent: Wednesday, May 14, 2008 3:54:53 PM Subject: Re: Field Meta Properties? ** You can simulate TR/DB functionality in active links by looking at the value in the database and comparing it to the current value. Set tmpStatus = (lookup status from DB where Request ID = Request ID) If tmpStatus != Status, then fire. This requires an extra field and one extra active link. You could get away with using the same tmp field for all of your workflow if you want to keep the number of objects down. This is important if you have users that open many many windows at once. I highly doubt they will ever add this as an RFE. You can try though JI’ve got stuff from several years ago out three still! Thanks, Gary Opela, Jr., RSP Remedy Engineer Leader Communications, Inc. http://www.5pointleader.com http://www.lcibest.com Best Product, Best People, Best PriceTM An ISO 9001:2000 Certified, CMMI® Level 3 Rated Company ________________________________ From:Action Request System discussion list(ARSList) [mailto: arslist@ARSLIST.ORG ] On Behalf Of Rick Cook Sent: Wednesday, May 14, 2008 2:22 PM To: arslist@ARSLIST.ORG Subject: Re: Field Meta Properties? ** Misi, as best I understand it, the TR/DB functionality only exists in Server-based workflow due to the client/server traffic involved in making it functional (retrieving DB info and processing it in phase, etc.) on client-based Active Links. There's almost certainly a better answer than that, but that one makes enough sense to me. Rick On Wed, May 14, 2008 at 12:08 PM, Misi Mladoniczky <[EMAIL PROTECTED]> wrote: Hi, The TR/DB-functionality allways does it. The problem is that the syntax is, for some very obscure reason, not available in Active Links. ('Status' != 'DB.Status') is the exact same thing as ('Status'.changed = 1) would be. I see no point in changing the syntax, but it would be nice to use it in Active Links. The Hidden/Visible stuff is less useful. It can allways be tracked with a display-only-flag. It does no great harm to do one extra Hide or Show... Best Regards - Misi, RRR AB , http://rrr.se > I'm going to put this in as an RFE - I highly expect to get shot down > even though it would save a LOT of coding work at times. > > First though I thought I'd ask for input and criticism of the idea. > > Frequently I want workflow to fire on dependencies like a field being > visible/hidden or a field value having been changed. TR/DB value > comparisons frequently do not do it depending on what I'm trying to > accomplish. > > What I'd really like to be able to do at least in Active Links is a "Run > IF" that went something like: > > 'Status'.changed=1 > > or > > 'Myfield".visible=0 > > Just about every GUI coding platform I've seen has things like this. > > I'm also going to put in an RFE for improved logging for things like > Dialog Open/Close field mappings, etc. > > Crazy requests? What say you? > > William Rentfrow, Principal Consultant > [EMAIL PROTECTED] > C 701-306-6157 > O 952-432-0227 > > > _______________________________________________________________________________ > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org > Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" > > -- > This message was scanned by ESVA and is believed to be clean. > > _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" __Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" html___ __Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" html___ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
