Support Article
ML7: Issues with FCM Configuration
SA-4521
Summary
1.Getting case type errors on saving our existing Case type rules(with FCM configuration) in ML7.
2. Due to the Case type errors it is not possible to built the new Application on top these as well.
3. CPMC needs new FCM configuration to be defiend in CFF case type rules.
Error Messages
.CustomerDetails.pyemail1:Page type properties are not allowed
.pyworkParty(customer).pxPartyrole:Page type properties are not allowed
.CustomerDetails.pyHomeAddress:Page type properties are not allowed
Steps to Reproduce
Define remote case type.
on advanced tab under List properties to initialize for instantiation section, set an embedded property , .Customer.CustomerInfo.pyFirstName for example, see error
Message Label:
** .Customer.CustomerInfo.pyLastName : Page type properties are not allowed
Message Label:
** .Customer.CustomerInfo.pyFirstName : Page type properties are not allowed
on advanced tab under List properties to initialize for instantiation section, set an embedded property , .Customer.CustomerInfo.pyFirstName for example, see error
Message Label:
** .Customer.CustomerInfo.pyLastName : Page type properties are not allowed
Message Label:
** .Customer.CustomerInfo.pyFirstName : Page type properties are not allowed
Error Message
Message Label:
** .Customer.CustomerInfo.pyLastName : Page type properties are not allowed
Message Label:
** .Customer.CustomerInfo.pyFirstName : Page type properties are not allowed
** .Customer.CustomerInfo.pyLastName : Page type properties are not allowed
Message Label:
** .Customer.CustomerInfo.pyFirstName : Page type properties are not allowed
Resolution
This issue is resolved by hotfix item HFix-20285 (which removes the validation) and is scheduled to be resolved in ML 8 for Pega 7.1.
Published January 31, 2016 - Updated October 8, 2020
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.