-
Notifications
You must be signed in to change notification settings - Fork 3
Email: Subject More LabWorks Info
Also.... in both the Development AND the Production databases, I have placed 2 new Test Codes: • PROC — Processing Fee, the once per Work Request value • SETUP — Setup Fee, the once or more per Test value Hope that helps. -David
On Tue, Aug 29, 2017 at 3:35 PM, David Benning [email protected] wrote: Ok....
Here are some better Work Request Numbers to try. They are all in the Development Server Database.
• UC Clients o 17P142 — $896.00 o 17P063 — RUSH — $1890.00 o 17P165 — RUSH — $210.00 o 17P166 — $360.00
• External Clients o 17M074 — RUSH — $802.50 o 17M096 — RUSH — $378.00 o 17P167 — $1518.00 o 17P168 — $1392.00 o 17P171 — $3864.00
Also... I told you the wrong table to look up RUSH — It is in SUERFLDS. (I left the "S" off the Table name which is a legitimate table with similar column names but is meant to define the DEFAULT login scenario for a CLIENT. SUERFLDS describes the individual cases for each work request.
• Where Rush lives in the database o SUSERFLDS.RUSHYNP — N, 1, 1.5 N means price as normally calculated 1 means it's a rush but no additional charge 1.5 means it's a rush and it is 1.5 x more costly o SUSERFLDS.RUSHDC — the date that the Rush is promised by o
Let's see if that works better!