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's Therapist' on September 03, 2001 at 11:41:51 EST:

In Reply to: Re: Implementing a time lag - Workflow posted by [IP Address: 194.154.214.69] 'Elaine' on August 30, 2001 at 04:04:02 EST:

Hi Elaine,
Whichever method you use for creating the worklist is not important. What is important is that in the Worklist Definition part on the Business Process you map a DateTime value to the ACTIONDTTM field . If you do not map a value to ACTIONDTTM then it has a NULL value and can be seen immediatly by the users. If you do map a value then a worklist can only be seen by users once the DateTime in the ACTIONDTTM field is reached.
Therefore this allows you to delay until a predetermined Date & Time when users can see a particular worklist.
Hope this helps!

Tom Namla's Therapist

P.S Tom has gone to have a long lie down in a very dark room.

: Unfortunately I work for a company that require System Design Documents before we are even allowed to touch the system. (As it should be!)

: Even if we were allowed, I can't, because they're still upgrading it.

: Why would they mention in PeopleBooks and on the training course that you can implement a time lag (exactly as I want it) by merely mapping a field, and not inform you that you have to create a Component Interface or DB agent to actually do this???

: I wasn't looking for a particularly complex solution - even GSC had no idea what I was talking about!

: Have YOU done this before? Have you implemented a time lag in workflow before?

: But, granted, your idea of creating a Component Interface does sound as though it can work. It's just a surprising turn of events.

: I feel dumb enough already - please don't make it worse!!! ;-)

Follow Ups:

Post a Followup

Name:
E-Mail:
Subject:
Message: : Hi Elaine, : Whichever method you use for creating the worklist is not important. What is important is that in the Worklist Definition part on the Business Process you map a DateTime value to the ACTIONDTTM field . If you do not map a value to ACTIONDTTM then it has a NULL value and can be seen immediatly by the users. If you do map a value then a worklist can only be seen by users once the DateTime in the ACTIONDTTM field is reached. : Therefore this allows you to delay until a predetermined Date & Time when users can see a particular worklist. : Hope this helps! : Tom Namla's Therapist : P.S Tom has gone to have a long lie down in a very dark room. : : Unfortunately I work for a company that require System Design Documents before we are even allowed to touch the system. (As it should be!) : : Even if we were allowed, I can't, because they're still upgrading it. : : Why would they mention in PeopleBooks and on the training course that you can implement a time lag (exactly as I want it) by merely mapping a field, and not inform you that you have to create a Component Interface or DB agent to actually do this??? : : I wasn't looking for a particularly complex solution - even GSC had no idea what I was talking about! : : Have YOU done this before? Have you implemented a time lag in workflow before? : : But, granted, your idea of creating a Component Interface does sound as though it can work. It's just a surprising turn of events. : : I feel dumb enough already - please don't make it worse!!! ;-)

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