The trace calculation function available in PAW, 3rd Party Tools, and generally via the REST API seems to be missing the ability to see the intermediate steps of a calculation, why is that? In perspectives trace calculation wouldn't only tell you the rule statement and the value, but also the intermediate steps the rule engine had to take to get there. The version of the trace function is missing this capability. Without being able to see how statements like Attribute References and Calculation Components resolve for a given given calculation makes it pretty useless.

Are there plans to bring the functionality on par with what everyone was used to?

------------------------------
Ryan Clapp
------------------------------

#PlanningAnalyticswithWatson

Hi Ryan,

I think what you are referring to is already in the REST API? Below is a screenshot in Arc, the first rule being "Payroll Taxes" that has 2 components (Salaries and a look up to Regional Assumptions). You can then drill into the components by clicking on the calculator icon, for example the Salaries components are in the second screenshot.



------------------------------
Tim Ryan - Cubewise
------------------------------

Original Message:
Sent: Thu July 09, 2020 03:37 PM
From: Ryan Clapp
Subject: Trace Calculation via REST API

The trace calculation function available in PAW, 3rd Party Tools, and generally via the REST API seems to be missing the ability to see the intermediate steps of a calculation, why is that? In perspectives trace calculation wouldn't only tell you the rule statement and the value, but also the intermediate steps the rule engine had to take to get there. The version of the trace function is missing this capability. Without being able to see how statements like Attribute References and Calculation Components resolve for a given given calculation makes it pretty useless.

Are there plans to bring the functionality on par with what everyone was used to?

------------------------------
Ryan Clapp
------------------------------

#PlanningAnalyticswithWatson

Interesting, I tested this in ARC and PAW and it doesn't seem to work. I traced a calculation and it only returned the rule and the value. Clicking on the hour glass only shows more of the rule. Might this be server version specific?



------------------------------
Ryan Clapp
------------------------------

Original Message:
Sent: Thu July 09, 2020 06:56 PM
From: Tim Ryan
Subject: Trace Calculation via REST API

Hi Ryan,

I think what you are referring to is already in the REST API? Below is a screenshot in Arc, the first rule being "Payroll Taxes" that has 2 components (Salaries and a look up to Regional Assumptions). You can then drill into the components by clicking on the calculator icon, for example the Salaries components are in the second screenshot.

------------------------------
Tim Ryan - Cubewise

Original Message:
Sent: Thu July 09, 2020 03:37 PM
From: Ryan Clapp
Subject: Trace Calculation via REST API

The trace calculation function available in PAW, 3rd Party Tools, and generally via the REST API seems to be missing the ability to see the intermediate steps of a calculation, why is that? In perspectives trace calculation wouldn't only tell you the rule statement and the value, but also the intermediate steps the rule engine had to take to get there. The version of the trace function is missing this capability. Without being able to see how statements like Attribute References and Calculation Components resolve for a given given calculation makes it pretty useless.

Are there plans to bring the functionality on par with what everyone was used to?

------------------------------
Ryan Clapp
------------------------------

#PlanningAnalyticswithWatson

It could be related to version, I am running the latest 2.0.9.1.

------------------------------
Tim Ryan - Cubewise
------------------------------

Original Message:
Sent: Thu July 09, 2020 07:03 PM
From: Ryan Clapp
Subject: Trace Calculation via REST API

Interesting, I tested this in ARC and PAW and it doesn't seem to work. I traced a calculation and it only returned the rule and the value. Clicking on the hour glass only shows more of the rule. Might this be server version specific?

------------------------------
Ryan Clapp

Original Message:
Sent: Thu July 09, 2020 06:56 PM
From: Tim Ryan
Subject: Trace Calculation via REST API

Hi Ryan,

I think what you are referring to is already in the REST API? Below is a screenshot in Arc, the first rule being "Payroll Taxes" that has 2 components (Salaries and a look up to Regional Assumptions). You can then drill into the components by clicking on the calculator icon, for example the Salaries components are in the second screenshot.

------------------------------
Tim Ryan - Cubewise

Original Message:
Sent: Thu July 09, 2020 03:37 PM
From: Ryan Clapp
Subject: Trace Calculation via REST API

The trace calculation function available in PAW, 3rd Party Tools, and generally via the REST API seems to be missing the ability to see the intermediate steps of a calculation, why is that? In perspectives trace calculation wouldn't only tell you the rule statement and the value, but also the intermediate steps the rule engine had to take to get there. The version of the trace function is missing this capability. Without being able to see how statements like Attribute References and Calculation Components resolve for a given given calculation makes it pretty useless.

Are there plans to bring the functionality on par with what everyone was used to?

------------------------------
Ryan Clapp
------------------------------

#PlanningAnalyticswithWatson

Original Message:
Sent: 7/9/2020 8:24:00 PM
From: Tim Ryan
Subject: RE: Trace Calculation via REST API

It could be related to version, I am running the latest 2.0.9.1.

------------------------------
Tim Ryan - Cubewise
------------------------------

Original Message:
Sent: Thu July 09, 2020 07:03 PM
From: Ryan Clapp
Subject: Trace Calculation via REST API

Interesting, I tested this in ARC and PAW and it doesn't seem to work. I traced a calculation and it only returned the rule and the value. Clicking on the hour glass only shows more of the rule. Might this be server version specific?

------------------------------
Ryan Clapp

Original Message:
Sent: Thu July 09, 2020 06:56 PM
From: Tim Ryan
Subject: Trace Calculation via REST API

Hi Ryan,

I think what you are referring to is already in the REST API? Below is a screenshot in Arc, the first rule being "Payroll Taxes" that has 2 components (Salaries and a look up to Regional Assumptions). You can then drill into the components by clicking on the calculator icon, for example the Salaries components are in the second screenshot.

------------------------------
Tim Ryan - Cubewise

Original Message:
Sent: Thu July 09, 2020 03:37 PM
From: Ryan Clapp
Subject: Trace Calculation via REST API

The trace calculation function available in PAW, 3rd Party Tools, and generally via the REST API seems to be missing the ability to see the intermediate steps of a calculation, why is that? In perspectives trace calculation wouldn't only tell you the rule statement and the value, but also the intermediate steps the rule engine had to take to get there. The version of the trace function is missing this capability. Without being able to see how statements like Attribute References and Calculation Components resolve for a given given calculation makes it pretty useless.

Are there plans to bring the functionality on par with what everyone was used to?

------------------------------
Ryan Clapp
------------------------------

#PlanningAnalyticswithWatson

IBM acknowledged this is a defect.

Severity 2 APAR PH27619 TRACE CALCULATION PERFORMED USING REST API RETRIEVES BLANK STATEMENTS.

------------------------------
Ryan Clapp
------------------------------

Original Message:
Sent: Thu July 09, 2020 03:37 PM
From: Ryan Clapp
Subject: Trace Calculation via REST API

The trace calculation function available in PAW, 3rd Party Tools, and generally via the REST API seems to be missing the ability to see the intermediate steps of a calculation, why is that? In perspectives trace calculation wouldn't only tell you the rule statement and the value, but also the intermediate steps the rule engine had to take to get there. The version of the trace function is missing this capability. Without being able to see how statements like Attribute References and Calculation Components resolve for a given given calculation makes it pretty useless.

Are there plans to bring the functionality on par with what everyone was used to?

------------------------------
Ryan Clapp
------------------------------

#PlanningAnalyticswithWatson