After further testing after getting Search server RU7 and higher installed, Catalog offerings and listings are not rendering correctly in Service Point
Release : 17.3
Component : SDM - xFlow
Determined that in EEM, examining the export of the EEM Offerings Policy for "ACL_all_Offerings", the setting for "All Resources" is incorrect.
For Catalog request listings not showing in Service Point, this is because Catalog is at an older RU than Search Server's RU.
Please be certain that Catalog and Search Server are both at the same RU level. Older Catalog releases (RU5 and older) will not work correctly with Search Server updated to 7.x starting in RU6
To address the form rendering concern, login to EEM as the EiamAdmin user, Application Service Catalog.
Click on "Manage Access Policies" tab, then "Offering" and locate the link "ACL_all_Offerings"
Scroll down to "Access Policy Configuration". Click on [All Resources] and click the Trash can icon to remove the entry.
Recycle EEM and Catalog for the change to take effect.
After correcting EEM permissions in the above, the forms should render correctly.
One can verify the above permissions by exporting the EEM Policies listings.
In EEM, click on "Configure", "EEM Server", "Export Application" and select just the Policies entry for Export.
In the resultant Service Catalog.xml file, you will see:
<Policy folder="/default/Policies" name="ACL_all_Offerings">
<Description>Full access to ALL. This is the default GRANT ALL rule for Services</Description>
<ResourceClassName>Offering</ResourceClassName>
<PolicyType>policy</PolicyType>
<Disabled>False</Disabled>
<ExplicitDeny>False</ExplicitDeny>
<PreDeployment>False</PreDeployment>
<RegexCompare>False</RegexCompare>
<Action>list</Action>
</Policy>
An incorrect setting will reference "All Resources", ie:
<Policy folder="/default/Policies" name="ACL_all_Offerings">
<Description>Full access to ALL. This is the default GRANT ALL rule for Services</Description>
<ResourceClassName>Offering</ResourceClassName>
<PolicyType>policy</PolicyType>
<Disabled>False</Disabled>
<ExplicitDeny>False</ExplicitDeny>
<PreDeployment>False</PreDeployment>
<RegexCompare>False</RegexCompare>
<Resource>[All Resources]</Resource>
<Action>list</Action>
</Policy>
The above actions will address this concern.