General and Communication Messaging
From FloristWiki
| (8 intermediate revisions not shown.) | |||
| Line 1: | Line 1: | ||
| - | General and communication messaging sent from Mercury Point of Sale and Mercury Connect | + | {{TOCright}} |
| + | [[General Message|General]] and communication messaging sent from Mercury Point of Sale and [[Mercury Connect]] customers supports the following functionality: | ||
*Tracking of Mercury User Roles and PC Client information | *Tracking of Mercury User Roles and PC Client information | ||
*A text message retry limit | *A text message retry limit | ||
| Line 6: | Line 7: | ||
<br> | <br> | ||
==Tracking Mercury User Roles and PC Client Information== | ==Tracking Mercury User Roles and PC Client Information== | ||
| - | You can track Mercury user roles as well as PC | + | You can track Mercury user roles as well as their PC client information. The following user roles, or job functions, are tracked: |
*'''Admin''': Employees that are configured as administrators in the [[Mercury Administration: Job Functions Screen| | *'''Admin''': Employees that are configured as administrators in the [[Mercury Administration: Job Functions Screen| | ||
Mercury Administration Job Functions]] screen. | Mercury Administration Job Functions]] screen. | ||
| Line 13: | Line 14: | ||
*'''Clerk''': Employees that are configured as any job function other than administrator or driver in the [[Mercury Administration: Job Functions Screen|Mercury Administration Job Functions]] screen. | *'''Clerk''': Employees that are configured as any job function other than administrator or driver in the [[Mercury Administration: Job Functions Screen|Mercury Administration Job Functions]] screen. | ||
| - | Once an employee logs in to the system, their job function is marked as “active.” The number of active user roles | + | Once an employee logs in to the system, their job function is marked as “active.” The number of active user roles ranges from 0 – 3. |
| - | On the 25th of each month, FTD Mercury generates a general (GEN) message as an FTD Mercury Usage Report | + | On the 25th of each month, FTD Mercury generates a [[General Message|general]] (GEN) message displayed as an FTD Mercury Usage Report. This message includes a list of clients, their operating systems, and the number of active user roles. |
The message includes each client and their operating system immediately below the server information. The number of active user roles is displayed below the client and operating system information. | The message includes each client and their operating system immediately below the server information. The number of active user roles is displayed below the client and operating system information. | ||
| + | |||
| + | For example, an FTD Mercury Usage Report may include the following information: | ||
| + | |||
| + | <tt><big>Client1: Windows 7<br> | ||
| + | Client2: Windows 7<br> | ||
| + | Active User Roles: 2</big></tt> | ||
<br> | <br> | ||
<table> | <table> | ||
| Line 25: | Line 32: | ||
</td> | </td> | ||
<td> | <td> | ||
| - | The number of active user roles indicates the user roles that have logged into the system since the last scheduled job was run. After the message is generated, the system resets the | + | The number of active user roles indicates the user roles that have logged into the system since the last scheduled job was run. After the message is generated, the system resets the active user role tracking. </td> |
</tr> | </tr> | ||
</table> | </table> | ||
| + | <br> | ||
==Text Message Retry Limit== | ==Text Message Retry Limit== | ||
| - | + | In the event that a text message is not correctly sent, the Mercury system attempts to send text messages from florists three times. Once the final attempt is made, an automated error message is logged in the Mercury support log. | |
| - | + | <br> | |
| + | <table> | ||
| + | <tr> | ||
| + | <td> | ||
| + | [[Image:NoteIcon.png]] | ||
| + | </td> | ||
| + | <td> | ||
| + | This value is not configurable by the user. </td> | ||
| + | </tr> | ||
| + | </table> | ||
For more information on text messaging, refer to [[Mercury Administration: Text Message Screen]]. | For more information on text messaging, refer to [[Mercury Administration: Text Message Screen]]. | ||
| + | <br><br> | ||
| + | ==Enforcing a Blackout Period== | ||
| + | You can schedule a blackout period through the [[Mercury Administration: Mercury Connection Screen|Mercury Administration’s Mercury Connection]] screen. During this time, the following external services are paused: | ||
| + | |||
| + | *Order Life Cycle events | ||
| + | *Mobile App | ||
| + | *Blabber Messages | ||
| + | *ASU | ||
| + | *Collector | ||
| + | <br> | ||
| + | ==Configurable Threshold for COM Alerts== | ||
| + | You can configure the printing of Communication (COM) alerts when communication is lost between the florist devices and the Mercury Administration system. This value is configured in the [[Mercury Administration: Printer Routing Screen|Mercury Administration’s Printer Routing]] screen via the Maximum Notifications field. This field can include values from 3-99, with a default value of 3. Additionally, you can set the number of minutes after which to resume COM alerts via the Resume Alerts in (minutes) field. This field allows values from 5-99 in 5 minute increments, with a default of 90 minutes. | ||
| + | |||
| + | If communication is not established, the FTD Mercury system continues to display and print alerts until the configurable number of minutes have passed since alerts were suspended. Once communication is reestablished and alerts resume, the notification counter and resume time are reset to zero. | ||
| + | |||
| + | Prior to the suspension of alerts, the following message appears and prints: | ||
| + | |||
| + | <tt><big>Printing suspended for the next ''configurable amount'' minutes.</big></tt> | ||
| + | <table> | ||
| + | <tr> | ||
| + | <td> | ||
| + | [[Image:NoteIcon.png]] | ||
| + | </td> | ||
| + | <td> | ||
| + | If the system is rebooted or restarted, COM alerts resume and the alert counter and resume time are reset to zero. </td> | ||
| + | </tr> | ||
| + | </table> | ||
| + | |||
| + | |||
| + | <hr> | ||
| + | [[FTD Mercury Documentation|Back to FTD Mercury Documentation]] | ||
Current revision
|
General and communication messaging sent from Mercury Point of Sale and Mercury Connect customers supports the following functionality:
- Tracking of Mercury User Roles and PC Client information
- A text message retry limit
- Enforcement of a blackout period for specified external services
- A configurable threshold for Communication (COM) alerts
Tracking Mercury User Roles and PC Client Information
You can track Mercury user roles as well as their PC client information. The following user roles, or job functions, are tracked:
- Admin: Employees that are configured as administrators in the Mercury Administration Job Functions screen.
- Driver: Employees that are configured as drivers in the Mercury Administration Job Functions screen.
- Clerk: Employees that are configured as any job function other than administrator or driver in the Mercury Administration Job Functions screen.
Once an employee logs in to the system, their job function is marked as “active.” The number of active user roles ranges from 0 – 3.
On the 25th of each month, FTD Mercury generates a general (GEN) message displayed as an FTD Mercury Usage Report. This message includes a list of clients, their operating systems, and the number of active user roles.
The message includes each client and their operating system immediately below the server information. The number of active user roles is displayed below the client and operating system information.
For example, an FTD Mercury Usage Report may include the following information:
Client1: Windows 7
Client2: Windows 7
Active User Roles: 2
|
|
The number of active user roles indicates the user roles that have logged into the system since the last scheduled job was run. After the message is generated, the system resets the active user role tracking. |
Text Message Retry Limit
In the event that a text message is not correctly sent, the Mercury system attempts to send text messages from florists three times. Once the final attempt is made, an automated error message is logged in the Mercury support log.
|
|
This value is not configurable by the user. |
For more information on text messaging, refer to Mercury Administration: Text Message Screen.
Enforcing a Blackout Period
You can schedule a blackout period through the Mercury Administration’s Mercury Connection screen. During this time, the following external services are paused:
- Order Life Cycle events
- Mobile App
- Blabber Messages
- ASU
- Collector
Configurable Threshold for COM Alerts
You can configure the printing of Communication (COM) alerts when communication is lost between the florist devices and the Mercury Administration system. This value is configured in the Mercury Administration’s Printer Routing screen via the Maximum Notifications field. This field can include values from 3-99, with a default value of 3. Additionally, you can set the number of minutes after which to resume COM alerts via the Resume Alerts in (minutes) field. This field allows values from 5-99 in 5 minute increments, with a default of 90 minutes.
If communication is not established, the FTD Mercury system continues to display and print alerts until the configurable number of minutes have passed since alerts were suspended. Once communication is reestablished and alerts resume, the notification counter and resume time are reset to zero.
Prior to the suspension of alerts, the following message appears and prints:
Printing suspended for the next configurable amount minutes.
|
|
If the system is rebooted or restarted, COM alerts resume and the alert counter and resume time are reset to zero. |
