Troubleshooting‎ > ‎

Supporting Walz Mailings

posted Oct 10, 2011, 9:50 AM by Greg Kent   [ updated Nov 8, 2011, 8:40 AM by Unknown user ]

There are three ServiceOrderTemplates utilized:

1.   Quandis Mailing - This is an individual mailing

2.   Quandis Batch Import (Inbound Batch) - mailings are sent from TMS system in a batch to in order to group them

3.   Quandis Mailing Fulfillment (Outbound Batch) - this is the process that submits eligible Quandis Mailings to Walz

 

There are two support scenarios:

 

1.   Check if Inbound Batch has invalid attachment and take appropriate action:

a.   If an attachment is invalid within an Inbound Batch, the Inbound Batch must be removed and the Outbound Batch order must be released

b.   If there was an issue accessing the mailing attachment but the attachment appears to be present the Outbound Batch order simply needs to be released

 

2.   Release Outbound Batch order – This will free up mailings associated with an Outbound Batch order

 

---

 

Scenario 1a – Determine if Inbound Batch has an invalid attachment

 

1.   Locate the failed Inbound Batch. This can be performed by viewing the failed Outbound Batch. Look under the notes section. If the batch failed due to an attachment access failure there will be a message inserted with text:

a.   Bad Attachment. ServiceOrderID: {x}; Attachment: 17244010.1191643.{Some Attachment Name}.pdf

 

b.   Navigate to Service Order x. Under attachments tab, click and open 17244010.1191643.{Some Attachment Name}.pdf. If you can view the PDF in a browser, the attachment exists and there was an issue accessing the attachment during run-time.  If you receive an error move to Scenaio 1b to remove the Inbound Batch

 

Scenario 1b – Remove Failed Inbound Batch

 

1.   From SQLMS, EXECUTE pQuandisMailingRemove @SourceBatchID={Failed Inbound Batch Service OrderID}

2.   The stored procedure will automatically make the ServiceOrder exempt from being in the next Outbound Batch by marking the ServiceOrder.Status = ‘Cancelled’

3.   The Stored Procedure will render 4 columns. Copy text in column 4 (statement to release Outbound Batch ) and move to Scenario 2. Note if there are multiple records each statement should refer to the same Outbound Batch ID.

4.   Add an entry into mailing fix log to note released batch. Ensure you note which batch had a failed attachment

5.   Send email to the support address associated with the file (Eg. Ets.support@quandis.com or fatms.support@quandis.com) indicating the failed AttachmentID (17244010.1191643.{Some Attachment Name}.pdf), FileName, ForeclosureID (Inbound Batch ServiceOrder.SourceObjectID).

 

Scenario 2: Release an Outbound Batch:

1.   Locate the Outbound Batch ServiceOrderID (Quandis Mailing Fulfillment SOID) . This can be found in the error report

2.   From SQLMS, execute EXECUTE pQuandisMailingRequeueBatch @BatchOrderID='{ServiceOrderID}'

a.   If no records are returned, move to step 5 below

3.   Four columns will be rendered with SQL Statements. Copy and execute the first 3 columns (1 – 3). Once complete repeat the process for column 4.

4.   Navigate to failed order from the website

5.   Remove failed DecisionStep ‘QMF Build Outbound File’. This will ensure the order no longer appears in error report

6.   Edit ServiceOrder. Set status = ‘Cancelled’

7.   Add an entry into mailing fix log to note released batch

---

Supporting Stored Procedures:

·         There are two stored procedures (based on active client) that can be executed from SQLMS to indicate if there are any aged mailings. This is another ad-hoc way to check if there are any stalled mailings.

 

o   rHeartbeatStalledMailingsETS

o   rHeartbeatStalledMailingsFATMS

Comments