Hi,
Has anyone experience with naming conventions and best practices regarding filter names in AuditStage?
If so, can you share this?
Thanks in advance.
Naming conventions on filters (AuditStage)
-
- Premium Member
- Posts: 301
- Joined: Thu Jul 14, 2005 10:27 am
- Location: Melbourne, Australia
- Contact:
Hi Eulderma,
We chose to use a format like 'DATASOURCE.Text Description'.
E.g.
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.
HTH,
John.
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.
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.
John.
<b>John McKeever</b>
Data Migrators
<b><a href="https://www.mettleci.com">MettleCI</a> - DevOps for DataStage</b>
<a href="http://www.datamigrators.com/"><img src="https://www.datamigrators.com/assets/im ... l.png"></a>
Data Migrators
<b><a href="https://www.mettleci.com">MettleCI</a> - DevOps for DataStage</b>
<a href="http://www.datamigrators.com/"><img src="https://www.datamigrators.com/assets/im ... l.png"></a>