VF360 Notifications

This section describes the conditions which must be fulfilled to send notifications to the different categories of VF360 users.

EVENT

TRIGGER

RECEIVER

CONDITION

EMAIL

Credits purchase threshold

Sent if the ‘Credit balance’ value reaches the value set in 'Threshold1’ field by the Administrator

Root Administrator,

Global User

  1. Affected flow step is Prepaid for Account - ‘Pre-paid’ toggle is ON.

  2. ‘Sales’ toggle is ON in Account Parameters.

Message header - “WARNING”.

Body text:

“An amount of <Purchased amount> credit was added to <Account name>, at <Flow step> Flow Step. Previous Balance was: <Credit balance value before purchase>, new balance is: <Credit balance value after purchase>. Purchase reference number is: <'Reference' value for corresponding purchase>.”

Monitoring User,

Organization Admin,
Organization User,
Account,
Account User

  1. Affected flow step is Prepaid for Account - ‘Pre-paid’ toggle is ON.

  2. ‘Purchasing’ toggle is ON in Account Parameters.

Expired contract

Sent if Contract is expired ('Contract expiration date' set in Account profile has passed).

Root Administrator,

Global User

  1. ‘Expiring contract notification’ toggle is ON in respective Account.

  2. ‘Sales’ toggle is ON in Account Parameters.

Message header - “WARNING”.

Body text:

“Contract has expired. To keep reports active, please renew the contract.”

Monitoring User,

Organization Admin,
Organization User,
Account,
Account User

  1. ‘Expiring contract notification’ toggle  is ON in respective Account.

  2. ‘Purchasing’ toggle  is ON in Account Parameters.

Expiring contract

Sent based on ‘Contract expiration date’ in respective Account:

  • one month prior to contract expiration based on ‘Contract expiration date’ in Account profile;

  • two weeks prior to contract expiration;

  • one day prior to contract expiration.

Root Administrator,

Global User

  1. ‘Expiring contract notification’ toggle is ON in respective Account.

  2. ‘Sales’ toggle is ON in Account Parameters.

Message header - “WARNING”.

Body text:

“<Account name> contract expiration date is 23:59:00 <Contract expiration date>. Please extend the contract.”

Monitoring User,

Organization Admin,
Organization User,
Account,
Account User

  1. ‘Expiring contract notification’ toggle is ON in respective Account.

  2. ‘Purchasing’ toggle is ON in Account Parameters.

Monthly Overall report

Sent on 1st day of the month, for the previous month.

Root Administrator,

Global User

‘Sales’ toggle is ON in Account Parameters.

Message header - “Monthly Report”.

Body text:

“Hi <Administratoristrator name>, 

The attached file contains your monthly report.”

Email contains attachment - Overall Report from Dashboard XLS reports.

Monthly Overage report

Sent on 1st month day - for previous month.

Root Administrator,

Global User

‘Sales’ toggle is ON in Account Parameters.

Message header - “Monthly Overage Report”.

Body text:

“Hi <Administratoristrator name>, 

The attached file contains your monthly report.”

Email contains attachment - Overage Report from Dashboard XLS reports.

Missing invoices

Sent if PDF invoice was not uploaded for specific purchase.

Sent once a week (Monday); one e-mail is sent for one missing invoice.

Root Administrator,

Global User

‘Finance’ toggle is ON in Account Parameters.

Message header - “Missing invoice”.

Body text:

“The invoice No. <'Reference' value for corresponding purchase> for the <Workflow step> step of the <Account name> company was not uploaded.”

Credits purchase

Sent if credit amount is purchased for Account with Pre-paid contract

Root Administrator,

Global User,

Monitoring User,

Organization Admin,
Organization User,
Account,
Account User

  1. Affected flow step is Prepaid for Account - ‘Pre-paid’ toggle is ON.

  2. Finance’ toggle is ON in Account Parameters.

Message header - “WARNING”.

Body text:

“An amount of <Purchased amount> credit was added to <Account name>, at <Flow step> Flow Step. Previous Balance was: <Credit balance value before purchase>, new balance is: <Credit balance value after purchase>. Purchase reference number is: <'Reference' value for corresponding purchase>.”

