Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

NullPointerException while generating Connect-REST rules

SA-56252

Summary



NullPointerException while generating Connect-REST rules through the wizard. 


Error Messages



[ PegaRULES-Batch-38] [ STANDARD] [ ] [ CCC:01.01.01] ( internal.util.PRServiceUtils) ERROR aaaa- Rule Generator thrown exception:
java.lang.NullPointerException
at com.pega.pegarules.integration.config.internal.mapping.RuleGeneratorREST.addRequestDataTransformInfo(RuleGeneratorREST.java:542)
at com.pega.pegarules.integration.config.internal.mapping.RuleGeneratorCommon.addDataPageDetails(RuleGeneratorCommon.java:4048)
at com.pega.pegarules.integration.config.internal.mapping.RuleGeneratorREST.processConnectorMetadata(RuleGeneratorREST.java:214)
at com.pega.pegarules.integration.config.internal.mapping.RuleGeneratorREST.generateRules(RuleGeneratorREST.java:171)
at com.pega.pegarules.integration.engine.internal.util.PRServiceUtils.generateRulesFromMetadata(PRServiceUtils.java:1719)
at com.pega.pegarules.integration.engine.internal.util.PRServiceUtils.generateRulesFromMetadata(PRServiceUtils.java:1747)
at com.pegarules.generated.activity.ra_action_pygeneraterulesfrommetadataasync_90350a212c6cdc08be679680c2693d97.step1_circum0(ra_action_pygeneraterulesfrommetadataasync_90350a212c6cdc08be679680c2693d97.java:160)
at com.pegarules.generated.activity.ra_action_pygeneraterulesfrommetadataasync_90350a212c6cdc08be679680c2693d97.perform(ra_action_pygeneraterulesfrommetadataasync_90350a212c6cdc08be679680c2693d97.java:69)

 

Steps to Reproduce

  1. Create a new REST integration (use any URL)
  2. Skip Define Parameters
  3. Navigate to Methods > deselect GET and select POST
  4. Open Configure for POST
  5. Add Sample > Choose File (any JSON file) > Upload File
  6. Click OK
  7. Click Next
  8. Provide the ruleset and Integration class name and click the Preview button


Root Cause

Integration class name does not support more than 30 characters.


Resolution



Perform the following local-change:

Provide an Integration class name which is less than 30 characters.



 

Published July 23, 2018 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us