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.

Issues resolved in PRPC 6.3 SP 1

Suggest edit Updated on February 17, 2016

In any software product, features occasionally do not behave as intended. Pegasystems is committed to a high standard of quality, and has implemented procedures and programs to detect and correct such issues in PRPC and our other products. Here is a list of resolved issues included in PRPC 6.3 SP1 that are of most interest and likely to have the most impact on the Pegasystems user and developer community.

Each resolved issue was packaged into a "hotfix" which Pegasystems made available to customers encountering the issue between the time it was resolved and the time it could be included in this release. If you upgrade to 6.3 SP1, you do not need to request any of the hotfixes in the list below.

A number of reported issues were resolved for this release as duplicates, "cannot reproduce", or with other resolutions that did not result in changes to PRPC.

HotFixNote
HFIX-5211A customer, defining a database column, set it to VARCHAR(MAX), which became available in MS SQL 2005. PRPC was not handling this setting correctly when the application was migrated to a new environment. PRPC can now handle this setting.
HFIX-5482It was not possible to localize the subject line for email correspondence. This is now corrected. To localize the subject line, create a field value for pyCaption. If the field value has parameters, it should be sent in the format to subject parameter &let;fieldvalue>\t<param1>\t<param2>...and so on. You can create a new field value on pyCaption or override the existing field value "Subject" on pyCaption.
HFIX-5513The browser window would freeze after multiple searches were executed. This has been resolved.
HFIX-5524A fix to the import wizard accidentally omitted extending the fix for repurposed rules, so repurposed rules were not being imported. This oversight has been corrected.
HFIX-5572In the "Get Next Work" function the currentWorkPool parameter was not being used. This has been corrected.
HFIX-5574If you renamed a class that contained a declare page, the class name change was not being passed to the declare page (it does not form part of the pzInskey for a declare page, but the declare page still uses it). This has been corrected.
HFIX-5583When using the spell checker in the rich text editor (RTE), if you hit backspace the current content would be deleted. This has been corrected.
HFIX-5579This fix corrects two issues: Support for "select all" was not present in the "Customer Service Data" step in the Service Accelerator, and properties with a size greater than 100 were not displaying.
HFIX-5597A customer using the Yahoo rich text editor to format outbound email reported that images added to the email were not being transmitted. The problem, in the process to clean up HTML content, has been corrected.
HFIX-5599A Connect-SQL call in a multiset stored procedure in a Sybase database was throwing an error because an invalid "fetch" size was being set. This has been corrected.
HFIX-5633In the Expression Builder, critical information such as the name of the activity to call on an "on change" event was being lost. This has been corrected.
HFIX-5660XSD URL location was not dynamic in XML Parse rules. Global Resource Settings are now available to handle XSD URLs.
HFIX-5682When Obj-Browse was called from the smart info activity, it would not populate pyDataSource. This has been resolved.
HFIX-5683Performance alerts on activities with very large parameters pages or a large number of individual parameters were causing performance issues for the file system, JMS message repositories, and SOAP transport. Options in prconfig.xml now allow truncating parameter pages in alerts and throttling memory use for alerts.
HFIX-5705There was a problem displaying the correct worklist in certain portals. The portlet has been updated so it can access information for the current user.
HFIX-5712Soap service was throwing an error on blank data. The parse rule now checks for a blank value, and handles it with a graceful error message, before attempting to process the XSD.
HFIX-5738An issue rendered the menu bar inaccessible for some PRPC users. This has been corrected.
HFIX-5789Parameters passed to a data transform would become blank. This has been corrected.
HFIX-5809AddAssign was hard-coded to create a queue for "Goal:event level only". The postUpdate activity can now set it for different event levels.
HFIX-5817In some circumstances, BIX was not extracting workbaskets and assignments without a log entry as to why. In debug mode, the List of Qualified Instances is now printed to the log file.
HFIX-5829A change allowing registration of Mbeans for all types of PRPC startup now makes it possible to add to SMA the PRPC engine running in JSR94 mode only.
HFIX-5853Before this fix, it was not possible to change the namespace in a SOAP Service WSDL. A checkbox is now available; checking it allows the user to specify a custom namespace.
HFIX-5870A specialized out-of-the-box stream used html rules, CompositePortalConflct and CompositePortalHarnessConflict, that did not localize correctly. This has been corrected
HFIX-5910If you had your development system configured to "Release on commit" and encountered an error while committing, the system would release the lock although you had not committed the rule. This has been resolved.
HFIX-5915To correct an error when using JMSAppender to send JMS messages, a third parameter has been added to the connection method in prconfig.xml. The additional parameter allows the user to set the JMS session acknowledge type that is valid for the JMS software the system is using. The default is 1, for "Auto_Acknowledge".
HFIX-5962Auto discovery was not working for remote case types. This has been resolved.
HFIX-5992Some users upgrading from 6.2 SP2 to 6.3 encountered CSS (stylesheet) errors. This has been corrected.

<== Back to the main release page

Did you find this content helpful? YesNo

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.

Ready to crush complexity?

Experience the benefits of Pega Community when you log in.

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

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us