Managing a Small Master List

Scenario

Lots of organisations do a lot of process work using some variation of what we call a MasterList. The simplest way to conceptualise this it to imagine an excel spreadsheet containing a large number of rows and a large number of columns, and this spreadsheet is passed around various people in the operations departments, some of whom update certain data in it and some of whom extract data from it to act on.

Implement an approval process for credits on invoices in CenterView, using the MasterList concept.

Solution:

• Create a merge stream to act as a MasterList, keyed off a unique identifier
• Create streams and/or file collectors to update the MasterList.
• Create a pull pipe linking the MasterList Stream to itself, with its date offsets set to -1, -1
• Every time the stream is run, the MasterList stream is recreated from the previous version of itself and the updates that happen via other streams.