Preemptive events
Greg Gilman/GM
Preemptive events are typically evaluated everytime the track is processed,
before the sequential events. An AP will not loop over and over, but it
should pickup where it left off the next time it is processed, after
evaluating the preemptive events. How is the track setup? Have you
considered branching to another track?
- Greg,
GoldMine Support
Visit our online KnowledgeBase at
http://kbase.goldminesw.com
Craig Smith <cra...@desktopvisuals.com> wrote in message
news:386A317B...@desktopvisuals.com...
> My AP is designed to loop back to a preemptive event which if true will
> then branch to a later sequential event and if false continue the track
> in sequence. The preemtive event works predictably the first time
> through but when the track loops back it behaves as a sequential event
> in that if false does not move on the next event.
>
> Is this how this is supposed to work? AP not support loops?
>
> Thank You,
>
> Craig
>
Craig Smith
I have been working with 2 tracks for days now. I have a lot of issues so I am
going to give you the tracks and explain the best I can.
Track 1
seq. Trigger Action comments
P30 Condition Goto Event If condition true goto S700
(contact2->utotslid)>20
P60 Condition Print If condtion true print a
form
S250 Immediate Update field ((contact2->utotslid)+1)
S350 immediate Attatch track Attatches Track 2 with "process
track..."checked
S400 Immediate Remove Track
S700 immediate Update field field=(contact2->utotslid)
value=1000
S800 immediate Update field field=(contact2->utotslid)
value=0
Track 2 is essentialy the same except it attatches Track 1 with "process
track..." also checked.
The value of (contact2->utotslid) works with a lookup.ini file to run 2
different macros. The value 0 does nothing, any edit other than 0 but not 1000
runs macro 801, and the value 1000 runs macro 802. If the value is >20 then we
run the last two events. Scan current contact is the scan method.
Issues.
1. Track 1 runs, Track 2 is attatched, runs and attatches Track 1. Track 1
does not process a second time. It is stopped at S250 (note the immediate
trigger).
2. P60 condition never triggers when run in the AP but works fine when I use
the expression tester. I have tested the condition as a trigger alone in its
own track and it does not work that way either. I only started having this
particular problem after updating to 9922. The expression is fairly simple.
(STOD((CONTSUPP->STATE))-10)<=DATE().AND.(DATE()<=(STOD((CONTSUPP->STATE))))
I realize that this expression will only work when the cursor is in the right
place. That is what the macros are going to do.
3. My field updates are not running the macros. My ini file is good. I can
enter the values manually and the macros run. The fields are updating during
the AP scan.
That is enough to chew on for now.
Craig
Craig Smith
I'm sorry if I did not explain well enough. The macros are not updating
fields. Events in the APs are doing the updating. I got the idea from
Goldmine support. Update a field and use the lookup.ini file to execute a
macro. Try and focus on the core problems with the APs for me and I will sort
out the rest.
Note that if the Lookup.ini file is changed to lookup.inx and goldmine
restarted, romoving any problems that might occur with the macros, I still have
issues 1 and 2.
Thank you
Craig
Greg Gilman/GM wrote:
> Craig,
>
> I would discourage the use of macros from within an AP, especially when
> using them to update a field. You should create events in your track to
> update those fields.
>
> - Greg,
>
> GoldMine Support
> Visit our online KnowledgeBase at
> http://kbase.goldminesw.com
>
> Craig Smith <cra...@desktopvisuals.com> wrote in message
> news:387BDC4F...@desktopvisuals.com...
Greg Gilman/GM
Greg Gilman/GM
Why don't you describe what you would like this track to do exactly. I can
then give you some suggestions on how to do that.
Thanks
- Greg,
GoldMine Support
Visit our online KnowledgeBase at
http://kbase.goldminesw.com
Craig Smith <cra...@desktopvisuals.com> wrote in message
news:387D06ED...@desktopvisuals.com...