Skip to main content

This content is closed to future replies and is no longer being maintained or updated.
Links may no longer function. If you have a similar request, please write a new post.

Question

 PRADEEP CHOWDARY PYDI (PradeepPydi)
Anthem
Senior PEGA DEVOPS and Cloud Administrator
Anthem
US
PradeepPydi Member since 2017 240 posts
Anthem
Posted: Nov 7, 2017
Last activity: Jan 29, 2018
Posted: 7 Nov 2017 16:10 EST
Last activity: 29 Jan 2018 8:35 EST
Closed
Solved

Decimal defined Property type values are getting converted to HexaDecimal values in the Clipboard after the upgrade to PEGA 7.3 from PEGA 7.2.2.

Hi,

Decimal defined Property type values are getting converted to HexaDecimal values in the Clipboard after the upgrade to PEGA 7.3 from PEGA 7.2.2.
Please find the attachment for the logs.

Regards,
Pradeep P.

***Moderator Edit: Vidyaranjan | Updated SR details***

To see attachments, please log in.
Installation and Deployment
Updates
Support Case Parallel

Accepted Solution

Posted: 7 years ago
Posted: 29 Nov 2017 15:31 EST
Sibasis Mohanty (_SibasisMohanty)
PEGA

Pegasystems Inc.

Pega parses all values received from service as text and the values are mapped to clipboard based on property type on Pega side. In previous Pega versions when integer values were mapped to deicmal properties on clipboard they were still represented as integer values (and not deimal value) due to a bug in Pega which is fixed in Pega 7.3 causing the reported change in behavior. These code changes were implemented as part of newer assembler. You can set the below DSS to continue using the old behavior:
Purpose : SwitchToOldAssembler
Owning Ruleset : Pega-IntegrationEngine
Value : true

To see attachments, please log in.
Posted: 7 years ago
Posted: 8 Nov 2017 0:50 EST
Ujjwal Kumar Shukla (UjjwalShukla_GCS)
PEGA
Senior Manager, Technical Support
Pegasystems Inc.
IN

Hi Pradeep,

Hope you are doing good!!

Could you please check for the values in DB, If the Property is not exposed could you run a report definition or refer the property in section to see how it behaves.

Could you also do obj Open by handle to open one of the instance and print the values in logs to check if it is still Hexadecimal.
Please send us the screen shots of the issue and any configuration if applicable.

Regards,
Ujjwal

To see attachments, please log in.

Accepted Solution

Posted: 7 years ago
Posted: 29 Nov 2017 15:31 EST
Sibasis Mohanty (_SibasisMohanty)
PEGA

Pegasystems Inc.

Pega parses all values received from service as text and the values are mapped to clipboard based on property type on Pega side. In previous Pega versions when integer values were mapped to deicmal properties on clipboard they were still represented as integer values (and not deimal value) due to a bug in Pega which is fixed in Pega 7.3 causing the reported change in behavior. These code changes were implemented as part of newer assembler. You can set the below DSS to continue using the old behavior:
Purpose : SwitchToOldAssembler
Owning Ruleset : Pega-IntegrationEngine
Value : true

To see attachments, please log in.
Posted: 7 years ago
Posted: 29 Jan 2018 8:35 EST
karamjeet kahlon (karamjeetk6459)
Charles Schwab & Company Inc

Charles Schwab & Company Inc
US

This resolved the issue in Pega 7.3 too. Looks like fix is not yet in 7.3 also.

set the below DSS to continue using the old behavior:
Purpose : SwitchToOldAssembler
Owning Ruleset : Pega-IntegrationEngine
Value : true

To see attachments, please log in.

We'd prefer it if you saw us at our best.

Pega Collaboration Center has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice