what option is available in BIX when i run from designer studio and want to include properties from child classes?

if it is command line, it would be '-c'. but if i want to run from designer studio where extract rule is defined in work group level and i would like to include all work types in the extract rule.

**Moderation Team has archived post**

This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.


Keep up to date on this post and subscribe to comments

February 10, 2016 - 7:09am

Command line options are not available when you run the extract rule from the ruleform. Extract rules are intended to be run from command line. That said, you can use the pxExtractDataWithArgs activity available from 7.1.8 onward. Please refer to the BIX user guide -

February 10, 2016 - 4:49pm
Response to nistr

Hi Rajiv,

Thanks a lot for your reply. I went over the document. Will the pyArgs take '-c' without quote?

February 18, 2016 - 9:11am
Response to DyanG412

Yes it would.

February 21, 2017 - 2:14am
Response to nistr


When i gave the argument -c to the pxExtractDataWithArgs activity, it is throwing an exception that it could not process the extract rule. Please advise.

March 3, 2017 - 12:13pm
Response to KommisettiV

Hello Kommisettiv

Can you please provide us the complete exception details. 

February 18, 2016 - 2:27pm

Hi Rajiv,

Thanks .We are considering whether command line or extract activity? What would be considerations to choose one option over another?

February 19, 2016 - 12:36am
Response to DyanG412

Note that when run via an agent, it will run in a background thread in the same JVM as the node where it has been scheduled to run. If run via a shell script, it spawns a new JVM (process) to extract the data. So the call is whether to load the current JVM with extra processing or to spawn a new one.

Extraction could be a heavy (resource intensive) process depending on how much data you are extracting.

Also, if you are using Pega Cloud, the pxExtractDataWithArgs is the only option to extract data.

February 19, 2016 - 10:41am

Hi Rajiv,

'Extraction could be a heavy (resource intensive) process depending on how much data you are extracting'

Is the resource intensiveness on the application server or on the database. I assume on both. But what is the impact like in database and app server? Does simply adding resources (CPU and Memory, and storage) resolve it even if we are using agent to run pxExtractDataWithArgs? We do not have cloud but looking at the option to use the activity be run from an agent? Are there any other considerations?

February 21, 2016 - 5:52am
Response to DyanG412

Typically the extract rule has only a subset of the properties that the work object (case) has. So depending on how big the BLOB is and how much data is extracted, that much processing is needed. Yes, it will have an effect on both database and application server. Please note that when you use this activity to run as an agent, it runs only on one node rather than all nodes connected to this DB (cluster).

You can get further details about the performance benchmark done for command line BIX in the user guide -