Re: Field Meta Properties?
Hi,
No DB/Server-traffic is needed. All fields are retrieved when the ticket
is shown. All that needs to be done, is to keep a data-copy of changed
fields in the client memory.
It would not be a true DB-value, but I do not think that it matters. What
you typically want to do is to check for changes that the specific user
has done. The user will in any case get a warning on save if the record
has been updated since retrieval.
What would be nice, both in ACTL and FLTR, would be to be able to use the
DB/TR syntax in Set-Fields Actions. Both in a search qualification and in
values for CURRENT TRANSACTION operation.
Best Regards - Misi, RRR AB, http://rrr.se
Products from RRR Scandinavia:
* RRR|License - Not enough Remedy licenses? Save money by optimizing.
* RRR|Log - Performance issues or elusive bugs? Analyze your Remedy logs.
* RRR|Translator - Manage and automate your language translations.
Find these products, and many free tools and utilities, at http://rrr.se.
> 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"
>>
>
> ___
> 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"
Re: Field Meta Properties?
True. It works. However, I have come to hate temp fields on principle. This is not rocket science - it's done in most major programming languages that are object based. Having these properties available is pretty simple stuff. Furthermore - there is DB activity going on that is superfluous. Doing a lookup to see if a value changed is not necessary if meta-properties were available. That said - these are all valid points. There are a lot of ways to accomplish these things - I just don't like that so many of them feel like workarounds. From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Joe DeSouza Sent: Wednesday, May 14, 2008 3:28 PM To: arslist@ARSLIST.ORG Subject: Re: Field Meta Properties? ** 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 :-) I'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.5pointleader.com/> http://www.lcibest.com <http://www.lcibest.com/> Best Product, Best People, Best PriceTM An ISO 9001:2000 Certified, CMMI(r) Level 3 Rated Company From: Action Request System discussion list(ARSList) [mailto: ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
Re: Field Meta Properties?
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"
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 :-)
I'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(r) Level 3 Rated Company
From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] 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___
___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
Re: Field Meta Properties?
Yep - that's very doable. But let's say you have a medium complex set of conditions that shows/hides fields based on a person's previous actions, the time of day, the time of issue, or any of 1000 other things. It would be so much nicer to have the meta property available for "Run if" to save workflow. It would also save the creation of creating a zillion temp fields at times. You really shouldn't have to create a field that is a flag indicating the state of another field (zTmpStatusChanged ring a bell to anyone?). From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Joe DeSouza Sent: Wednesday, May 14, 2008 2:20 PM To: arslist@ARSLIST.ORG Subject: Re: Field Meta Properties? ** Can't you just control the visibility of the field using an AL Guide and use that guide to do the rest of the stuff you want depending on its visibility status? Checking the change flag of a field at client level would be a nice to have feature though it is possible to do this via workflow too.. Go for it, they seem to be reasonable RFE's.. having these would make life a little more easier.. Joe - Original Message From: Rick Cook <[EMAIL PROTECTED]> To: arslist@ARSLIST.ORG Sent: Wednesday, May 14, 2008 3:09:00 PM Subject: Re: Field Meta Properties? ** William, I wonder if we'll have functionality like that in the new Eclipse tool in 7.5? Could anyone from BMC feel comfortable commenting generically on the issue? Rick On Wed, May 14, 2008 at 12:00 PM, William Rentfrow <[EMAIL PROTECTED]> wrote: ** 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 __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"
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"
>
___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
Re: Field Meta Properties?
Can't you just control the visibility of the field using an AL Guide and use that guide to do the rest of the stuff you want depending on its visibility status? Checking the change flag of a field at client level would be a nice to have feature though it is possible to do this via workflow too.. Go for it, they seem to be reasonable RFE's.. having these would make life a little more easier.. Joe - Original Message From: Rick Cook <[EMAIL PROTECTED]> To: arslist@ARSLIST.ORG Sent: Wednesday, May 14, 2008 3:09:00 PM Subject: Re: Field Meta Properties? ** William, I wonder if we'll have functionality like that in the new Eclipse tool in 7.5? Could anyone from BMC feel comfortable commenting generically on the issue? Rick On Wed, May 14, 2008 at 12:00 PM, William Rentfrow <[EMAIL PROTECTED]> wrote: ** 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"
Re: Field Meta Properties?
That would be a useful feature. Does anyone know if this is possible in 7.5 being that the development method has, from what I've heard, gone more toward a IDE? --- J.T. Shyman _ From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of William Rentfrow Sent: Wednesday, May 14, 2008 3:01 PM To: arslist@ARSLIST.ORG Subject: Field Meta Properties? 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 __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"
Re: Field Meta Properties?
In the interim, you could create view forms into the metatables that might get you the data you want. I'm sure you know how to do that. Then run workflow against the conditions found in the view form. Rick On Wed, May 14, 2008 at 12:09 PM, Rick Cook <[EMAIL PROTECTED]> wrote: > William, I wonder if we'll have functionality like that in the new Eclipse > tool in 7.5? Could anyone from BMC feel comfortable commenting generically > on the issue? > > Rick > > > On Wed, May 14, 2008 at 12:00 PM, William Rentfrow < > [EMAIL PROTECTED]> wrote: > >> ** 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 >> >> __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"
Re: Field Meta Properties?
William, I wonder if we'll have functionality like that in the new Eclipse tool in 7.5? Could anyone from BMC feel comfortable commenting generically on the issue? Rick On Wed, May 14, 2008 at 12:00 PM, William Rentfrow < [EMAIL PROTECTED]> wrote: > ** 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 > > __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"
Re: Field Meta Properties?
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"
