Does anyone have any suggestions on how to build dynamic business rules into
a DataStage XE job? We have a requirement that the business rules to
calculate a field can change over time and by country. In addition, the
customer can send updates to historical data, in which case the process
would need to apply the correct business rule. It also needs to be dynamic,
in that the customer can change the rules at any time, without changes to
the job itself.
Any thoughts would be greatly appreciated.
John
Dynamic Business Rules
Dynamic Business Rules
<b>PLEASE READ</b>
Do not contact admin unless you have technical support or account questions. Do not send email or Private Messages about discussion topics to ADMIN. Contact the webmaster concerning abusive or offensive posts.
Do not contact admin unless you have technical support or account questions. Do not send email or Private Messages about discussion topics to ADMIN. Contact the webmaster concerning abusive or offensive posts.
Dynamic Business Rules
The *only* way you are going to accomplish something like this - regardless
of the tool - is to have all of your "business rules" table driven. Sounds
like they'll need to be effective dated as well if I read your "updates to
historical data" part correctly.
The hardest part will be in digesting all of the business rules and turning
that into a set of tables that can be used to support them. After that,
writing the job should be *fairly* straight-forward, I would think. Then all
that's left is the fun of maintaining the tables.
-craig
-----Original Message-----
From: Reedy, John [mailto:john.reedy@eds.com]
Sent: Wednesday, December 03, 2003 6:08 AM
To: datastage-users@oliver.com
Subject: Dynamic Business Rules
Does anyone have any suggestions on how to build dynamic business rules into
a DataStage XE job? We have a requirement that the business rules to
calculate a field can change over time and by country. In addition, the
customer can send updates to historical data, in which case the process
would need to apply the correct business rule. It also needs to be dynamic,
in that the customer can change the rules at any time, without changes to
the job itself.
Any thoughts would be greatly appreciated.
John
of the tool - is to have all of your "business rules" table driven. Sounds
like they'll need to be effective dated as well if I read your "updates to
historical data" part correctly.
The hardest part will be in digesting all of the business rules and turning
that into a set of tables that can be used to support them. After that,
writing the job should be *fairly* straight-forward, I would think. Then all
that's left is the fun of maintaining the tables.
-craig
-----Original Message-----
From: Reedy, John [mailto:john.reedy@eds.com]
Sent: Wednesday, December 03, 2003 6:08 AM
To: datastage-users@oliver.com
Subject: Dynamic Business Rules
Does anyone have any suggestions on how to build dynamic business rules into
a DataStage XE job? We have a requirement that the business rules to
calculate a field can change over time and by country. In addition, the
customer can send updates to historical data, in which case the process
would need to apply the correct business rule. It also needs to be dynamic,
in that the customer can change the rules at any time, without changes to
the job itself.
Any thoughts would be greatly appreciated.
John
<b>PLEASE READ</b>
Do not contact admin unless you have technical support or account questions. Do not send email or Private Messages about discussion topics to ADMIN. Contact the webmaster concerning abusive or offensive posts.
Do not contact admin unless you have technical support or account questions. Do not send email or Private Messages about discussion topics to ADMIN. Contact the webmaster concerning abusive or offensive posts.
Dynamic Business Rules
How about deploying re-usable transforms or routines using case
statements. Therefore, it you call a calculation in numerous jobs and
if your calculation changes, you just have to change the calculation in
one place.
Per Craig's comment, I like to use a "conversion table" to house all my
conversions/translation from old codes/values to new codes/values. I
have also used a similar table to house groupings .... Ex financial
account rollups.
I hope that this helps,
Tim
-----Original Message-----
From: Craig Hulett [mailto:Craig.Hulett@comcast.net]
Sent: Wednesday, December 03, 2003 2:29 PM
To: datastage-users@oliver.com
Subject: RE: Dynamic Business Rules
The *only* way you are going to accomplish something like this -
regardless of the tool - is to have all of your "business rules" table
driven. Sounds like they'll need to be effective dated as well if I read
your "updates to historical data" part correctly.
The hardest part will be in digesting all of the business rules and
turning that into a set of tables that can be used to support them.
After that, writing the job should be *fairly* straight-forward, I would
think. Then all that's left is the fun of maintaining the tables.
-craig
-----Original Message-----
From: Reedy, John [mailto:john.reedy@eds.com]
Sent: Wednesday, December 03, 2003 6:08 AM
To: datastage-users@oliver.com
Subject: Dynamic Business Rules
Does anyone have any suggestions on how to build dynamic business rules
into a DataStage XE job? We have a requirement that the business rules
to calculate a field can change over time and by country. In addition,
the customer can send updates to historical data, in which case the
process would need to apply the correct business rule. It also needs to
be dynamic, in that the customer can change the rules at any time,
without changes to the job itself.
Any thoughts would be greatly appreciated.
John
statements. Therefore, it you call a calculation in numerous jobs and
if your calculation changes, you just have to change the calculation in
one place.
Per Craig's comment, I like to use a "conversion table" to house all my
conversions/translation from old codes/values to new codes/values. I
have also used a similar table to house groupings .... Ex financial
account rollups.
I hope that this helps,
Tim
-----Original Message-----
From: Craig Hulett [mailto:Craig.Hulett@comcast.net]
Sent: Wednesday, December 03, 2003 2:29 PM
To: datastage-users@oliver.com
Subject: RE: Dynamic Business Rules
The *only* way you are going to accomplish something like this -
regardless of the tool - is to have all of your "business rules" table
driven. Sounds like they'll need to be effective dated as well if I read
your "updates to historical data" part correctly.
The hardest part will be in digesting all of the business rules and
turning that into a set of tables that can be used to support them.
After that, writing the job should be *fairly* straight-forward, I would
think. Then all that's left is the fun of maintaining the tables.
-craig
-----Original Message-----
From: Reedy, John [mailto:john.reedy@eds.com]
Sent: Wednesday, December 03, 2003 6:08 AM
To: datastage-users@oliver.com
Subject: Dynamic Business Rules
Does anyone have any suggestions on how to build dynamic business rules
into a DataStage XE job? We have a requirement that the business rules
to calculate a field can change over time and by country. In addition,
the customer can send updates to historical data, in which case the
process would need to apply the correct business rule. It also needs to
be dynamic, in that the customer can change the rules at any time,
without changes to the job itself.
Any thoughts would be greatly appreciated.
John
<b>PLEASE READ</b>
Do not contact admin unless you have technical support or account questions. Do not send email or Private Messages about discussion topics to ADMIN. Contact the webmaster concerning abusive or offensive posts.
Do not contact admin unless you have technical support or account questions. Do not send email or Private Messages about discussion topics to ADMIN. Contact the webmaster concerning abusive or offensive posts.
Dynamic Business Rules
The customer needs to be able to be changed the calculation without the
involvement a developer; so, that probably means it needs to be table
driven. We will probably be using the latest release of DataStage(server
version). Can you call an external Java program, passing necessary
variables and returning the results to the DataStage Job?
-----Original Message-----
From: Timothy Walsh [mailto:Tim.Walsh@york.com]
Sent: Wednesday, December 03, 2003 8:44 AM
To: datastage-users@oliver.com
Subject: RE: Dynamic Business Rules
How about deploying re-usable transforms or routines using case statements.
Therefore, it you call a calculation in numerous jobs and if your
calculation changes, you just have to change the calculation in one place.
Per Craig's comment, I like to use a "conversion table" to house all my
conversions/translation from old codes/values to new codes/values. I have
also used a similar table to house groupings .... Ex financial account
rollups.
I hope that this helps,
Tim
-----Original Message-----
From: Craig Hulett [mailto:Craig.Hulett@comcast.net]
Sent: Wednesday, December 03, 2003 2:29 PM
To: datastage-users@oliver.com
Subject: RE: Dynamic Business Rules
The *only* way you are going to accomplish something like this - regardless
of the tool - is to have all of your "business rules" table driven. Sounds
like they'll need to be effective dated as well if I read your "updates to
historical data" part correctly.
The hardest part will be in digesting all of the business rules and turning
that into a set of tables that can be used to support them. After that,
writing the job should be *fairly* straight-forward, I would think. Then all
that's left is the fun of maintaining the tables.
-craig
-----Original Message-----
From: Reedy, John [mailto:john.reedy@eds.com]
Sent: Wednesday, December 03, 2003 6:08 AM
To: datastage-users@oliver.com
Subject: Dynamic Business Rules
Does anyone have any suggestions on how to build dynamic business rules into
a DataStage XE job? We have a requirement that the business rules to
calculate a field can change over time and by country. In addition, the
customer can send updates to historical data, in which case the process
would need to apply the correct business rule. It also needs to be dynamic,
in that the customer can change the rules at any time, without changes to
the job itself.
Any thoughts would be greatly appreciated.
John
involvement a developer; so, that probably means it needs to be table
driven. We will probably be using the latest release of DataStage(server
version). Can you call an external Java program, passing necessary
variables and returning the results to the DataStage Job?
-----Original Message-----
From: Timothy Walsh [mailto:Tim.Walsh@york.com]
Sent: Wednesday, December 03, 2003 8:44 AM
To: datastage-users@oliver.com
Subject: RE: Dynamic Business Rules
How about deploying re-usable transforms or routines using case statements.
Therefore, it you call a calculation in numerous jobs and if your
calculation changes, you just have to change the calculation in one place.
Per Craig's comment, I like to use a "conversion table" to house all my
conversions/translation from old codes/values to new codes/values. I have
also used a similar table to house groupings .... Ex financial account
rollups.
I hope that this helps,
Tim
-----Original Message-----
From: Craig Hulett [mailto:Craig.Hulett@comcast.net]
Sent: Wednesday, December 03, 2003 2:29 PM
To: datastage-users@oliver.com
Subject: RE: Dynamic Business Rules
The *only* way you are going to accomplish something like this - regardless
of the tool - is to have all of your "business rules" table driven. Sounds
like they'll need to be effective dated as well if I read your "updates to
historical data" part correctly.
The hardest part will be in digesting all of the business rules and turning
that into a set of tables that can be used to support them. After that,
writing the job should be *fairly* straight-forward, I would think. Then all
that's left is the fun of maintaining the tables.
-craig
-----Original Message-----
From: Reedy, John [mailto:john.reedy@eds.com]
Sent: Wednesday, December 03, 2003 6:08 AM
To: datastage-users@oliver.com
Subject: Dynamic Business Rules
Does anyone have any suggestions on how to build dynamic business rules into
a DataStage XE job? We have a requirement that the business rules to
calculate a field can change over time and by country. In addition, the
customer can send updates to historical data, in which case the process
would need to apply the correct business rule. It also needs to be dynamic,
in that the customer can change the rules at any time, without changes to
the job itself.
Any thoughts would be greatly appreciated.
John
<b>PLEASE READ</b>
Do not contact admin unless you have technical support or account questions. Do not send email or Private Messages about discussion topics to ADMIN. Contact the webmaster concerning abusive or offensive posts.
Do not contact admin unless you have technical support or account questions. Do not send email or Private Messages about discussion topics to ADMIN. Contact the webmaster concerning abusive or offensive posts.
Dynamic Business Rules
If you are going to use Java, you can just as easily use a DS
Routine(s). Then, your code is contained within the realm on DataStage.
Make maintenance and migrations easier .... or at least that's my
opinion.
-----Original Message-----
From: Reedy, John [mailto:john.reedy@eds.com]
Sent: Wednesday, December 03, 2003 3:15 PM
To: 'datastage-users@oliver.com'
Subject: RE: Dynamic Business Rules
The customer needs to be able to be changed the calculation without the
involvement a developer; so, that probably means it needs to be table
driven. We will probably be using the latest release of
DataStage(server version). Can you call an external Java program,
passing necessary variables and returning the results to the DataStage
Job?
-----Original Message-----
From: Timothy Walsh [mailto:Tim.Walsh@york.com]
Sent: Wednesday, December 03, 2003 8:44 AM
To: datastage-users@oliver.com
Subject: RE: Dynamic Business Rules
How about deploying re-usable transforms or routines using case
statements. Therefore, it you call a calculation in numerous jobs and if
your calculation changes, you just have to change the calculation in one
place.
Per Craig's comment, I like to use a "conversion table" to house all my
conversions/translation from old codes/values to new codes/values. I
have also used a similar table to house groupings .... Ex financial
account rollups.
I hope that this helps,
Tim
-----Original Message-----
From: Craig Hulett [mailto:Craig.Hulett@comcast.net]
Sent: Wednesday, December 03, 2003 2:29 PM
To: datastage-users@oliver.com
Subject: RE: Dynamic Business Rules
The *only* way you are going to accomplish something like this -
regardless of the tool - is to have all of your "business rules" table
driven. Sounds like they'll need to be effective dated as well if I read
your "updates to historical data" part correctly.
The hardest part will be in digesting all of the business rules and
turning that into a set of tables that can be used to support them.
After that, writing the job should be *fairly* straight-forward, I would
think. Then all that's left is the fun of maintaining the tables.
-craig
-----Original Message-----
From: Reedy, John [mailto:john.reedy@eds.com]
Sent: Wednesday, December 03, 2003 6:08 AM
To: datastage-users@oliver.com
Subject: Dynamic Business Rules
Does anyone have any suggestions on how to build dynamic business rules
into a DataStage XE job? We have a requirement that the business rules
to calculate a field can change over time and by country. In addition,
the customer can send updates to historical data, in which case the
process would need to apply the correct business rule. It also needs to
be dynamic, in that the customer can change the rules at any time,
without changes to the job itself.
Any thoughts would be greatly appreciated.
John
Routine(s). Then, your code is contained within the realm on DataStage.
Make maintenance and migrations easier .... or at least that's my
opinion.
-----Original Message-----
From: Reedy, John [mailto:john.reedy@eds.com]
Sent: Wednesday, December 03, 2003 3:15 PM
To: 'datastage-users@oliver.com'
Subject: RE: Dynamic Business Rules
The customer needs to be able to be changed the calculation without the
involvement a developer; so, that probably means it needs to be table
driven. We will probably be using the latest release of
DataStage(server version). Can you call an external Java program,
passing necessary variables and returning the results to the DataStage
Job?
-----Original Message-----
From: Timothy Walsh [mailto:Tim.Walsh@york.com]
Sent: Wednesday, December 03, 2003 8:44 AM
To: datastage-users@oliver.com
Subject: RE: Dynamic Business Rules
How about deploying re-usable transforms or routines using case
statements. Therefore, it you call a calculation in numerous jobs and if
your calculation changes, you just have to change the calculation in one
place.
Per Craig's comment, I like to use a "conversion table" to house all my
conversions/translation from old codes/values to new codes/values. I
have also used a similar table to house groupings .... Ex financial
account rollups.
I hope that this helps,
Tim
-----Original Message-----
From: Craig Hulett [mailto:Craig.Hulett@comcast.net]
Sent: Wednesday, December 03, 2003 2:29 PM
To: datastage-users@oliver.com
Subject: RE: Dynamic Business Rules
The *only* way you are going to accomplish something like this -
regardless of the tool - is to have all of your "business rules" table
driven. Sounds like they'll need to be effective dated as well if I read
your "updates to historical data" part correctly.
The hardest part will be in digesting all of the business rules and
turning that into a set of tables that can be used to support them.
After that, writing the job should be *fairly* straight-forward, I would
think. Then all that's left is the fun of maintaining the tables.
-craig
-----Original Message-----
From: Reedy, John [mailto:john.reedy@eds.com]
Sent: Wednesday, December 03, 2003 6:08 AM
To: datastage-users@oliver.com
Subject: Dynamic Business Rules
Does anyone have any suggestions on how to build dynamic business rules
into a DataStage XE job? We have a requirement that the business rules
to calculate a field can change over time and by country. In addition,
the customer can send updates to historical data, in which case the
process would need to apply the correct business rule. It also needs to
be dynamic, in that the customer can change the rules at any time,
without changes to the job itself.
Any thoughts would be greatly appreciated.
John
<b>PLEASE READ</b>
Do not contact admin unless you have technical support or account questions. Do not send email or Private Messages about discussion topics to ADMIN. Contact the webmaster concerning abusive or offensive posts.
Do not contact admin unless you have technical support or account questions. Do not send email or Private Messages about discussion topics to ADMIN. Contact the webmaster concerning abusive or offensive posts.
Dynamic Business Rules
Yes! This works very well, but you will need the java pack.
-----Original Message-----
From: Reedy, John [mailto:john.reedy@eds.com]
Sent: Wednesday, December 03, 2003 8:15 AM
To: 'datastage-users@oliver.com'
Subject: RE: Dynamic Business Rules
The customer needs to be able to be changed the calculation without the
involvement a developer; so, that probably means it needs to be table
driven. We will probably be using the latest release of DataStage(server
version). Can you call an external Java program, passing necessary
variables and returning the results to the DataStage Job?
-----Original Message-----
From: Timothy Walsh [mailto:Tim.Walsh@york.com]
Sent: Wednesday, December 03, 2003 8:44 AM
To: datastage-users@oliver.com
Subject: RE: Dynamic Business Rules
How about deploying re-usable transforms or routines using case statements.
Therefore, it you call a calculation in numerous jobs and if your
calculation changes, you just have to change the calculation in one place.
Per Craig's comment, I like to use a "conversion table" to house all my
conversions/translation from old codes/values to new codes/values. I have
also used a similar table to house groupings .... Ex financial account
rollups.
I hope that this helps,
Tim
-----Original Message-----
From: Craig Hulett [mailto:Craig.Hulett@comcast.net]
Sent: Wednesday, December 03, 2003 2:29 PM
To: datastage-users@oliver.com
Subject: RE: Dynamic Business Rules
The *only* way you are going to accomplish something like this - regardless
of the tool - is to have all of your "business rules" table driven. Sounds
like they'll need to be effective dated as well if I read your "updates to
historical data" part correctly.
The hardest part will be in digesting all of the business rules and turning
that into a set of tables that can be used to support them. After that,
writing the job should be *fairly* straight-forward, I would think. Then all
that's left is the fun of maintaining the tables.
-craig
-----Original Message-----
From: Reedy, John [mailto:john.reedy@eds.com]
Sent: Wednesday, December 03, 2003 6:08 AM
To: datastage-users@oliver.com
Subject: Dynamic Business Rules
Does anyone have any suggestions on how to build dynamic business rules into
a DataStage XE job? We have a requirement that the business rules to
calculate a field can change over time and by country. In addition, the
customer can send updates to historical data, in which case the process
would need to apply the correct business rule. It also needs to be dynamic,
in that the customer can change the rules at any time, without changes to
the job itself.
Any thoughts would be greatly appreciated.
John
-----Original Message-----
From: Reedy, John [mailto:john.reedy@eds.com]
Sent: Wednesday, December 03, 2003 8:15 AM
To: 'datastage-users@oliver.com'
Subject: RE: Dynamic Business Rules
The customer needs to be able to be changed the calculation without the
involvement a developer; so, that probably means it needs to be table
driven. We will probably be using the latest release of DataStage(server
version). Can you call an external Java program, passing necessary
variables and returning the results to the DataStage Job?
-----Original Message-----
From: Timothy Walsh [mailto:Tim.Walsh@york.com]
Sent: Wednesday, December 03, 2003 8:44 AM
To: datastage-users@oliver.com
Subject: RE: Dynamic Business Rules
How about deploying re-usable transforms or routines using case statements.
Therefore, it you call a calculation in numerous jobs and if your
calculation changes, you just have to change the calculation in one place.
Per Craig's comment, I like to use a "conversion table" to house all my
conversions/translation from old codes/values to new codes/values. I have
also used a similar table to house groupings .... Ex financial account
rollups.
I hope that this helps,
Tim
-----Original Message-----
From: Craig Hulett [mailto:Craig.Hulett@comcast.net]
Sent: Wednesday, December 03, 2003 2:29 PM
To: datastage-users@oliver.com
Subject: RE: Dynamic Business Rules
The *only* way you are going to accomplish something like this - regardless
of the tool - is to have all of your "business rules" table driven. Sounds
like they'll need to be effective dated as well if I read your "updates to
historical data" part correctly.
The hardest part will be in digesting all of the business rules and turning
that into a set of tables that can be used to support them. After that,
writing the job should be *fairly* straight-forward, I would think. Then all
that's left is the fun of maintaining the tables.
-craig
-----Original Message-----
From: Reedy, John [mailto:john.reedy@eds.com]
Sent: Wednesday, December 03, 2003 6:08 AM
To: datastage-users@oliver.com
Subject: Dynamic Business Rules
Does anyone have any suggestions on how to build dynamic business rules into
a DataStage XE job? We have a requirement that the business rules to
calculate a field can change over time and by country. In addition, the
customer can send updates to historical data, in which case the process
would need to apply the correct business rule. It also needs to be dynamic,
in that the customer can change the rules at any time, without changes to
the job itself.
Any thoughts would be greatly appreciated.
John
<b>PLEASE READ</b>
Do not contact admin unless you have technical support or account questions. Do not send email or Private Messages about discussion topics to ADMIN. Contact the webmaster concerning abusive or offensive posts.
Do not contact admin unless you have technical support or account questions. Do not send email or Private Messages about discussion topics to ADMIN. Contact the webmaster concerning abusive or offensive posts.