Workflow error

Sent if error event is triggered for Account’s workflow step

Root Administrator,

Global User

  1. ‘Workflow KeepAlive monitoring’ toggle is ON in respective Account.

  2. ‘Workflow errors’ toggle is ON in Account Parameters.

Message header - “WORKFLOW ERROR”

Body text:

“Error in the <Flow step name> flow step.”

Monitoring User,

Organization Admin,
Organization User,
Account,
Account User

  1. ‘Workflow KeepAlive monitoring’ toggle is ON in respective Account.

  2. ‘Operator’ toggle is ON in Account Parameters.

Workflow recovery

Sent if recovery event for error is triggered for Account’s workflow step

Root Administrator,

Global User

  1. ‘Workflow KeepAlive monitoring’ toggle is ON in respective Account.

  2. ‘Workflow errors’ toggle is ON in Account Parameters.

Message header - “WORKFLOW RECOVERY”

Body text:

“Recovery in the <Flow step name> flow step.”

Monitoring User,

Organization Admin,
Organization User,
Account,
Account User

  1. ‘Workflow KeepAlive monitoring’ toggle is ON in respective Account.

  2. ‘Operator’ toggle is ON in Account Parameters.

Workflow NO KEEP ALIVE

Sent if no keep alive message is received for Account’s workflow step.

Root Administrator,

Global User

  1. ‘Workflow KeepAlive monitoring’ toggle is ON in respective Account.

  2. ‘Workflow errors’ toggle is ON in Account Parameters.

Message header - “Agent Keep Alive Error”

Body text:

“Workflow stopped reporting online status.”

Monitoring User,

Organization Admin,
Organization User,
Account,
Account User

  1. ‘Workflow KeepAlive monitoring’ toggle is ON in respective Account.

  2. ‘Operator’ toggle is ON in Account Parameters.

Workflow NO KEEP ALIVE Recovery

Sent if keep alive recovery message is received for Account’s workflow step.

Root Administrator,

Global User

  1. ‘Workflow KeepAlive monitoring’ toggle is ON in respective Account.

  2. ‘Workflow errors’ toggle is ON in Account Parameters.

Message header - “Agent Keep Alive Recovery”

Body text:

“Workflow resumed reporting online status.”

Monitoring User,

Organization Admin,
Organization User,
Account,
Account User

  1. ‘Workflow KeepAlive monitoring’ toggle is ON in respective Account.

  2. ‘Operator’ toggle is ON in Account Parameters.

PARSING ERROR

Sent if XML cannot be parsed by the system:

  • unknown account - Account cannot be read in XML ('event account_name' element);

  • timestamp in future - future date provided in XML (‘time_stamp’ element);

  • unknown error - XML structure cannot be be parsed.

Root Administrator,

Global User

‘Workflow errors’ toggle is ON in Account Parameters.

Message header - “PARSING ERROR”

Body text:

“XML file <XML file name> with timestamp: <value from ‘time_stamp’ element> has failed.

Errors found:

  • <List of error types>.”

Monitoring User,

Organization Admin,
Organization User,
Account,
Account User

‘Operator’ toggle is ON in Account Parameters.

Hardware error

Sent if error event is triggered for Account’s Server

Root Administrator,

Global User

  1. ‘Enable monitoring' toggle is ON in parameters of Account’s Server.

  2. ‘H/W errors’ toggle is ON in Account Parameters.

Message header - “Hardware/OS Error”

Body text:

“<Account name>

Server <Server name> reports:

<Monitored OS/Folder name> usage is over <percentage set as limit for the OS/folder>. Please contact our support team.”

Monitoring User,

Organization Admin,
Organization User,
Account,
Account User

  1. ‘Enable monitoring' toggle is ON in parameters of Account’s Server.

  2. ‘Operator’ toggle is ON in Account Parameters.

Hardware recovery

Sent if recovery event for error is triggered for Account’s Server

Root Administrator,

Global User

  1. ‘Enable monitoring' toggle is ON in parameters of Account’s Server.

  2. ‘H/W errors’ toggle is ON in Account Parameters.

