Application behaves differently when using existing Org Class

Hi,

We are running the Sales Automation Wizard to setup our environment. If we let the wizard generate the organisation and organisation class, the application functions perfectly.

When we use our existing organisation class, the application does not work anymore. Switching to the application crashes the portal it uses (Developer and User Portal). It leaves us with an almost empty screen.

The organisation class is quite old, but we could not find differences between the config of the generated class, or our own class. Also we tried to remove all differences in the Org structure.

We can also mention our Org class ends with a “-”, and has a total of 7 characters.

Furthermore we tried:

  • Using an existing org and org class from DMSample (DMOrg) → Works

  • Creating an application using the bare “New application” wizard, and using our own org class → Works

We have seen that the developer studio somewhat works, when we add our application containing the Org class in the top position of our built on list. But not fully. We do have the ruleset containing the class and org in our application ruleset list. (and also tried without).

We ran out of ideas where we should look, or what might cause the portals to not load correctly.

Question: what would your suggestion be, where to look?

It turned out that in the:

RULE-DECLARE-DECISIONTABLE PEGACRM-DATA-APPEXT DETERMINECRMAPPEXTCLASS

Our organization class (containing a “-”) was put in without double quotes (“”). Therefor upon switching portals, there was a compilation error. Resulting in no portal shown.

Adding the quotes around our organization class solved the issue.