Skip to main content
1-Visitor
January 25, 2013
Question

Timers and Deadlines in Workflow

  • January 25, 2013
  • 2 replies
  • 856 views

Which is better ? A timer running for 3 years ? or a Dead line set for 3 years?



Giridhar














2 replies

12-Amethyst
January 25, 2013
If you can use a deadline, then do that. Timers create queue objects that
run on a schedule, and over 3 years, you will do several MORs and possibly
a major upgrade. Lots and lots of long-running, queued up timers should
theoretically work fine, but I'd rather not have to worry about them for
that long.

We don't use deadlines because we don't have any tasks that have a
specific, easily identifiable deadline, and we didn't want to worry about
setting or changing them. Instead, we use Need Date in the change process
to communicate when something is or is not on time rather than trying to
put deadlines on each task within each change object's workflow.

Al






[solutions] - Timers and Deadlines in Workflow

Giri G
1-Visitor
January 28, 2013

OK.


I checked the same with PTC and they say there is no difference between Timer or deadline, and works pretty much the same.


Either can be used with same performance impact.