Message header - “Hardware/OS Recovery”

Body text:

“<Account name>

Server <Server name> reports:

<Monitored OS/Folder name> usage is back to normal.”

Monitoring User,

Organization Admin,
Organization User,
Account,
Account User

  1. ‘Enable monitoring' toggle is ON in parameters of Account’s Server.

  2. ‘Operator’ toggle is ON in Account Parameters.

Hardware NO KEEP ALIVE

Sent if no keep alive message is received for Account’s Server.

Root Administrator,

Global User

  1. ‘Enable monitoring' toggle is ON in parameters of Account’s Server.

  2. ‘H/W errors’ toggle is ON in Account Parameters.

Message header - “Agent Keep Alive Error”

Body text:

“<Account name>

Server <Server name> reports:

No Communication with the server.

Please contact our support team.”

Monitoring User,

Organization Admin,
Organization User,
Account,
Account User

  1. ‘Enable monitoring' toggle is ON in parameters of Account’s Server.

  2. ‘Operator’ toggle is ON in Account Parameters.

Hardware NO KEEP ALIVE Recovery

Sent if recovery message for no keep alive is received for Account’s Server

Root Administrator,

Global User

  1. ‘Enable monitoring' toggle is ON in parameters of Account’s Server.

  2. ‘H/W errors’ toggle is ON in Account Parameters.

Message header - “Agent Keep Alive Recovery”

Body text:

“<Account name>

Server <Server name> reports:

Communication with the server recovered.

Resumed reporting online status.”

Monitoring User,

Organization Admin,
Organization User,
Account,
Account User

  1. ‘Enable monitoring' toggle is ON in parameters of Account’s Server.

  2. ‘Operator’ toggle is ON in Account Parameters.

Hardware PARSING ERROR

Sent if hardware XMLs cannot be parsed:

  • unknown account - Account cannot be read in XML ('accountName' element);

  • timestamp in future - future date provided in XML (‘timeStamp’ element);

  • unknown error - XML structure cannot be be parsed.

Root Administrator,

Global User

  1. ‘Enable monitoring' toggle is ON in parameters of Account’s Server.

  2. ‘H/W errors’ toggle is ON in Account Parameters.

Message header - “PARSING ERROR”

Body text:

“XML file <XML file name> with timestamp: <value from ‘time_stamp’ element> has failed.

Errors found:

  • <List of error types>.”

Monitoring User,

Organization Admin,
Organization User,
Account,
Account User

  1. ‘Enable monitoring' toggle is ON in parameters of Account’s Server.

  2. ‘Operator’ toggle is ON in Account Parameters.

Server Entering maintenance mode

Set Maintenance mode ON via Monitoring Agent application.

Root Administrator,

Global User

  1. ‘Enable monitoring' toggle is ON in parameters of Account’s Server.

  2. ‘H/W errors’ toggle is ON in Account Parameters.

Message header - “Maintenance”

Body text:

“<Account name>

Server <Server name> reports:

<Server name> is entering maintenance mode”

Monitoring User,

Organization Admin,
Organization User,
Account,
Account User

  1. ‘Enable monitoring' toggle is ON in parameters of Account’s Server.

  2. ‘Operator’ toggle is ON in Account Parameters.

Server Maintenance mode ended

Set Maintenance mode ON via Monitoring Agent application.

Root Administrator,

Global User

  1. ‘Enable monitoring' toggle is ON in parameters of Account’s Server.

  2. ‘H/W errors’ toggle is ON in Account Parameters.

Message header - “Maintenance”

Body text:

“<Account name>

Server <Server name> reports:

<Server name> ended maintenance mode”

Monitoring User,

Organization Admin,
Organization User,
Account,
Account User

  1. ‘Enable monitoring' toggle is ON in parameters of Account’s Server.

  2. ‘Operator’ toggle is ON in Account Parameters.

System report Warning

Sent if ‘Warning’ system state is reported in system XML.

Root Administrator,

Global User

  1. ‘Enable monitoring' toggle is ON in parameters of Account’s Server.

  2. ‘Software/Modules errors’ toggle is ON in Account Parameters.

