Re: Implementing a time lag

Re: Implementing a time lag - Workflow

[ Follow Ups ] [ Post Followup ] [ Message Board ]

Posted by [IP Address: 194.154.214.69] 'Tom Namla' on August 29, 2001 at 03:43:56 EST:

In Reply to: Re: Implementing a time lag - Workflow posted by [IP Address: 194.154.214.69] 'Tom Namla' on August 28, 2001 at 12:19:33 EST:

after a quick think...
I've been able to get actiondttime mapping to work, although it has'nt been a problem for me. no matter what you map it always sets it to what it wants ( at least 7.5 and below ).
If you want a different date:
answer1
maybe try a sqlexec after the triggerbusinessprocess to update it. Problem with this is that sqlexecs used like this can have inherent problems.
answer2 maybe do a database agent or a component interface to create the worklist on the date you prefer. Problem with this is that database agent are a black art and you'll have to sacrifice 2 chickens and a virgin.

Follow Ups:

Re: Implementing a time lag - Workflow Elaine 09:06:02 8/29/01 EST (3)
- Re: Implementing a time lag - Workflow Tom Namla 10:21:46 8/29/01 EST (2)
  - Re: Implementing a time lag - Workflow Elaine 04:04:02 8/30/01 EST (1)
    - Re: Implementing a time lag - Workflow Tom Namla's Therapist 11:41:51 9/03/01 EST (0)

Post a Followup

Name:
E-Mail:
Subject:
Message: : after a quick think... : I've been able to get actiondttime mapping to work, although it has'nt been a problem for me. no matter what you map it always sets it to what it wants ( at least 7.5 and below ). : If you want a different date: : answer1 : maybe try a sqlexec after the triggerbusinessprocess to update it. Problem with this is that sqlexecs used like this can have inherent problems. : answer2 maybe do a database agent or a component interface to create the worklist on the date you prefer. Problem with this is that database agent are a black art and you'll have to sacrifice 2 chickens and a virgin.