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

 Harun ÇAKMAKÇI (Harunc61)
Turkiye Finans Kat?l?m Bankas?

Turkiye Finans Kat?l?m Bankas?
TR
Harunc61 Member since 2014 10 posts
Turkiye Finans Kat?l?m Bankas?
Posted: Nov 23, 2015
Last activity: Nov 25, 2015
Posted: 23 Nov 2015 4:05 EST
Last activity: 25 Nov 2015 13:15 EST
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?

To see attachments, please log in.
System Administration

Posted: 9 years ago
Posted: 25 Nov 2015 13:15 EST
Phani Sahukaru (sahup1)
Pegasystems Inc.
Phani Sahukaru
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.

To see attachments, please log in.

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