Question
Ernst & Young, LLP
US
Last activity: 8 Mar 2019 11:35 EST
Customizing PEGA 7 login page - Calling a screen flow
I would like to customize PEGA 7 login page (web-login HTML rule) by adding a link/button called "Create Account". Upon clicking "Create Account", a screen flow should be displayed where the user can enter his details and create an account for himself.
I have seen a post where we can customize PEGA 7 login page by creating an unauthenticated ruleset.
Is there a way to call screen flow in web-login HTML rule to fulfill the above requirement stated?
***Edited by Moderator Marissa to update platform capability tags & add SR Details***
-
Like (0)
-
Share this page Facebook Twitter LinkedIn Email Copying... Copied!
Pegasystems Inc.
US
Theoretically, you could could add to your unauthenticated RS/access group and build its own "mini" app to achieve what you are describing. I imagine it is going to need a handful of custom activities, etc to eventually "hook" into your real application to create actual data instances that will be resolved once you do authenticate yourself.
I personally do not have intimate experience with creating such an app, but I'm willing to bet there are others out there that have done something similar. Or you could draw some parallels with related functionality like a "forgot my password" link.
Ernst & Young, LLP
US
I have tried the below in my personal edition.
1. In Web-Login HTML rule I have added a link/button called "Create Account". On clicking of this link, am calling an activity "TestActivity"
2. In this "TestActivity" I have added the below steps.
a. Create new page
b. Call Work-.New Activity (passing starting flow and class name as parameters)
c. Call Show-Harness (with purpose as Perform)
I have added all the above rules in unauthenticated ruleset and added this unauthenticated access group to "Browser" Requestor type. When I clicked on "Create Account", I could see a blank screen and Perform harness is not loading. But when I checked the tracer, I could see the case is getting created.
Need assistance if anyone has worked on similar requirement and any help is highly appreciated.
Pegasystems Inc.
US
Hello,
Please see the following community posts on this topic:
https://collaborate.pega.com/question/password-changelogin-page-pega
https://collaborate.pega.com/question/where-web-login-login-html-page-configured
The last post also provides the attached document as a reference.
I agree with Rett's comment that the "forgot your password" functionality might be a good example also.
Ernst & Young, LLP
US
I have gone through the posts already before, but none of them are helpful to achieve my requirement. Most of the posts are about configuring PEGA 7 login page, or implementing forgot password functionality (launching a HTML) which can be achieved. My requirement is to launch a Flow on click of a button/link on PEGA 7 login page.
1. In Web-Login HTML rule I have added a link/button called "Create Account". On clicking of this link, am calling an activity "TestActivity"
2. In this "TestActivity" I have added the below steps.
a. Create new page
b. Call Work-.New Activity (passing starting flow and class name as parameters)
c. Call Show-Harness (with purpose as Perform)
I have added all the above rules in unauthenticated ruleset and added this unauthenticated access group to "Browser" Requestor type. When I clicked on "Create Account", I could see a blank screen and Perform harness is not loading. But when I checked the tracer, I could see the case is getting created.
PEG
PL
Hi,
One small pointer, can you try to put all the rules in code-security class. I have not come across this exact thing, but in past have seen scenario where moving one activity from work- to code-security- resolved the issue.
-
Mahesh Kharde Akansha Jain Sai Pasaragi Dheerender Ranga Georgy Kuskov
Ernst & Young, LLP
US
Hi,
It did not work even after creating the rules in Code-Security class.
Please find the screenshots attached.
BPM Company
NL
Hi,
I guess you cannot see anything after clicking the button because the Perform harness is not in the unauthenticated ruleset, which is only one who's accessible at that moment