About Publications, Categories, Subscribers, and Key Values
Predefined Publications
SyteLine has set up these predefined publications to which users can subscribe:
Publication | Description | Used By |
---|---|---|
APVoucherPostingBackgroundError | An error occurred while posting an A/P voucher in Background Queue | SyteLine users |
ARPaymentPostingBackgroundError | An error occurred while posting an A/R payment on the Background Queue | SyteLine users |
BOMBulkImportError | BOM Bulk Import error occurred | Users running a BOM bulk import |
CPConsignedInvLevelAlert | Quantity of customer consigned inventory has gone below the minimum or above the maximum value | Customer Portal users |
CPVendorInteractionAlert | SyteLine user has entered interaction text for subscribed Customer Portal users | Customer Portal users |
CustomerCreditHoldAlert | A customer was put on credit hold | Financial Controller mobile; Salesperson mobile |
CustomerDocumentUploadAlert | A customer has uploaded a document using Customer Portal, or an SyteLine user has uploaded a customer document using | SyteLine users who approve documents uploaded by other users or by customers using Customer Portal |
CustomerInteractionFollowUpAlert | A follow-up is needed to a customer interaction. Key Value 1 defines the customer number. | Salesperson mobile |
CustomerOrderCreditHoldAlert | A customer order was put on credit hold | Salesperson mobile |
CustomerShipmentAlert | An order was shipped to a customer (for specific orders/customers) | Salesperson mobile |
DCShopFloorTransactionErrorAlert | A specified number of Data Collection shop floor transaction errors occurred. Key Value 1 defines how many errors must be generated before the user receives an alert | Production supervisor mobile |
InvoiceTransactionBackgroundError | An error occurred during invoice posting on the Background Queue | SyteLine users |
ItemPriceRequestAlert | An item price request was entered in SyteLine | Vendor Portal users who respond to item price requests |
ItemPriceResponseAcceptedAlert | An item price response was accepted in SyteLine | Vendor Portal users who respond to item price requests |
ItemPriceResponseAlert | An item price response was entered in Vendor Portal | SyteLine users who enter item price requests |
JobMaterialCostAlert | The quantity issued against a job is more than required and the total material cost (actual) of the job exceeds the required cost by a certain percent (tolerance) set by the user | Financial Controller mobile; Production supervisor mobile |
JobOperationHoursAlert | Labor hours for a job were more than estimated | Production supervisor mobile |
JobOverProductionAlert | The completed quantity of a job is greater than the released quantity | Production supervisor mobile |
JobProjectedLateForCustomerAlert | A job is projected to be late for a specified customer. Key Value 1 is the customer number. | Production supervisor mobile |
LateOrderShippingAlert | At least one open order line for a customer has a due date prior to the current date. Key Value 1 is the customer number | Executive mobile |
LeadAssignedAlert | A lead is assigned to a salesperson | Salesperson mobile |
LockedUserAlert | A user is locked out | IT Admin mobile |
NewCustomerCreatedAlert | A new customer has been created in Customer or Reseller Portal.
For resellers to receive emails when new customers associated with them are registered in the Customer Portal, reseller users should be subscribed to this publication with KeyValue set to their salesperson ID (for example, KeyValue = JAR). When any customer with slsman = JAR is registered in the portal, the reseller is notified by email. SyteLine users should be subscribed with KeyValue set to Null, so they get email when any customer is created from the portals. |
Reseller Portal users and
SyteLine users |
OpportunityDueAlert | An opportunity is due | Salesperson mobile |
OrderShippingAlert | The customer's order has shipped | Customer Portal or Reseller Portal users |
OverBudgetAlert | The specified account's actual amount is above budget for the current fiscal period. Key Value 1 is the account number, and Key Value 2 is the percentage over budget that triggers an alert | Financial Controller mobile; Executive mobile |
PortalIncidentAlert | An incident was entered in Customer or Reseller Portal | SyteLine users |
PortalOrderReceivedAlert | An order has been placed in
Customer or Reseller Portal. For resellers to receive emails when their customers place orders in the Customer Portal, reseller users should be subscribed to this publication with KeyValue set to their salesperson ID (for example, KeyValue = JAR). When any customer with slsman = JAR places an order in the portal, the reseller is notified by email. SyteLine users should be subscribed with KeyValue set to Null, so they get email when any order is created from the portals. |
Reseller Portal users and
SyteLine users |
PortalOrderRequestDateBeforeDueDateAlert | A portal order was placed with a request date before the due date | SyteLine users |
PortalSROLaborTransactionAlert | A service request order (SRO) labor transaction was entered in Reseller Portal | SyteLine users |
PortalSROMatlTransactionAlert | A service request order (SRO) material transaction was entered in Reseller Portal | SyteLine users |
PortalSROMiscTransactionAlert | A service request order (SRO) miscellaneous transaction was entered in Reseller Portal | SyteLine users |
PortalUnitRegistrationAlert | A unit registration was entered in Customer or Reseller Portal | SyteLine users |
ProjectedLateShipAlert | An order line is projected to ship late. Key Value 1 is the customer number. | Salesperson mobile; Executive mobile |
ProspectInteractionFollowUpAlert | A follow-up is needed with a prospect. Key Value 1 is the prospect ID. | Salesperson mobile |
ScheduledMaintenanceAddedAlert | A service request originates as a result of a call center incident. | Molding Industry Pack |
ScheduledMaintenanceAlert | Service work for scheduled maintenance is needed. | Molding Industry Pack |
SLCustomerInteractionAlert | A customer has entered interaction text using Customer Portal. Key Value for subscribers of this publication can contain a single interaction topic (from the Interaction Topics form) to limit alerts received to only interactions about that topic. Key Value also can be left blank to receive all alerts about all topics. | SyteLine users who respond to Customer Portal
interactions In multi-site implementations, the user must be subscribed to this alert in the site for which they are responsible and in the primary site. |
SLVendorInteractionAlert | A vendor has entered interaction text using Vendor Portal. Key Value for subscribers of this publication can contain a single interaction topic (from the Interaction Topics form) to limit alerts received to only interactions about that topic. Key Value also can be left blank to receive all alerts about all topics. The subscriber's email Type must be set to Primary. | SyteLine users who respond to Vendor Portal
interactions In multi-site implementations, the user must be subscribed to this alert in the site for which they are responsible and in the primary site. |
SpecialPromotionsAnnouncements | An announcement or promotion was sent to you | Customer Portal users |
TaxCodeEvaluationAlert | A new user has been added on the portal and/or an order has been submitted, but there is no default tax code record associated with the user's ship-to address | SyteLine users |
TransactionAmountAlert | The amount of a transaction for a specified account is over the specified amount. Key Value 1 is the account number. Key Value 2 is the amount to which transactions should be limited. | Financial Controller mobile |
VendorDocumentUploadAlert | A vendor has uploaded a document using Vendor Portal, or an user has uploaded a vendor document using | SyteLine users who approve documents uploaded by other users or by vendors using Vendor Portal |
VPConsignedInvConsumptionAlert | The quantity on hand of a vendor consigned inventory item has been reduced through consumption or return to the vendor | Vendor Portal users |
VPConsignedInvLevelAlert | Vendor consigned inventory of an item has gone below the minimum or above the maximum value | Vendor Portal users |
VPCustomerInteractionAlert | SyteLine user has entered interaction text for subscribed Vendor Portal users | Vendor Portal users |
You can also create your own publications on the Publications form.
Publication Categories
Certain publications are intended for certain types of users. To help organize the publications for users, SyteLine provides some predefined categories. In most cases, these categories match the predefined mobile home pages. For example, there is a salesperson category that is used to organize publications that are available on the salesperson mobile home form.
You can create additional custom categories on the Publication Categories form.
Publication Subscribers
Users can subscribe to publications using the Publication Subscribers form. They can also subscribe from the SyteLine mobile Subscribe to Alerts page or from the customer or vendor portals.
If the user is also defined with the same PersonId or email address in Infor Ming.le and IFS, then the alerts for some of these publications can also be displayed in the Infor Ming.le Alerts panel. For more information, see the Infor SyteLine Configuration Guide for Infor Operating Service.
Using Publications for Alerts
Publications work with the Application Event system and optionally with other application forms to send email alerts to subscribed users when specific circumstances occur.
Use these forms to set up publications:
- Publication Categories: Use this form to create and manage publication categories. Some categories are predefined to be used with SyteLine Mobile.
- Publications: Use this form to create publications and associate them with publication categories. You can associate any number of categories with a single publication. You can also associate any number of publications with a single category. Some publications are predefined to be used with SyteLine Mobile.
- Publication Subscribers: This form links individual users to publications. Instead of using this form, mobile users can subscribe to publications from their mobile devices through the Subscribe to Alerts link on their mobile home page.
Key Values
Some publications allow you to enter key values when you subscribe. For example, the TransactionAmountAlert requires two key values: Key Value 1 holds the account number and Key Value 2 holds the amount to which transactions should be limited. Where they are required, the key values are listed in the table above. IF you leave a key value field blank, you will receive alerts for every matching event or transaction that occurs.
Another example: The DCShopFloorTransactionErrorAlert Key Value 1 defines how many errors must be generated before the user receives an alert. You specify a Key Value of 10. Then if 47 DC errors are generated, you receive 4 alerts, one for each batch of 10 errors. The remaining seven alerts do not generate an alert because they did not reach the specified amount. After three more errors are generated, a new alert is sent.
Enter a zero (0) in the Key Value field to suspend alerts from a publication. This lets you temporarily stop receiving alerts without having to unsubscribe from the publication.