Message header - “Hardware/OS Warning”

Body text:

“<Account name>

Server <Server name> reports:

<System name> <Module name>

<Text from ‘message’ element in system XML (IF not empty)>

Please contact our support team.”

Monitoring User,

Organization Admin,
Organization User,
Account,
Account User

  1. ‘Enable monitoring' toggle is ON in parameters of Account’s Server.

  2. ‘Operator’ toggle is ON in Account Parameters.

System report Error

Sent if ‘Error’ system state is reported in system XML.

Root Administrator,

Global User

  1. ‘Enable monitoring' toggle is ON in parameters of Account’s Server.

  2. ‘Software/Modules errors’ toggle is ON in Account Parameters.

Message header - “Hardware/OS Error”

Body text:

“<Account name>

Server <Server name> reports:

<System name> <Module name>

<Text from ‘message’ element in system XML (IF not empty)>

Please contact our support team.”

Monitoring User,

Organization Admin,
Organization User,
Account,
Account User

  1. ‘Enable monitoring' toggle is ON in parameters of Account’s Server.

  2. ‘Operator’ toggle is ON in Account Parameters.

System report Recovery

Sent if ‘Recovery’ system state is reported in system XML for an error.

Root Administrator,

Global User

  1. ‘Enable monitoring' toggle is ON in parameters of Account’s Server.

  2. ‘Software/Modules errors’ toggle is ON in Account Parameters.

Message header - “Hardware/OS Recovery”

Body text:

“<Account name>

Server <Server name> reports:

<System name> <Module name>

<Text from ‘message’ element in system XML (IF not empty)>.

Monitoring User,

Organization Admin,
Organization User,
Account,
Account User

  1. ‘Enable monitoring' toggle is ON in parameters of Account’s Server.

  2. ‘Operator’ toggle is ON in Account Parameters.

System report INFO

Sent if ‘Info’ system state is reported in system XML

Root Administrator,

Global User

  1. ‘Enable monitoring' toggle is ON in parameters of Account’s Server.

  2. ‘Software/Modules errors’ toggle is ON in Account Parameters.

Message header - “Software Info”

Body text:

“<Account name>

Server <Server name> reports:

<System name> <Module name> has sent the following message: <Text from ‘message’ element in system XML (IF not empty)>”.

Monitoring User,

Organization Admin,
Organization User,
Account,
Account User

  1. ‘Enable monitoring' toggle is ON in parameters of Account’s Server.

  2. ‘Operator’ toggle is ON in Account Parameters.

System PARSING ERROR

XML cannot be parsed:

  • unknown account - Account cannot be read in XML ('accountName' element);

  • timestamp in future - future date provided in XML (‘timeStamp’ element);

  • unknown error - XML structure cannot be be parsed.

Root Administrator,

Global User

  1. ‘Enable monitoring' toggle is ON in parameters of Account’s Server.

  2. ‘Software/Modules errors’ toggle is ON in Account Parameters.

Message header - “PARSING ERROR”

Body text:

“XML file <XML file name> with timestamp: <value from ‘time_stamp’ element> has failed.

Errors found:

  • <List of error types>.”

Monitoring User,

Organization Admin,
Organization User,
Account,
Account User

  1. ‘Enable monitoring' toggle is ON in parameters of Account’s Server.

  2. ‘Operator’ toggle is ON in Account Parameters.

System report No KeepAlive

Sent if no keep alive message is received for Account’s System

Root Administrator,

Global User

  1. ‘Enable monitoring' toggle is ON in parameters of Account’s Server.

  2. ‘Software/Modules errors’ toggle is ON in Account Parameters.

Message header - “Agent Keep Alive Error”

Body text:

“<Account name>

Server <Server name> reports:

<System Name>/<System Name> <Module name> stopped reporting online status.

Please contact our support team.”

Monitoring User,

Organization Admin,
Organization User,
Account,
Account User

  1. ‘Enable monitoring' toggle is ON in parameters of Account’s Server.

  2. ‘Operator’ toggle is ON in Account Parameters.

System report recovery No KeepAlive

