multiple tracks - kill one only
Charles Jerry
built an automated process that notifies their producers at certain times
during the sales cycle when to contact the prospect. Many of their
prospects have multiple policies and these policies can have different
x-dates (policy expiration dates). I have set up a profile for each x-date
on each prospect. The profile is "xdate" and the reference is one of the 12
months of the year.
Based on this criteria, we create groups for individual x-date months and
attach the AP it.
Here's the scenario for my problem:
We have a prospect with multiple APs running, (say one for a January policy
and one for a March policy). I can't seem to figure how to kill the January
process at the end of the sales cycle (or the did not quote cycle) without
affecting the March AP as well. Can you lend me any help on the criteria I
can use in the AP to touch only January and not kill March along with it?
Greg Gilman
Are you attaching a separate track for each expiration month? If you branch
to a separate track for each month, you should be able to remove each track
independently of any others. It does not have to be a newly created track,
you could attach the same track for each expiration month.
- Greg,
GoldMine Support
Visit our online KnowledgeBase at
http://kbase.goldminesw.com
Charles Jerry <cp...@aristotle.net> wrote in message
news:Y7j0JYQX$GA.169@gmnews2...
Charles Jerry
tell the system to kill that track for January and not for March if it is
the same track name?
Greg Gilman <newss...@goldmine.com> wrote in message
news:nemJyriX$GA.169@gmnews2...
Greg Gilman/GM
Each track is processed independently. If you attach the track in January
and tell it to do something in 30 days it will do it. At the same time you
can attach another track in Febuary and it will complete the tasks assigned
to it. These are all things we must deal with creating APs. If you can not
tell one track from another after attaching them, rename the track for each
month before you attach it.
I do not know what criteria you use to remove the tracks, or what events
your tracks contain, so I can not offer any suggestions about how to modify
them. What are you trying to accomplish with this AP and what events does
it contain?
- Greg,
GoldMine Support
Visit our online KnowledgeBase at
http://kbase.goldminesw.com
Charles Jerry <cp...@aristotle.net> wrote in message
news:LgL9wepX$GA.282@gmnews2...
Charles Jerry
sales process. Mainly its a reminder that its time to take a particular
action. Call the prospect here, visit the prospect at this point, etc. The
logic problem I am having is that a potential sale can have 3 possible
outcomes. Sold, Lost, or Did Not Quote. I believe where I am getting hung
up is at the point of a Did Not Quote. This could come at any time during
the sales process. Under my design, it is possible to have 3 process
running at once. One for January, one for March and one for April as an
example. Each of these tracks would be placed on the same prospect because
he has multiple policies with different expiration dates. The process needs
to be worked through for each policy. Up to this point I thought I could
use a history item as the trigger to remove a particular track. My thought
was to have a preemptive item that looked for a history item pertaining to a
sale.
Based on the outcome of this sale, items would be printed then the track
would be removed.
Assume all the tracks look the same (as you suggested earlier) except for
the date they are placed in motion. If my March track is running and I have
a recorded history event from my January track for a "did not quote" (this
would be shown as a sale in the history folder), what is to keep the
preemptive process in my March track from killing itself because of a
history item generated for the January track?
Is there any way to identify a sales outcome to a particular track or should
I be trying to use a different item as the "kill track" trigger?
Greg Gilman/GM <sup...@goldminesw.com> wrote in message
news:56LJm5QY$GA.169@gmnews2...
Greg Gilman/GM
If you would like the history records to reflect which policy they are
associated with you may specify an activity and/or a result code. Each AP
can then trigger history records with the correct code. The code could
simply be the month of expiration. This would require a separate copy of
the track for each expiration month.
Another alternative is to attach the AP for one month at a time, however it
sounds like you would like to track multiple months at the same time.
- Greg,
GoldMine Support
Visit our online KnowledgeBase at
http://kbase.goldminesw.com
Charles Jerry <cp...@aristotle.net> wrote in message
news:geU4FVjY$GA.291@gmnews2...