Currently we create entirely new notices for SLIP type notices when really they're just a different medium and thus should be a message transport type. I propose adding a SLIP message transport type and where appropriate merging the current SLIP notices into their corresponding non-slip counterparts. A 'slip' is just a small form printer and likely to have similar summary detail as an SMS for example.
This would also make it clearer when SlipCSS and NoticeCSS should be used.
These are the slips listed as slips in my devbox: Current Code Transport New Code ACCOUNT_SUMMARY print ACCOUNT_SUMMARY AR_SLIP print AR_NEW CHECKINSLIP print CHECKIN HOLD_SLIP email HOLD ISSUEQSLIP email CHECKOUTS OVERDUES_SLIP print ODUE (/first OD notice if different?) PRES_TRAIN_ITEM print -> This doesn't have a corresponding email notice, so we could change this to slip transport type TRANSFERSLIP email-> This doesn't have a corresponding email notice, so we could change this to slip transport type ISSUESLIP email -> -> This doesn't have a corresponding email notice, so we could change this to slip transport type SR_SLIP email -> (This looks like it's more an email than a slip?)