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

Aged Updates does not work for import mode with command-line



User imports a JAR file using command line. In aged update scenario, when they import using wizard they are getting an error and import doesn't take place. But, when they try to import using command line, import was succesfull and rules were overridden.

In file, under "settings for import tool" the value of "import.existing.instances" property is unset. So the deployment should fail for aged update scenario.

But it is not failing. Since "import.existing.instances" property is unset in prpcUtils.Properties file, the deployment should fail. But it imported one rule successfully.

User is expecting the import should fail because of above issue when user tries to import the same jar file using command line (prpcUtils). 

Error Messages

No error message.

When user tries importing a jar file using Import wizard,  a warning message regarding Aged Updates is shown and user can either proceed by clicking next or withdraw by clicking cancel.

Steps to Reproduce

1. Import Jar1 using Import Wizard.
2. Import Jar2 using Import Wizard.
3. Now again import Jar1 through Wizard.

Error for aged updates as shown in the attachment. Here deployment has been paused because of aged update scenario.

Like this when tried to import using command line one must get error for aged update or the deployment should fail.

To make the deployment fail, user has tried unset the value of "import.existing.instances" property (leave "import.existing.instances" property as blank).

But while importing using command line the decision table is getting imported.

Root Cause

User has assumed that import.existing.instances property is used to handle the Aged updates.  

This property (import.existing.instances) is used for the non-rule resolved classes (Rule-Obj-Class), so if you have the same rule available in a different ruleset then one can override skip or failure using import.existing.instances property.


Requested functionality (Aged Updates) is not supported using command-line tool and user has been advised to use Import Wizard in the Designer Studio for Aged Updates rather than command-line utility.

Published January 30, 2016 - 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