Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

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.

Troubleshooting: "Unexpected character +" exception with truncated property name

Updated on September 13, 2021


Rules with a circumstance property defined may display the following errors when you attempt to check them out:

Check out failed. Exception while opening to check for conflict with an existing check out record. InvalidReference newAssignPage.pxAssignedOperato+
unexpected character '+' at position 31, expected end of name



The '+' mentioned in the error points to the issue: In the above example, the Circumstance property has been truncated in the database column.

Some property references (especially when the page name is included) may be too long for the width of the column defined in the database where they are being stored.  When this occurs, Process Commander truncates the name of the property to fit in the column as it saves the property rule, and adds a "+" at the end of the name in the column to signify that the truncation occurred.


Property name: newAssignPage.pxAssignedOperatorID


Shorten the property reference (if possible) to work around this problem.  For the example above with a circumstanced rule, the property should probably belong on the primary page. In that case, the page reference part (the part before the period character) of the property reference is no longer needed, so the reference requires fewer characters.

  • Previous topic Troubleshooting: "Unable to use SHA1PRNG algorithm" when saviing DB Name (WebSphere 5.1)
  • Next topic Troubleshooting: "java.sql.SQLException" Name of SQL Server 2005 driver differs from SQL Server 2000


Pega Platform 7.1.1 - 8.3.1 Business Architect System Architect System/Cloud Ops Administrator Data Integration System Administration

Have a question? Get answers now.

Visit the Support 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. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us