requestMap not available when using journalContent in WEM

• Type: Bug
• Status: Closed
• Resolution: Fixed
• Affects Version/s: 7.0.X, 7.1.X, Master
• Fix Version/s: 7.0.0 DXP FP89, 7.0.10.13 DXP SP13, 7.0.X, 7.1.10 DXP FP13, 7.1.10.3 SP3, 7.1.X, 7.2.X, Master
• Component/s: Content Display Widgets > Web Content Display widget
• Labels:
  • ee-ts
  • liferay-dxp-70-sp13
  • liferay-dxp-71-sp3
  • liferay-fixpack-de-89-7010
  • liferay-fixpack-dxp-13-7110
• Branch Version/s:
  7.1.x, 7.0.x
• Backported to Branch:
  Committed
• Fix Priority: 3
• Git Pull Request: https://github.com/brianchandotcom/liferay-portal/pull/70133

Description:
Attempt to render one Web Content Article inside another Web Content Article using journalContentUtil.getContent where requestMap is available in the nested Web Content Article. This results in the next Web Content Article not displaying the requestMap keys. Underlying issue is that the portletRequestModelFactory context object is missing.

Steps to Reproduce:
1) Create two structures with a text field, Structure A and Structure B.
2) Create templates:
Template A (Structure A):

<h1>template A request map keys</h1>
<#list requestMap?keys as key>
${key}
</#list>

Note:

• Template A shows some text and prints requestMap keys

Template B (Structure B):

${journalContentUtil.getContent(themeDisplay.getScopeGroupId(), Texta4r4.getData(), viewMode, themeDisplay .getLanguageId())}
 
<h1>template B request map keys</h1>
<#list requestMap?keys as key>
${key}
</#list>

Note:

• Texta4r4.getData() needs to be changed. Please refer to templateB_instructions.png.
• Template B renders a content by articleId, some text and prints requestMap keys.

3) Create Content A using Structure A and add text in the text field
4) Create Content B using Structure B and add article ID of Content A in the text field
5) Add Web Content Display portlet to the page and configure it to show Content B.

Expected Results: requestMap keys show for both A and B
Actual Results: requestMap is empty for A (nested WC), but shows for B (not nested WC)

Can reproduce on 7.0.x, 7.1.x, and master. Harder to test on master because articleId is no longer visible from the UI when viewing a web content article. However, can use database browser to find articleId from the JournalArticle table.