Page 1 of 1
Naming conventions on filters (AuditStage)
Posted: Wed Mar 21, 2007 9:07 am
by Eulderma
Hi,
Has anyone experience with naming conventions and best practices regarding filter names in AuditStage?
If so, can you share this?
Thanks in advance.
Posted: Wed Mar 21, 2007 9:24 am
by jhmckeever
Hi Eulderma,
We chose to use a format like 'DATASOURCE.Text Description'.
E.g.
Code: Select all
ACCOUNTS.Mismatch to Meter_Grps
ACCOUNTS.No live mandate for live DD
ACCOUNTS.Billing suspension date not null
AGREEMENTS.AGRMT_CUST_NAME is null
AGREEMENTS.Invalid price for SME
AGREEMENTS.No price line for CORPORATE
etc.
I'm not sure this is reflective of any 'Best Practice' but it worked well for us. In hindsight we may have also built in a Business Rule Reference Number such as ...
E.g.
Code: Select all
ACCOUNTS.B132.Mismatch to Meter_Grps
ACCOUNTS.B029.No live mandate for live DD
ACCOUNTS.X033.Billing suspension date not null
AGREEMENTS.B034.AGRMT_CUST_NAME is null
AGREEMENTS.B199.Invalid price for SME
AGREEMENTS.X043.No price line for CORPORATE
etc.
HTH,
John.
Posted: Thu Jul 05, 2007 12:01 am
by Eulderma
We named the filters via uniques numbering and a description that came closest to the business rule.
Example
00.1.1 Validate customer name similarity