Skip to main content


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

Batches and target actions

Updated on January 26, 2021

Before you begin, review the information about batches that are used in Smart Update and the restrictions on entity target actions.

Pega Product Composer for Healthcare Pega Product Composer for Healthcare Pega Product Composer for Healthcare

About batches

Smart Update uses batches in the flows. You can use batches to organize your information to apply all related changes at the same time.

You can configure your target entities with batches of information for the following content:

  • Benefit set content
  • Benefit set, product template, product, and plan metadata
  • Product template, product, and plan benefit categories
  • Product template, product, and plan coverages

The changes that you specify in the batch are made to all the benefit sets, product templates, products, and plans that you add to the specified batch.

For example, to update 10 products, but change the coverage level on only seven products, you define a product metadata batch by adding the seven products to the batch, and then apply the changes. The changes are applied only to the seven products.

About target actions

During Smart Update, you select target actions for entities, including update existing, replicate, or create new version.

Restrictions on target actions

Benefit setProduct templateProductPlan
Update existingUpdate existingUpdate existingUpdate existing
ReplicateReplicateReplicate
Create version
  • Create version
  • Replicate
  • Update existing
  • Create version
  • Replicate
  • Update existing
  • Create version
  • Replicate
  • Update existing

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.

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

Close Deprecation Notice
Contact us