-
Notifications
You must be signed in to change notification settings - Fork 347
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #3542 from kasperbolarsen/develop
Update bug report and index.md templates + new Q&A page
- Loading branch information
Showing
4 changed files
with
60 additions
and
1 deletion.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,45 @@ | ||
|
||
|
||
**Q: In version 4.10.1 the LPC (Live Person Card) hover option became available as an option for the People Layout. What is the difference between LCP and Persona card? ** | ||
|
||
 | ||
|
||
|
||
|
||
|
||
|
||
**A**: The Live Person Card does not require any additional Graph Permissions. The LPC can be customized to show additional fields from Entra ID, but not the same way as the pnp-people or mgt-person. However it will always show equal to any other people card shown in Microsoft 365.See https://learn.microsoft.com/en-us/graph/add-properties-profilecard. | ||
|
||
---------------------- | ||
|
||
**Q: Is the deprecation of SharePoint-Add-in's affecting PnP Modern Search?** | ||
|
||
**A**: No, as the project is built using the SharePoint Framework, not the deprecated add-in model. | ||
|
||
----------------------- | ||
|
||
**Q: Is the PnP Modern Search package certified by a 3rd party in order to ensure compliance with GDPR or similar requirements? ** | ||
|
||
**A**: No, it is up to you to review the source code in order to ensure compliance with any relevant requirements. The web parts do not store, process or log any data, thus GDPR is not directly relevant. Any privacy concern of data is up to how data is stored and protected at the source level, e.g. SharePoint. | ||
|
||
----------------------- | ||
|
||
**Q: Are the PnP Modern Search web parts logging data to a local or remote receiver? ** | ||
|
||
**A**: No, the PnP Modern Search web parts are not logging data to any receiver, not even telemetry data. | ||
|
||
----------------------- | ||
|
||
**Q: What is the ID or Name of the PnP Modern Search App Registration in Azure AD/Entra? ** | ||
|
||
**A**: There isn’t an App Registration nor Enterprise application as PnP Modern Search does not rely on an application entry. The solution uses FedAuth cookies from SharePoint when calling the SharePoint Search API, and uses the “SharePoint Online Client Extensibility” app registrations when calling Graph API’s. | ||
|
||
The solution does elevate any permissions when calling the API’s as permissions are all of the type Delegated Permissions, meaning that the permissions are bound to the current user, not the PnP Modern Search solution. | ||
|
||
----------------------- | ||
|
||
**Q: I am concerned about what will happen if the project is abandoned. Will Microsoft take over the project? ** | ||
|
||
**A**: It is hard to predict the future, but a vast number of companies are using the PnP Modern Search web parts in their solutions. The solution is hosted on GitHub owned by the Microsoft Search team. Most likely these companies will either clone the project and make a commercial version or will provide the manpower needed to keep the project in maintenance mode. | ||
|
||
----------------------- |
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters