Hi,

What is the difference between application validation and ruleset validation mode?which situation we can use application validation and ruleset validation?

Ruleset validation is performed every time a rule is saved. It guarantees that referenced rules are available on the target system when the ruleset is promoted.
Ruleset validation does not affect rule resolution at run time, but is only applied at design time.
There are two options for the validation mode:
 1.Application Validation
 2.Ruleset Validation
The selected validation mode applies to all versions of the ruleset.
The New Application wizard creates rulesets that are set to both Application Validation (AV) and Ruleset
Validation (RV) modes. The rulesets containing the application rules are AV mode to reduce the difference between design and run time.
Conversely, the organizational rulesets created by the New Application wizard are RV mode. RV ensures strict validation on prerequisite rulesets when migrated.

Application validation mode
If the AV mode is used, rules in the ruleset can reference all rules in the rulesets defined in the:
 1.Same application
 2.Rulesets belonging to any built-on application
Rules in the ruleset cannot reference rules outside the current application stack or above the defining application.

Ruleset validation mode
When you use RV mode, each ruleset version defines one or more ruleset versions on which the ruleset
version depends. For example, if you create a ruleset Myco:01-01-01 that uses rules in MyCoInt:01-01-01 and Customer:01-01-01, then MyCoInt:01-01-01 and Customer:01-01-01 ruleset versions must be specified as a prerequisite. Only rules in the ruleset versions that are specified as prerequisites (and their prerequisites) can be referenced from the ruleset.

Mixing application ruleset validation modes
You can mix rulesets that use AV and RV.
 1.Rulesets with another ruleset in brackets — for example, MyCoPL [MyCo] — next to them use RV. The ruleset in brackets is the prerequisite ruleset.
 2.Rulesets without a ruleset with brackets next to them use AV.
With RV, you cannot call AV rulesets that are not in the prerequisites.

Thank You.

How and who can differentiate the portals like user Portal, manager portal?

Access group references an application version that the user can access, and the roles that the user belongs to when logged in. For each role in an application, you allow or deny actions and privileges to
determine what actions users assigned to the role can and cannot perform.
When you extend the access control model for an application, you may need to create additional access groups to implement the entire model. When creating a new access group, consider how the access
group differs from existing access groups.
Identify allowed portals for user interaction
An access group specifies the portal or portals that members of the access group use to perform work.
Access groups for end users reference one of the standard end-user portals. When identifying portals to add to an access group, select portals that align to the roles assigned to the access group. For example,
if members of an access group are managers, add the Manager portal to the access group record. To add a portal to an access group record, list the portal in the Available portals section of the Definition tab
of the access group record. When adding portals to an access group, identify a default portal to present to users upon log in. The following example shows an access group configured to allow users access to the Manager and User
portals. In this configuration, Pega presents the Manager portal to members of the access group after they log in.

If an access group lists more than one portal, the remaining portals are available to users from the
Operator menu.
Note: In Designer Studio, additional portals are listed in the Launch menu, rather than the operator menu. In Pega Express, additional portals are listed in the Application view menu.

Identify allowed access roles for group members
An access group identifies the access roles granted to members of the group. As you extend the access control model for your application, you add new roles to an access group. Adding a role to an access
group grants the access control and privileges for the role to the user. To add an access role to an access group, list the Access Role Name record in the Available roles section of the Definition tab of
the access group record. When configuring an access group, identify the access roles that grant or deny privileges to match the needs of members of the access group. An access group can reference more than one access role.
For example, an application allows employees to submit expense reports for reimbursement. The application then assigns the case to the manager of the user for review. However, managers also submit
expense reports. So managers perform tasks associated with both the user and manager roles. In this situation, you apply both roles to the access group for managers.
When an access group references more than one access role, Pega applies the most-permissive setting across all the access roles.

Thank You