Closed
Operator Export/Import
We have some operators in Development Environment .
We don't want to export these operators to the production environment while deploying.
How can we exclude development environment operators when we are creating packages for the production environment?
Posted: 10 years ago
PEGA
PEG
IN
Posted: 10 years ago
Turkiye Finans Kat?l?m Bankas?
Turkiye Finans Kat?l?m Bankas?
TR
When creating the package pega can't allow excluding class.
Posted: 10 years ago
Pegasystems Inc.
Pegasystems Inc.
IN
>>> when we are creating packages for the production environment...
how is the package created?
- is it through Application package wizard?
- step #5 in Application package wizard provides option either to exclude or include in RAP rule
- or a manual R-A-P rule creation?
- along with Gangababu's suggestion, also ensure that operator ids are not added under "Individual instances to include" section
- remove ruleset association in the operator ID rule form also helps
- otherwise uncheck include associated data at rulesets to include section
lastly, preview the package (Data-Admin-Operator-ID instances) before creating jar file and correct the data if need.
Try excluding the class Data-Admin-Operator-ID while creating the package.