Question
Capgemini
IN
Last activity: 9 Aug 2017 7:31 EDT
Getting error which we are not able to resolve Error: .pyWorkParty(CardHolder).pyState: "MEXICO" is too long, maximum length allowed is 2
Hi All,
We have a requirement to hold more than 2 characters in pystate property, In pyState of Data-Party maximum length and expected length was mentioned as 2 , so we were getting below error .
Solutions Tried:
1) Save as of pyState into our application ruleset and we removed max and expected lengths.
2) Created new property with name pyState with no max or expected length.
3) Rule cache for pyState cleared.
Even after the changes are done getting same error, anyone have any idea why we are still getting the error?
Thanks
Abilash
***Updated by moderator: Lochan to move post from Pega Academy to PSC***
Accepted Solution
Capgemini
IN
Hi,
Thanks for response, Issue got resolved .
Even though we had done save as of pyState in our application RS and removed the Max and Expected length we were still getting error, because the pyState was used in activities.
When activities were created pyState had restriction, java code got generated with latest property settings @ that time (restriction to 2 characters) . Even though we had updated the property pyState, referencing activities still had old java code, so we had to save as the activities into new open RS version for java code to regenerate and take latest property settings .
Example java code in old activity:
/ LHS: .pyState
// RHS: pyWorkPage.AccountDetails.StateCode pega.setViaPropRef(".pyState", pRef_19, myStepPage, pega.getStringValueViaPropRef(".AccountDetails.StateCode", pRef_18,
pega.findPageWithException( "pyWorkPage", (String) null)
, false, false, false), "sTN2", false, true);
After save as into new RS version (Note: After pyState property changes are completed to remove max length restriction):
Hi,
Thanks for response, Issue got resolved .
Even though we had done save as of pyState in our application RS and removed the Max and Expected length we were still getting error, because the pyState was used in activities.
When activities were created pyState had restriction, java code got generated with latest property settings @ that time (restriction to 2 characters) . Even though we had updated the property pyState, referencing activities still had old java code, so we had to save as the activities into new open RS version for java code to regenerate and take latest property settings .
Example java code in old activity:
/ LHS: .pyState
// RHS: pyWorkPage.AccountDetails.StateCode pega.setViaPropRef(".pyState", pRef_19, myStepPage, pega.getStringValueViaPropRef(".AccountDetails.StateCode", pRef_18,
pega.findPageWithException( "pyWorkPage", (String) null)
, false, false, false), "sTN2", false, true);
After save as into new RS version (Note: After pyState property changes are completed to remove max length restriction):
/ LHS: .pyState
// RHS: pyWorkPage.AccountDetails.StateCode pega.setViaPropRef(".pyState", pRef_19, myStepPage, pega.getStringValueViaPropRef(".AccountDetails.StateCode", pRef_18,
pega.findPageWithException( "pyWorkPage", (String) null)
, false, false, false), "sTN", false, true);
Pegasystems Inc.
US
Hi Abilash
When you run tracer, can you see which ruleset the error is coming from? Quick review reveals that there is one pyState in the baseclass (PegaRules ruleset) and another in Data-Party (Pega ProCom). Find out which ruleset is throwing the error.
Bhuvana.
Accepted Solution
Capgemini
IN
Hi,
Thanks for response, Issue got resolved .
Even though we had done save as of pyState in our application RS and removed the Max and Expected length we were still getting error, because the pyState was used in activities.
When activities were created pyState had restriction, java code got generated with latest property settings @ that time (restriction to 2 characters) . Even though we had updated the property pyState, referencing activities still had old java code, so we had to save as the activities into new open RS version for java code to regenerate and take latest property settings .
Example java code in old activity:
/ LHS: .pyState
// RHS: pyWorkPage.AccountDetails.StateCode pega.setViaPropRef(".pyState", pRef_19, myStepPage, pega.getStringValueViaPropRef(".AccountDetails.StateCode", pRef_18,
pega.findPageWithException( "pyWorkPage", (String) null)
, false, false, false), "sTN2", false, true);
After save as into new RS version (Note: After pyState property changes are completed to remove max length restriction):
Hi,
Thanks for response, Issue got resolved .
Even though we had done save as of pyState in our application RS and removed the Max and Expected length we were still getting error, because the pyState was used in activities.
When activities were created pyState had restriction, java code got generated with latest property settings @ that time (restriction to 2 characters) . Even though we had updated the property pyState, referencing activities still had old java code, so we had to save as the activities into new open RS version for java code to regenerate and take latest property settings .
Example java code in old activity:
/ LHS: .pyState
// RHS: pyWorkPage.AccountDetails.StateCode pega.setViaPropRef(".pyState", pRef_19, myStepPage, pega.getStringValueViaPropRef(".AccountDetails.StateCode", pRef_18,
pega.findPageWithException( "pyWorkPage", (String) null)
, false, false, false), "sTN2", false, true);
After save as into new RS version (Note: After pyState property changes are completed to remove max length restriction):
/ LHS: .pyState
// RHS: pyWorkPage.AccountDetails.StateCode pega.setViaPropRef(".pyState", pRef_19, myStepPage, pega.getStringValueViaPropRef(".AccountDetails.StateCode", pRef_18,
pega.findPageWithException( "pyWorkPage", (String) null)
, false, false, false), "sTN", false, true);