There are several steps in setting up an event mapping notification, however some of these only need to be completed once for all clients.
If you wish to trigger a task or a workflow when your clients meet the
relevant pre-determined event, first you must ensure that a template exists.
If I navigate to Client
> Fact Find > Compliance and input review dates for the clients,
it will then appear correctly.
Note that the ‘notice’ column is set at 30
days. This is dependent on the Due Date in the original
task template, as mentioned earlier in this article.
Step 4: Select the notifications you wish to trigger for the client.
If you wish for a specific notification to trigger for a client, you need to ensure that the tick box has been ticked. Alternatively, if there are notifications you do not wish to trigger you need to ensure these are unticked.
o Review: This has the ‘Annual Review’ preset task to trigger 30 days prior to the date, which we had previously set up. You can see this has a ‘tick’ in the box meaning the task will be created.
o Reminder Date for FTA: As there is no preset task assigned to this key date we are unable to select this notification to trigger. You will need to return to Settings > Event Mapping and assign a task (see Step 2 above)
o Australian drivers license: You can see that while a preset task is assigned to this event, the tick box is not selected. This means the preset task will not trigger for this client. If we were to tick this box on, it would trigger 7 days before the due date.
o
Next Appointment: As per our previous step 2, we assigned a workflow rather than a
preset task to this event. The relevant workflow will trigger instead, based on
the parameters set in that flow.
You will notice that these are the only auto task notifications available for these clients in particular. This page will only display those notifications relevant to a client, so for example another client who has an active FDS rather than FTA would see the relevant FDS key dates in this section.
To summarise,
you can trigger certain tasks or workflows based on key events for a client by
following the following steps:
2. Assign these via the Settings section of AdviceOS to the relevant events
a. This only needs to be completed once and can apply for all clients.
3. Ensure your clients meet the required criteria for the event
4. Tick the notifications you wish to see triggered for this client
a. This needs to be completed at a client level for each client you want the task or workflow to trigger for.
Below is a list of each of the events that can be mapped in AdviceOS, and the location of the respective field. The client must have the relevant fields completed in order to trigger the event.
You will
know whether a client can have an event triggered by seeing the event in the
Client > Fact Find > Notifications section. Only those relevant to that
particular client will be visible. If they are not visible then you need to
update the relevant field.
Notification | Field Location in AdviceOS |
Review Auto Task | Client > Fact Find > Compliance > Reviews |
Disclosure Auto Task* | Client > Fact Find > Compliance > Legacy FDS > Disclosures |
Opt In Auto Task* | Client > Fact Find > Compliance > Legacy FDS > Opt-in |
Client Appointment Auto Task | Client > Fact Find > Notifications > Next appointment date |
Insurance Start Auto Task | Client > Fact Find > Insurance > Policy start date |
Holding Expiry Auto Task | Client > Fact Find > Super, pension and investments > Expiry Date |
Identification Expiry Auto Task | Client > Fact Find > Compliance > Identification details |
FDS Anniversary Reminder Date Auto Task | Advanced Admin > FDS Management > Create Service Agreement |
FDS Reminder Due Date Auto Task | Advanced Admin > FDS Management > Create Service Agreement |
FDS Consent Reminder Date Auto Task | Advanced Admin > FDS Management > Create Service Agreement |
FDS Fee Shutoff Reminder Date Auto Task | Advanced Admin > FDS Management > Create Service Agreement |
FTA Reminder Date Auto Task | Advanced Admin > Fixed Term Agreement Management |
*Note that these are legacy compliance fields, retained for record keeping purposes but ideally should be superseded with the FTA or FDS functionality