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

6
Replies
3096
Views
SukhdevP2374 Member since 2022 7 posts
Sky
Posted: Jan 28, 2018
Last activity: Jun 17, 2019
Closed
Solved

How to package an application with all rues/rulesets?

Hi,

I am working on CSA exercise provided in the PDN and developed Onboarding application with Benefit Enrollment case types and configured all the rules as advised in the exercise material.

I want to package my rules for this application so that I can import this later on if Pega clears my exercise system or can use on any other system, please advise me how to package an application and steps to import it on another system?

Thanks

Sukhdev

***Moderator Edit: Vidyaranjan | Moved from PSC to Academy***

To see attachments, please log in.
Pega Academy

Accepted Solution

Posted: 7 years ago

Yes. You should lock the ruleset before migrating it. Instead you can enable 'allow unlocked Versions to be exported'

After completing the package, click on modify, and at the bottom, check the checkbox 'allow unlocked Versions to be exported' and save. You will be able to create the product file.

To see attachments, please log in.
Posted: 7 years ago

Hi Sukhdev,

You can package using package wizard Designer Studio> Application> Distribution>Package and follow the onscreen instructions.

You can import this package in target system using Designer Studio> Application> Import wizard.

 

To see attachments, please log in.
Posted: 7 years ago

Hi Sandeep,

Thanks for help, I did try that but it displayed following message , am not sure what needs to be done here as there might be any rules so how can I unlock all of them, any idea ?

Show More

Hi Sandeep,

Thanks for help, I did try that but it displayed following message , am not sure what needs to be done here as there might be any rules so how can I unlock all of them, any idea ?

The Product is referencing unlocked RuleSet Version instances, please follow the links below to lock them or update your Product rule to allow unlocked Versions to be exported. Be sure to save the Product rule if allowing unlocked RuleSet Versions to be exported, otherwise your change won't take effect.

     HRApps:01-01-01
     HRApps:01-02-01
     HRApps:01-03-01
     HRAppsInt:01-01-01
     Onboarding:01-01-01
     TGB:01-01-01
     TGBInt:01-01-01


Show Less
To see attachments, please log in.

Accepted Solution

Posted: 7 years ago

Yes. You should lock the ruleset before migrating it. Instead you can enable 'allow unlocked Versions to be exported'

After completing the package, click on modify, and at the bottom, check the checkbox 'allow unlocked Versions to be exported' and save. You will be able to create the product file.

To see attachments, please log in.
Posted: 5 years ago

Hi,

In general we don't/never include Branch RSVs in RAP.

We use Branching when we have multiple teams working on the same application. We merge Branch RSVs to single RSV and take RAP of that single RSV.

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