====== Advisories ======

<WRAP right>
<faicon fas fa-exclamation-triangle fa-xl >
</WRAP>

Advisories are checks which can be run against certain records in the database such as unbooked slots or booked appointments.  They allow you to set warning markers if any of the checks fail.  They will be indicated on views with an alert indicator similar to that on the right.

In general usage they are quick ways to flag process or status issues in your MB data.  As an example, your incubator may expect a user to engage with an advisor no more than once every two weeks.  An advisory could be written to check for users that have requested more frequent meetings than this.  If a user books a slot but an advisory triggers, the meeting will be requested, but even if the [[booking_logic|meeting logic]] allows confirmation, a meeting with an advisory warning can only be requested.

If you then click into a specific record to view it in detail, the same checks will be run and any warnings displayed at the top of the page.

Advisories are based upon specific SQL reports, written in a similar fashion to [[reports|Reports]], but there are a couple of extra items that need setting to make them function correctly. Details of how to create these can be found here:  [[advisory-examples|Advisory Examples]]

If you have sufficient permissions, you can see your current Advisories via the  **Other Views -> Advisories** menu. 

<WRAP important round>
Individual advisories can be enabled or disabled as required, but do note that each advisory in a category (such as slots) will be run on all active slots each time the index or calendar view is opened. It is therefore advised to keep the number of advisories fairly short to avoid long processing and loading times.
</WRAP>