Sent if recovery message is received for no keep alive for Account’s System

Root Administrator,

Global User

  1. ‘Enable monitoring' toggle is ON in parameters of Account’s Server.

  2. ‘Software/Modules errors’ toggle is ON in Account Parameters.

Message header - “Agent Keep Alive Recovery”

Body text:

“<Account name>

Server <Server name> reports:

<System Name>/<System Name> <Module name> resumed reporting online status.

Monitoring User,

Organization Admin,
Organization User,
Account,
Account User

  1. ‘Enable monitoring' toggle is ON in parameters of Account’s Server.

  2. ‘Operator’ toggle is ON in Account Parameters.

System/module Entering maintenance mode started

Sent if XML is received with info that Maintenance mode has started.

Root Administrator,

Global User

  1. ‘Enable monitoring' toggle is ON in parameters of Account’s Server.

  2. ‘Software/Modules errors’ toggle is ON in Account Parameters.

Message header - “Maintenance”

Body text:

“<Account name>

Server <Server name> reports:

<Server name> <System name> <Module name> is entering maintenance mode”

Monitoring User,

Organization Admin,
Organization User,
Account,
Account User

  1. ‘Enable monitoring' toggle is ON in parameters of Account’s Server.

  2. ‘Operator’ toggle is ON.

System/module Maintenance mode ended

Sent if XML is received with info that Maintenance mode has ended.

Root Administrator,

Global User

  1. ‘Enable monitoring' toggle is ON in parameters of Account’s Server.

  2. ‘Software/Modules errors’ toggle is ON.

Message header - “Maintenance”

Body text:

“<Account name>

Server <Server name> reports:

<Server name> <System name> <Module name> ended maintenance mode”

Monitoring User,

Organization Admin,
Organization User,
Account,
Account User

  1. ‘Enable monitoring' toggle is ON in parameters of Account’s Server.

  2. ‘Operator’ toggle is ON in Account Parameters.

System/module installed

Sent if new version of System/Module was installed on a Server

Root Administrator,

Global User,

Monitoring User,

Organization Admin,
Organization User,
Account,
Account User

  1. Notifications toggle is ON for System/Module on Global Version Control page.
  2. Notifications toggle is ON for the same System/Module on Account Version Control page.

  3. ‘Software /Modules version & Licenses Notifications’ toggle is ON in Account Parameters.

Message header - “Software Info”

Body text:

“<Account name>

Server <Server name> reports:

<System/Module name> version 3 was installed on the server.”

Licence will expire

Sent weekly (on Monday).

Every Monday email is sent for each System and Module that will expire during the week.

Message header - “System/Module Warning”

Body text:

“<Account name>

Server <Server name> reports:

<System name>/<System name> <Module name> version 1.

License will expire on <Expiration date value for affected System/Module> 00:00:00.”

System is up to date

Sent if Account reports system and modules versions used IF these versions are the latest ones (available on the Global Version Control page).

Message header - “System version”

Body text:

“<Account name>

Dear account,

Current version <System name> <System version> is up to date.

New version of the System/Module is available

Sent if installed version of System/Module is not up to date and latest version is available.

Message header - “System/Module version warning”

Body text:

“<Account name>

Server <Server name> reports:

Dear account, You run <System name>/ <System name> <Module name> version <System/Module version installed by Account>.

The latest version is <Latest System/Module Version>, which includes important bug and security updates.

Please contact our support team for information regarding the advantages of using the newest version.”

Security code usage

Security Code entered during System and Module reporting via the Monitoring Agent application does not match any Code in the Server Monitoring table.

Message header - empty.

Body text:

“<Account name>

Server <Server name> reports:

Unauthorized software update attempt for <Server name> <System name>.”

Daily report

Sent on a daily basis containing XLS report from Table View.

Organization Admin,

Organization User, Account, Account User

  1. ‘Send daily report’ toggle is ON for needed Flow step in respective Account Parameters.

  2. ‘Daily reports’ toggle is ON in Account Parameters.

Message header - Daily report.

Body text:

“Hi <Account name>,

The attached file contains your daily report.”

The email contains attachment.