Skip to main content

This content is closed to future replies and is no longer being maintained or updated.
Links may no longer function. If you have a similar request, please write a new post.

Question

 Sreekanth Reddy Annapureddy (SreekanthReddyA) Staidlogic
Staidlogic
IN
SreekanthReddyA Member since 2017 12 posts
Staidlogic
Posted: Dec 30, 2019
Last activity: Dec 31, 2019
Posted: 30 Dec 2019 5:20 EST
Last activity: 31 Dec 2019 7:58 EST
Closed

what is import.existing.instances=skip is going to do (noticed skip is functioning as override)

Report
import.existing.instances
How the import action handles existing instances:
skip : (Default) Skip instances that already exist in different rulesets or versions.
override : Replace instances that already exist in different rulesets or versions.
However, skip and override is behaving in same. Can you please explain the differences?
Below are the parameters sent, both scenarios are adding new rules and updating rules in same version on import.
  • with skip

"artifactType":"","codesetVersion":"06-01-01","compileLibraries":"true","commitRate":"100","codesetName":"Customer","bypassSchema":"true",
"archivePath":"","existingInstances":"skip","repositoryName":"","nofailonerror":"false","mode":"import","preserveOrder":"true","async":"false","skipBackup":"false",
"allowImportWithMissingDependencies":"false","insecureOperators":"","importFromRepository":"false","allowInheritedConnections":"false"

Show More
import.existing.instances
How the import action handles existing instances:
skip : (Default) Skip instances that already exist in different rulesets or versions.
override : Replace instances that already exist in different rulesets or versions.
However, skip and override is behaving in same. Can you please explain the differences?
Below are the parameters sent, both scenarios are adding new rules and updating rules in same version on import.
  • with skip

"artifactType":"","codesetVersion":"06-01-01","compileLibraries":"true","commitRate":"100","codesetName":"Customer","bypassSchema":"true",
"archivePath":"","existingInstances":"skip","repositoryName":"","nofailonerror":"false","mode":"import","preserveOrder":"true","async":"false","skipBackup":"false",
"allowImportWithMissingDependencies":"false","insecureOperators":"","importFromRepository":"false","allowInheritedConnections":"false"

  • with override

"artifactType":"","codesetVersion":"06-01-01","compileLibraries":"true","commitRate":"100","codesetName":"Customer","bypassSchema":"true",
"archivePath":"","existingInstances":"override","repositoryName":"","nofailonerror":"false","mode":"import","preserveOrder":"true","async":"false","skipBackup":"false",
"allowImportWithMissingDependencies":"false","insecureOperators":"","importFromRepository":"false","allowInheritedConnections":"false"


Show Less
DevOps
Posted: 3 years ago
Posted: 30 Dec 2019 8:13 EST
Vishal Sinha (sinhv1) Senior Technical Solutions Engineer
Pegasystems Inc.
IN
Report

Hi,

What type of archive you are trying to import? Is it a PegaArchive or ApplicationArchive?

The import.existing.instances option is supported only for PegaArchives.

Thanks
Posted: 3 years ago
Posted: 30 Dec 2019 22:57 EST
Sreekanth Reddy Annapureddy (SreekanthReddyA) Staidlogic
Staidlogic
IN
Report

I'm trying to import Pega Product with one ruleset.
Posted: 3 years ago
Posted: 30 Dec 2019 11:36 EST
Prakhar Aggarwal (Prakhar_GCS) PEGA Principal Engineer, Technical Support
Pegasystems Inc.
GB
Report

Please check below if this helps you:-

-->override - For rules - If a rule with the same key exists in the system but the rule resolution properties differ (e.g. RuleSet, Version, etc), then replace the existing rule with the imported rule.
            For work - If a work object with the same key exists but it belongs to a different application (e.g. different class hierarchy but same classgroup name and same ID prefix), replace the existing work object with the imported work object.
 

-->skip     - For rules - If a rule with the same key exists in the system and the rule resolution properties differ, do not replace the existing rule.
           For work  - If a work object with the same key exists but it belongs to a different application, do not replace the existing work object.
Posted: 3 years ago
Posted: 30 Dec 2019 22:56 EST
Sreekanth Reddy Annapureddy (SreekanthReddyA) Staidlogic
Staidlogic
IN
Report

I'm trying to import a product which contains one ruleset.  Ruleset ABC:01-01-01, has 5 rules. 2 exiting rule updates and one new rule.

what happens when i use import.existing.instances=skip?
Posted: 3 years ago
Posted: 31 Dec 2019 7:58 EST
Pawan Narain Singh (pawann) Swedbank AB
Swedbank AB
SE
Report

Hello Srikanth,

When using the "skip" option, if a rule with the same key exists in the system and the rule resolution properties differ, do not replace the existing rule and if a work object with the same key exists but it belongs to a different application, do not replace the existing work object.

Thank you,
Pawan
Posted: 3 years ago
Posted: 30 Dec 2019 17:11 EST
Pawan Narain Singh (pawann) Swedbank AB
Swedbank AB
SE
Report

If the outcome is unexpected, can you share the complete logs while performing the import using both the options?
Posted: 3 years ago
Posted: 30 Dec 2019 22:58 EST
Sreekanth Reddy Annapureddy (SreekanthReddyA) Staidlogic
Staidlogic
IN
Report

I'm trying to import a product which contains one ruleset.  Ruleset ABC:01-01-01, has 5 rules. 2 exiting rule updates and one new rule.

what happens when i use import.existing.instances=skip?

 

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

Pega Collaboration Center 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