Breadcrumbs

PrinterEventComment

Description

Implementation of this method is not required; however, you must indicate on the MPS Portal that it will not be used. If implemented, this method will be executed by the MPS Portal when a user posts a comment on a printer event.

Syntax 

public string PrinterEventComment(int eventID, int enterpriseID, string enterpriseName, int warningID, string warningName, string warningData, DateTime dtCreated, int criticalID, string printerName, string printerModel, string printerManufacturer, string printerSerial, string printerAddress, string printerLocation, string printerSite, string printerDepartment, int userID, string userName, string userEmail, string comments)

Parameters

  • eventID: a unique identifier that identifies this specific event opened in the MPS Portal;

  • enterpriseID: a unique numeric identifier representing the company;

  • enterpriseName: company name;

  • warningID: a unique numeric identifier indicating the type of alert this event represents;

  • warningName: name (in Portuguese) of the problem type. Example: Out of Paper, Cover Open, etc.;

  • warningData: additional information reported by the printer regarding the event;

  • dtCreated: date and time the alert occurred on the printer;

  • criticalID: indicates the criticality level of this event (according to rules defined by the provider). These are: 1 (critical), 2 (moderate), and 3 (minor);

  • printerName: name of the printer where the event occurred;

  • printerModel: model name of the printer where the event occurred;

  • printerManufacturer: name of the manufacturer of the printer where the event occurred;

  • printerSerial: serial number of the printer where the event occurred;

  • printerAddress: IP address of the printer where the event occurred;

  • printerLocation: physical location of the printer within the company;

  • printerSite: name of the printer’s site;

  • printerDepartment: name of the printer’s department;

  • userID: unique numerical identifier representing the user who called this function via the MPS interface;

  • userName: name of the user who made the call;

  • userEmail: email address of the user who made the call (left blank if the call was made by the system);

  • comments: comment the user made regarding this action.

Sending a response to the MPS

Click here to learn how to send a response to the MPS Portal by referring to the item titled Sending a response to the MPS Portal.