Configure OAuth2 provider settings for portals.
The OAuth 2.0 based external identity providers involve registering an "application" with a third-party service to obtain a "client ID" and "client secret" pair.
The supported providers are:
Microsoft Account
Twitter
Facebook
Google
LinkedIn
Yahoo
Reference:
https://docs.microsoft.com/en-us/powerapps/maker/portals/configure/configure-oauth2-settings

The body will contain string that represents the JSON value of an instance of the RemoteExecutionContext class.
Reference:
https://docs.microsoft.com/en-us/powerapps/developer/data-platform/use-webhooks

Topic 4, Proseware, IncBackground
Proseware, Inc. is an industry leading software company with several thousand employees. The company has had some trouble recruiting talented employees. Top-level candidates interview with the company but go on to work for competitors.
Feedback from candidates show that some offers were not accepted because the interview scheduling process was unpleasant. The company does not have a system to keep track of the candidates that were not selected.
Current environment
The recruiting process starts when an individual applies for a position on the company website. The individual may have found the position on their own, they may have been officially referred by an employee, or in some cases were contacted directly by a hiring manager and encouraged to apply.
Recruiters schedule an interview with a hiring manager and interviews with two senior team members. Each interview results in feedback about the candidate and a recommendation whether to hire or not.
The recruiting team manages all information by using a model-driven application.
The company has the following Microsoft Dataverse tables and columns:
* JobPosting
o Hiring Manager - lookup to SystemUser
o Recruiter Assigned - lookup to SystemUser
* Contact (Job Applicant)
o Contact identifier
o First name
o Last name
o Time-Zone Offset
o Person of Interest - Yes/No (default)
* Application proapplication
o Contact identifier, Contact - lookup to Contact
o Job Posting - lookup to JobPosting
o pro_recruiterassignedid
* Interview
o Application - lookup to Application o Job Posting - lookup to JobPosting o Recommend - Choice (Yes (0), No (1), and null (default) are the available values) o Person of Interest - Yes/No, No is the de'aul: value
* Referral
o Contact - lookup to Contact o Referrer - lookup to SystemUser o Job Posting - lookup to JobPosting
* SystemUser
o Manger - lookup to SystemUser o Time-Zone Offset
* Recruiter
o Recruiter identifier o Recruiter name
Applications
There may be multiple applications associated with each job posting. Applications are linked to an employee record if an employee referred the applicant for a position. The same individual can be an applicant for multiple job postings.
Interviews
Each interview is performed by an employee and is related to a single application.
The interview scheduling process may force potential candidates to accept interviews at unusual times with the senior team members due to time-zone differences.
Interview scheduling
The system must provide recruiters with a list of team members and their time-zone information. You must create a Microsoft Power Apps Component Framework (PCF) control for the Job Application form to display a list of senior team members who report directly to a hiring manager.
* The control must display the current time in each team members local time.
* The control must be bound so that it minimizes the amount of code that must be written.
* You must display the list of team members and sort the list to show team members who reside in time zones closest to the applicant's time zone first.
You must develop a second PCF control that displays the time-zone name and current time on the Job Application form. You must display the data in the candidate's local time.
Historical information tracking
You must create a process to identify individuals as a person of interest that the company should consider hiring. You must assign each individual a score based on their past interactions.
* You must be able to determine the following information about a candidate:
o The number of interviews in the past two years and whether team members provided recommendations o The number of hiring manager referrals and employee referrals in the past two years o Whether the individual has any of the 12 designations or certifications that the company considers significant
* Only a single referral can be made per job application. The system must be able to support multiple referrals for a candidate.
* The system must track referrals even if an application is not completed.
Historical information scoring
The automated process must run weekly to assess all candidates. The process must also run automatically when historical information is updated. You must be able to perform scoring by selecting a command button on the contact form.
* This new command button must only be visible to employees who belong to a security role assigned named Recruiter. The command button must not be visible to anyone unless the contact form is in Update mode.
* A person of interest is defined as having a score of 15 or more based on the following historical information criteria:
o Each interview with a recommendation adds two to the score.
o Each interview without a recommendation subtracts two from the score.
o Each employee or manager referral adds one to the score.
o Each designation or certification adds one to the score.
* All scoring elements must be recalculated when changes occur. You must assign the score to the Person of Interest field.
* Values representing totals or scores must be stored in their own numeric fields.
* Plug-ins must be used to keep the Person of Interest field on active interview records associated with the Contact.
* Plug-ins registered on the update of the Person of Interest field must send an email notification when the candidate named in the email is a person of interest. Recruiters must receive the message when the field is updated on the Contact record.
* Interviewers must get an email notification when the Person of Interest field on the interview record is successfully updated.
Design guidelines
The following design guidelines must be followed:
* Schema changes must be made using the method requiring the least amount of storage to meet the requirement.
* Out-of-the-box functionality must be used when possible.
* Any code required to calculate scores must be able to be run from a single point.
* Email notifications need to be kept to a minimum.
Issues
* Recruiters report that the command button to score a candidate is not working. You debug the code and observe that the context input parameter is null.
* The system does not support associating designations and certifications with candidates.
* The value for the field used by the PCF control to display local time is saved to Microsoft Dataverse each time an active application record is opened.
* Interviewers report that they do not receive email notifications when interview records are created for an existing person of interest.

Explanation:

Box 1: No.
An alternate key is needed, not a new field for the record identifier.
Box 2: Yes
The specified key attributes are not a defined key for the account entity.
Name: EntityKeyNotDefined
Message: The specified key attributes are not a defined key for the {0} entity Box 3: Yes One way to create an entity is by using the UpsertRequest class. An upsert will create a new entity when there is no existing record that has the unique identifiers included in the entity passed with the request.
Box 4: No
Reference:
https://docs.microsoft.com/en-us/powerapps/developer/common-data-service/org-service/web-service-error- codes
https://docs.microsoft.com/en-us/powerapps/developer/common-data-service/org-service/entity-operations- update-delete#use-upsert