Noticias en tiempo real

It is the playgroud having issues. I am facing the same issue. Data Stream last run status is success. However, in Data Explorer, it says both DLO and DMO are not existing 

Hi @JANAGAMA SAI CHARAN TEJA, 

Start by checking the "Owned by members of" setting  

- Setup > Security > Sharing Settings. Find the sharing rule  

- Select which records to be shared - ensure that "Owned by members of:" is explicitly set to Roles: Recruiter  

If that doesn't work, check the record ownership. Make sure the owner is assigned the recruiter role  

Last, you might need to recalculate the sharing rules. Go to the sharing rule and click the Recalculate button. 

Security > Sharing Settings." style="display: block;" /> 

Ref:

Security > Sharing Settings." style="display: block;" />

@Harmeet Singh

You can drop the Protected Custom Setting and the manual refresh entirely - use an External Credential (the new Named Credential model) instead of the old No-Auth pattern, and the platform mints and auto-refreshes the token for you. 

1. External Credential - Authentication Protocol OAuth 2.0, Flow Type 'Client Credentials with Client Secret Flow'. This is the exact server-to-server case: the subscriber supplies Client ID + Secret and Salesforce generates and refreshes the access token natively - no token in a custom setting, no refresh code. 

2. Named Credential - points to the API endpoint and references that External Credential. In Apex just call callout:YourNamedCredential/path and the Bearer header is injected. 

3. Grant access with a Permission Set (External Credential Principal Access). 

All three are packageable; after install the subscriber only populates the Principal's Client ID + Secret, so auth stays isolated from your package logic - exactly what an AgentExchange security review wants. 

if this helps, please mark it as the Best Answer so it helps the next person - thanks 🙂

Hello @Swetha S,  

You can try the below options

• Clear the browser cache -> Logout & log in again then check the challenge
• Check your challenge in incognito mode/Private Window or a different browser.

If still you face the same error, delete and create it again then try to check your challenge or I will recommend that you create a new playground and complete this task there.

Hello, 

I was able to resolve the issue by first installing package

The package provides its own Candidate and Position fields, so I updated both fields on the Job Application object by changing them to Lookup Relationships. During the setup, I made sure to grant Read Access while leaving Edit Access unchecked for both fields.

After that, I followed the remaining challenge steps and configured the Manage Job Applications permission set. Under Object Settings > Job Applications, verify that all fields have both Read and Edit access, except for Candidate and Position, which should have Read Access only.

Once these settings were in place, the challenge validated successfully.