Question
CGI
IN
Last activity: 16 Aug 2017 1:11 EDT
Error on opening the flow "This is a placeholder."
Error on opening the flow "This is a placeholder.". Help in resolving the issue.
Thanks in Advance!
Accepted Solution
Pegasystems Inc.
IN
As I have mentioned in my earlier comment, have you ran tracer and check for error?
Pegasystems Inc.
US
Hi,
Do you have the Pega-EndUserUI ruleset in your application rulesets? That could be one reason for the error as noted in the below Support Article.
CGI
IN
Thanks.
We have not removed Pega-EndUserUI ruleset. But We don't why the "This is a placeholder" error is not coming now, when "Pega-EndUserUI" ruleset is there.
I am not able to access url "https://mesh.pega.com/message/79307#79307". could you please share the contents of url "https://mesh.pega.com/message/79307#79307"
Thanks in Advance!
Updated: 20 Feb 2017 23:19 EST
Pegasystems Inc.
IN
Hi Rajasekhar,
I had a look into this internal post (accessible only to Pega employees) and here's the gist of it - issue was due to the addition of "ruleset pega-EndUserURL:06-03" in the application's rule stack. The issue was resolved after removing this.
Hope this helps!
CGI
IN
Thanks.
We have not removed Pega-EndUserUI ruleset. We don't why the "This is a placeholder" error is not coming now, when "Pega-EndUserUI" ruleset is there.
How can I debug it.
Pegasystems Inc.
IN
Ideally the End User UI ruleset should not get included. If it is there , then definitely that is the root cause.
If it is not there but still you are facing the issue then please run tracer and share the outcome.
Accepted Solution
Pegasystems Inc.
IN
As I have mentioned in my earlier comment, have you ran tracer and check for error?
Maantic
IN
But we don't see the very same issue in versions like 7.2.2 or 7.2.1 or earlier, how come it just got introduced in this version.
Even when we build a new application from scratch the base product Pega Rules has Pega-EndUserUI:07-10 ruleset in the application ruleset stack.
Removing Pega-EndUserUI:07-10 ruleset resolves the issue but i don't think that's a permanent solution.