Change |
More Information |
Portal URL Aliases The documentation on portal URL aliases has been revised and extended. |
|
Federated Portal Network: New Permission Checks for Remote Role Assignment A role with the following UME actions and user assigned to it must now exist on the producer portal so that a user administrator on the consumer can perform remote role assignments in the Identity Management tool: ● UME actions: ○ Remote_Producer_Write_Access ○ Remote_Producer_Read_Access ● User: pcd_service In addition, when a user administrator deletes a role on a producer portal, the administrator performing this task should be assigned the Remote_Producer_Write_Access action (through the pcd_service user). This ensures that all remote role assignments to that role on the respective consumer portals are also automatically removed. Without the assigned UME action, the role assignments remain on the consumer portal after the source role is deleted on the producer portal. |
|
Federated Portal Network: Recommendation Added to Documentation Regarding Browsing of Remote Content (Relevant to remote delta link usage only) If a content administrator updates properties on the producer portal, and the changes are not visible on the consumer portal, then the content administrator on a consumer portal should refresh the display of the remote Portal Catalog (by choosing Refresh in the content menu of the producer's Portal Content folder). This ensures that the most up-to-date Portal Catalog structure is displayed on the screen. The reason that the content structure may not be up-to-date on the consumer portal is because the portal caches the Portal Catalog structure exposed by a remote producer portal only at preset intervals. This improves portal performance by reducing round-trips between the producer and consumer portals. If a content administrator does not know when content is being updated on the producer, then it is advised to always refresh the Portal Content before browsing the Portal Catalog of a remote producer. Note that the ensuing round-trips between the producer portal and consumer portal impede overall portal performance while the update is being performed. |
|
Federated Portal Network: Information Added to Documentation about Remote Delta Links and Integration Properties (Relevant to remote delta link usage only) In certain cases, the value of an object property that is categorized as an integration property is taken from what is stored on the consumer portal instead of the producer portal. This means that if a content administrator updates the value of an integration property in a source object (iView, page, and role) on the producer portal, then any corresponding remote object on the consumer portal renders its content at runtime with the old value from the consumer portal. Information about the instances when this takes place and a list of known integration properties is now available in the documentation. |
|
Federated Portal Network: Names of 'P4 Connection' Dropdown Menu Options Have Changed In the Add a NetWeaver Portal wizard and editor and in the Producer Registration tool, the names of the options in the P4 Connection dropdown menu have changed as follows: · Via SAP Message Server is now Load-balanced via SAP Message Server · Direct to Server is now Connection String or Single Server Note that the existing functionality has not changed. This name change is intended to make the options in the list more understandable and accurate. |