Warning
WARNING: The TrackAbout MetaWiki has been deprecated and is no longer being updated.

Please visit our new TrackAbout Knowledge Base at https://supportkb.trackabout.com for the most-up-to-date documentation on TrackAbout and TrackAbout Mobile.

Linked Exchange - Recipient Queue

From TrackAbout MetaWiki
Revision as of 13:23, 23 April 2009 by Sangelo (talk | contribs)
Jump to navigation Jump to search

The recipient queue shows a list of all messages that have been recieved from any Linked Exchange partners.

Linked Exchange Recipient Queue
There are several filters available to limit the messages that are shown and allow users to narrow down the queue to view what they want to see.:

  • Start Date
  • End Date
  • Partner
  • Status

All partners that have a valid Linked Exchange relationship (active and verified) will show in the list of partners. Messages go through the following statuses:

  1. Pending: This is the initial status of the message when it is initially received. There is a background process that runs periodically, checking for and processing new messages.
  2. Processed: Once a message has successfully been processed, it is moved into this status. Consider this to be successful.
  3. Missing Mappings: When a message is received and has customer, location or product code that is not mapped in the recipient database, it will be marked as missing mappings. While the message can be retried manually, the soluition is to complete the mappings, and the message will be retried automatically.
  4. Failed: When there is a problem processing the message, it is moved into this status. An email message should be sent to the email addresses specified in the partnership setup detailing the error. Messages in this status can be retried.
  5. Pending Retry: When a user retries a missing mapping message or a failed message, it is put into this status. The automated process will pick these messages up and retry them during the next interval.

The queue also shows some basic information about the message that was received: the customer mapped to the message's location, the number of assets on the record, and the action that triggered the message.