Based upon environment we need to change the invoice number .

User Experience
, ,
1

Hi ,

Actually for invoice number we created a data transform all values will be hardcoded.

For all environment we used same number format.

Now change the requirement , based up on the environment we need to change the invoice number format .

for example :

Dev–cpc-dev-123

uat-cpc-Uat-123

prod–cpc-prd-123

how to handle this please help me

2

@kirti

Instead of hard coding the number format inside data transform.

  • Have a DSS and in that maintain the number format.. Invoke this DSS inside data transform. So that after deployment completed in all environment you could change the format based in business need.
  • Another option is have system setting and inside that based on production level define your number format and invoke the system setting inside data transform. If your going for this approach then after deployment completed you don’t want to update anything manually.
3

@Gunasekaran_Baskaran I will go with 2nd Approach ,Please example some more .I already have one Dt for dev . next what can i do .

Please help me

4

@kirti You can make use of pxProcess.pzProductionLevel to identify whether it is dev/UAT/Prod.

Based on that you can change the invoice.

[https://community.pega.com/sites/pdn.pega.com/files/help_v719/definitions/p/productionlevel.htm#:~:text=Each%20Pega%207%20Platform%20system,security%20features%20of%20your%20system.&text=The%20System%20instance%20(the%20single,production%20level%20of%20your%20system.](https://community.pega.com/sites/pdn.pega.com/files/help_v719/definitions/p/productionlevel.htm#:~:text=Each%20Pega%207%20Platform%20system,security%20features%20of%20your%20system.&text=The%20System%20instance%20(the%20single,production%20level%20of%20your%20system.)

5

@kirti

Prod level.png
Prod level.png498×151 6.4 KB

You can make use of this number value with the pxProcess.pzProductionLevel and you can change the invoice. You can use any method to implement

6

@kirti

Please refer below mentioned article, in that it was clearly explained how to use system setting.

Configure the system setting as mentioned in article and invoke that inside data transform. Apart from this you don’t want to do any changes.

During runtime number will get returned dynamically from system setting based on production level value.

Dynamic System Setting & (Rule) System Setting in Pega - OneStopPega.

You could find respective environment Production Level value under pxProcess.pzProductionLevel page. This is pega OOTB internal logic value to identify production and non production system.

7

@Anoop Krishna How to Call Applications setting in Data transform , I can see OOTB Datapage "D_pxGetApplicationSettingValue ", But This Datapage not Avilable in my version 8.3.4.

Is Any another Option to call

8

@kirti You don’t need to call application settings. You can straightaway use pxProcess.pzProductionLevel for your logic if system level system is already been set. Pega system level setting will put prod level value to the clipboard. You can check your clipboard for this value pxProcess.pzProductionLevel, if value is there that means value is been already set.If you don’t find it you will need to set that prod level value to system setting.

pxProcess.pzProductionLevel==2

“Dev” + “–cpc-dev-123”

pxProcess.pzProductionLevel==3

“uat” +“-cpc-Uat-123”

You can set these values to DSS and get it from DSS if you want to avoid hardcoding.