I passed Class name, RuleSet Name, RuleSet Version Range, Package saving path.
Whenever execute the command line, it is generating the package with the whole instances of Class irrespective of RuleSet Name and Version.
So the generated package is huge, not the one which expecting.
EX: i wanted to create a package by exporting instances belongs to Pega-FW-Work class and associated to Pega (RuleSet), and versions from 01-01-01 to 01-02-04.
The package created contains the entire instances of class (Pega-FW-Work). But the package should contains only instances within the Peg-FW-Work class associated Pega (RuleSet) versions from 01-01-01 to 01-02-04.
If i pass only RuleSet name and version,command line tool is not allowing to create package and expecting class.
If i give only class (Pega-FW-Work) it is creating package with the instances of entire class.
I'm not able to create package with desired instances.
Can you go into Pega and create a product rule which has exactly what you want? Once you have that you could use that rule to run the export from prpcUtils or if you post the rule here we can try to figure out how to set the properties to match what you have in the product rule.
I created a product rule with required information within application. I tried to export that rule using prpcUtils. While exporting rule, script is expecting class name . Then I gave class name of that rule(Rule-Admin-Product). The script generated all the products from the class (Rule-Admin-Product) .
Please post the log file from when you tried to export using the product rule as well as the prpcUtils.properties file you are using. I don't care about the database properties, just all of the properties in the section titled "SETTINGS FOR EXPORT TOOL". It would be good to see the product rule as well.
If you click on the "Use advanced editor" in top right of text area for your reply then you will see on the bottom right a paperclip Attach. Or you reply to the email notification you get for this discussion with the file attached and I think they will get attached that way as well.
I'm not sure why you do not see it. In this box that I am typing this reply it is in the top right corner.
Anyway I just tried a product rule export on 6.3sp1 and it worked just fine. From the command line the parameter that you would use is exportRAP when trying to export a product key . And you need to specify the pega.user.username and password in the properties file for the operator to use for rule resolution.