Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Summary / TL:DR: For monthly publications that are mailed to customers, affiliates will request issue pulls to be manually run monthly.  Use these instructions to setup a manual issue pull. 

...

CIR420 Initializes the select and places it in a table\buffer (will need to look for that table).
CIR430 reassigned the customers to the updated select.

Do NOT Run Cycle End / Issue Pull Jobstream Twice (See Step 4)

If you run the jobstream and the client says the CIR441 report is incorrect, do not run the issue pull jobstream again. The cycle end processes will decrement the customer issues to go. 

...

Table of Contents
minLevel12
maxLevel7

...

What you Need

When requesting an issue pull, here is what is necessary to have:

...

  1. Go to the Operations folder on the network (\\maui\AdvProd\PubProd\reports\operations)

  2. Locate and open the correct folder.  Folders are organized by year and month, for example 07/17 would be the 1707 folder.

  3. Locate and open the folder for the day the process ran

  4. Search for the CIR441 report.  The report can be found by searching by CIR441_ = pub code (for example CIR441_LD1)

  5. Drag and drop the file into the attachments section of the support ticket and add a public comment to the ticket for the affiliate letting them know the counts are attached to the ticket.

HOW TO RE-RUN AN ISSUE PULL

Do NOT Re-Submit the Issue Pull Jobstream. The Cycle End processes will decrement the customers' remaining issues-to-go twice in the same time period. 

...