I agree with this @Alex you say that the verification is there to protect, but we are talking about deposit, finance, B&P when an agent clicks on those it is gone, no more reminder that infact it is still due.
It looks like there’s 2 requirement requests going on here:
1. Triggering addition of tracks based on an event.
2. Having reminders that are attached to floating dates (e.g. unconditional date, settlement date etc). E.g. 3 days before unconditional.
Would be good to get some more info on both of these items.
1. Regarding triggering addition of tracks based on events:
Presumably you want support for this in multiple modules. If so, is it all modules or just some?
For each module, what are the events that you think should be supported for triggering track addition?
Is this an automatic process or is the user prompted to add the track when the event occurs.
If the desire is for the track addition it to be automatic, how do we deal with questions like which contact should a track be attached to in a listing or property that includes multiple contacts or in a contact that includes multiple listing /properties?
If the process is manual and the event occurs via API or in some way other than the user interacting with the track what do we do?
How are these tracks cancelled?
2. Regarding floating date reminders:
Presumably you want support for this in multiple modules. If so, is it all modules or just some?
For each module, what are the date fields that you think should be supported for a reminder to be tied against.
What happens to these reminders when they exist but the date does not (e.g. a reminder that is tied to an active contract unconditional date but there is no active contract on the property).
Would be great to get more input on this either here in the comments section or in rexperts.
It looks like there’s 2 requirement requests going on here:
1. Triggering addition of tracks based on an event.
2. Having reminders that are attached to floating dates (e.g. unconditional date, settlement date etc). E.g. 3 days before unconditional.
Would be good to get some more info on both of these items.
1. Regarding triggering addition of tracks based on events:
Presumably you want support for this in multiple modules. If so, is it all modules or just some?
For each module, what are the events that you think should be supported for triggering track addition?
Is this an automatic process or is the user prompted to add the track when the event occurs.
If the desire is for the track addition it to be automatic, how do we deal with questions like which contact should a track be attached to in a listing or property that includes multiple contacts…
Yvonne Howard
I agree with this @Alex you say that the verification is there to protect, but we are talking about deposit, finance, B&P when an agent clicks on those it is gone, no more reminder that infact it is still due.