Hi,

There is one option of using "refactor" (Designer Studio>System>Tools>Refactor Rules>Rename a Class)

but I am not very sure if it will rename the application name.
You can try refactor and see if it helps.

Also you can refer to below link it should provide you more clarity
https://collaborate.pega.com/question/renaming-existing-organization-class-new-name

Thank You

Hi Sekhar,

Thanks for your comments. But our application is in production, and we want to understand the data dependency on change of proposition name in DB records along with IH records.   

Also, proposition record does not create a separate class. 

Hi Gaurav,

I don't think there is a facility in the UI to edit a proposition name. i am assuming you are using Pega 7.1.9 and above and using Decision Data rules.

Changing a proposition name would mean its a new entity. Proposition are products/services in terms of business. 
Instead of changing the proposition rule, you could just create a new Offer and it also creates a backing proposition of the same name.

You can then choose if you want to migrate old proposition's historical data (like IH Fact records) to point to a new name, it requires manual intervention. the Interaction History data model is normalised structure and i think the Proposition name  stored in PR_DATA_IH_DIM_ACTION, you can try to update it there.

But there may be some references within your application depending on how these proposition were used (external integrations or inhouse NBA UI), and if it is still inflight and can receive responses. hence i think the approach should be to deactivate or withdraw the old proposition (name with spaces) and initiate new Offers.

another approach you could try is to build a data flow that reads data from a copy of IH and processes it(update the proposition name and outcometime) and push it to IH using pxInteractionHistory dataset. 
you need to check if you want to keep the same  pxoutcometime as older record.

thanks 

Manu

Hi Manu,

Thanks for you input but we are on Pega 7.1.7 and not using decision data rules.

But we are think a work around similar to approach 1 where we will update the IH action table based on new proposition.

Regarding approach 2, we are thinking about the designing of the strategy by utilizing data flow within an outbound programs for Pega Marketing 7.12.