@ManishK8444

This usually isn’t a product bug it’s access and application context. First, compare the SSO user’s Access Group, roles, and application stack with the non-SSO user; make the SSO user use the same Access Group (fix your LDAP model operator if needed). Ensure the delegated decision table is in a Production ruleset and that ruleset/version is in the application and listed under the Access Group’s Production rulesets for SSO users. Give the role read/open/update on Rule-Declare-DecisionTable (quick test: add PegaRULES:SysAdm4 temporarily if it works, add only the needed privileges). Check for ABAC/Access-Deny rules on Rule-* classes that could hide rule content for external users. If you switch Access Groups during SSO, set the AG before the portal thread starts (or explicitly switch application) so the rule resolves in the right app context. Re-save the rule and clear rule/decision caches (Invalidate and restart) to remove stale resolution. If it’s still blank only for SSO, trace rule resolution on login and when opening the rule to spot a missing ruleset or privilege.