Health Cloud Specialist Superbadge

Challenge 4:

• Create record type on Person Account Object.
• Configure Custom record type for individual. Create a new record in custom metadata with name "Individual Record Type Mapper". This is an existing metadata custom setting. See below screen shot. 
• Make sure you selected Console navigation as the Navigation Style when creating the app.
• Create patient record in account object.

https://developer.salesforce.com/docs/atlas.en-us.health_cloud.meta/health_cloud/admin_config_custom_record_type.htm?search_text=configure%20custom%20record&_ga=2.109255109.1551928910.1679425307-1666235364.1662575682

Error:

If facing this error "We could not find the Patient record type correctly configured under Custom Metadata Types".

Check if you have same name record type on any other object if yes deactivate that.

https://trailhead.salesforce.com/de/trailblazer-community/feed/0D54S00000CfOToSAN

We cant find the expected tabs in the care coordination console app.

I had the same error. Please check all tabs in navigations items in your app. There are two "Home" items.   You should add home page with the pink house icon. And also there are several patients - you need to add Patient tab with lightning icon. 

https://trailhead.salesforce.com/ja/trailblazer-community/feed/0D54S00000FSVmRSAX

Challenge 5:

• Go on care plan template tab and create a new care plan template with name "Diabetes Care Plan Template".
• Enter new care plane template problems
• Enter Goals under care plan template
• Create another care plan template "Care Plan Template for Nutrition Education" with problem mentioned in task
• From Setup, enter Custom Settings in the Quick Find box and select Custom Settings.
• In the list of custom settings, click Manage next to Health Cloud Feature Toggles.
• Click Edit next to Multiple Care Plans and select the Enabled checkbox.
• Click Save
• Household record is already exists with name Suman Household. Just add shankar as patient in that household.

https://trailhead.salesforce.com/ja/content/learn/modules/health-cloud-care-plans/set-up-care-plans

Error:

We can’t find the 'Diabetes Education' case team.

On the Case Team, make sure that Adam is listed first and Martha is listed second. I had to delete Martha, save it, and then add her back on. Then remove the Case team from both of Shankar's Care plans. Refresh the page and add them back on. I was able to clear the error and pass the challenge after that. 

https://trailhead.salesforce.com/ja/trailblazer-community/feed/0D54S00000FSG9O

Challenge 6:

• Go to timeline view configuration object and create one record in it as per screen shot.
• Then go to all list view of timeline view configuration object and activate all existing time line view.

• Enter data in each of the object as per instructions
• Clinical Encounters
• Health Conditions
• Medication Statement
• Patient Immunization
• Diabetes Coaching Session
• Enter some random data in these object and link to shankar
• Contact Preferences
• Medications
• Conditions
• Insurance Plan
• Member Id
• Allergies
• Create spouse link and other user relation.
• Create care Care Intervention Type(go to tab and click new)
• 
  
  
  
  

Error:

1. We can't find the patient card configured according to the requirements.

Make sure you created a new Patient Card Configuration record using the Health Condition object. In order for the conditions to show in the card, you need to populate the Override Filter Field on the configuration record with a field from the Health Condition object that returns true or false. Consider creating a new field on the Health Condition object (optional), like the other objects that show in the card.

1. We can’t find the Patient Timeline with the correct configuration.

Make sure you see all the data in patient timeline.

https://trailhead.salesforce.com/ja/trailblazer-community/feed/0D54S00000Gh9h3

1. We can’t find 'Anna Jones' under Related Contacts for 'Shankar Suman', or we can’t find the expected reciprocal role

Please make sure that you are trying to verify the correct dev org if you have more than one. For me, it looks all good now. If you are still getting the error, please submit a case to Trailhead support, and they can assist further.

https://trailhead.salesforce.com/ja/trailblazer-community/feed/0D54S00000FVs5zSAD

1. We can’t find an account named 'Get Cloudy Health Cloud Super Badge...Consulting' under Related Accounts for 'Shankar Suman', or we can't find the expected role.

https://trailhead.salesforce.com/ja/trailblazer-community/feed/0D54S00000ElwUY

Platform Developer I Certification Maintenance (Winter '23)

First Challenge 

Second Challenge

@isTest

private class DataGenerationTest {

  @testSetup

  static void dataCreation() {

      Account account = TestFactory.getAccount('Muddy Waters Inc.', true);

      Contact contact = TestFactory.getContact(account.Id, 'Muddy', 'Waters', true);

      Opportunity opp = New Opportunity();

      opp.Name = 'Long lost record';

      opp.AccountId = account.Id;

      opp.CloseDate = Date.today().addDays(14);

      opp.StageName = 'Prospecting';

      insert opp;

  }

  @isTest

  static void testBruteForceAccountCreation() {

      List<Account> accts = new List<Account>();

      Test.startTest();

          accts = [SELECT Id FROM Account];

      Test.stopTest();

      Assert.IsTrue(accts.size() > 0, 'Was expecting to find at least one account created on the Test Setup');

  }

  @isTest

  static void testUseTestFactoryToCreateAccountsWithContacts() {

      List<Account> accts;

      List<Contact> contacts;

      TestFactory.generateAccountWithContacts(5);

      Test.startTest();

          accts = [SELECT Id FROM Account];

          contacts = [SELECT Id FROM Contact];

      Test.stopTest();

      Assert.IsTrue(accts.size() > 0, 'Was expecting to find at least one account created');

      Assert.IsTrue(contacts.size() == 6 ,'Was expecting to find 6 contacts');

      Assert.areNotEqual(accts.size(), contacts.size(), 'Was expecting there to be a different number of account and contacts');

  }

  @isTest

  static void testAtTestSetupMethodsRule() {

      List<Opportunity> opps = [SELECT Id, AccountId FROM Opportunity];

      Assert.areEqual(1,opps.size(), 'Expected test to find a single Opp');

  }

}

Copado Certification Maintenance - Fundamentals 1

 Q1. When working with second generation packaging  you can:

    a) Manage package creation, publishing, and distribution from copado UI.

    b) Start using the default rules and code analysis while creating the package version.

    c) Deploy metadata from one salesforce org to another without having to build a new change set.

    d) Integrate critical industry-followed DevSecOps tools.

Answer: Manage package creation, publishing, and distribution from copado UI.

Q2. Which of the following are the improved capabilities of copado CI/CD for second generation?

    a) Leverages source format support.

    b) Provides access to logs and more details executed logic.

    c)Leads to greater stability and authorize further customization.

    d)All of the above.

Answer: All of the above.

Q3. What should you check if you cannot see the Rollback button on your promotion record?

    a) If the rollback feature is enabled in the destination org.

    b) If your profile is assigned the correct license to use the Rollback feature.

    c) If the rollback option is marked as selected in your promotion.

    d) If your user story qualifies to avail of the rollback feature.

Answer: If the rollback feature is enabled in the destination org.

Q4. What is the user of Review Merge Conflict feature in Copado?

    a) To change the conflict resolution strategy and redeploy your changes.

    b) To review the conflict and stop the promotion until the conflict is resolved.

    c) To let copado know that a particular user story requires an auto resolve.

    d) To review user stories potentially conflicting with your current user story.

Answer: To change the conflict resolution strategy and redeploy your changes.

Q5. If your package is in the beta stage, you can distribute it to non production environments only.

    a) true

    b) false

Answer : False

Q6. Which feature enables you to ensure that when you select a child metadata, the parent element nested metadata is also selected?

    a) Commit, Promote, and Deploy flow of copado CI/CD for salesforce 2nd generation.

    b) Commit, Promote, and Deploy copado classic.

    c) Commit, Promote, and Deploy copado DevOps platform.

Answer : Commit, Promote, and Deploy flow of copado CI/CD for salesforce 2nd generation.

Q7. Which of the following tools can be integrated with copado as quality gate?

    a) Copado Continuous Delivery

    b) Copado Robotic Testing

    c) Copado DevOps Platform

    d) Copado CI/CD for salesforce 2nd Generation

Answer:  Copado Robotic Testing

Q8. From the promotion record how can you auto resolve conflicts for multiple user stories?

    a) Select user stories with conflicts and promote them to the next environment. Copado will detect and the resolve the conflict.

    b) Select the auto resolve conflict button in the promotion record and resolve the conflict automatically.

    c) Determine the overlap between the user stories and select the user stories with conflict only for copado to auto resolve the conflict.

    d) Conflicts can not be resolved automatically for multiple user stories. It can only be resolved manually.

Answer: Determine the overlap between the user stories and select the user stories with conflict only for copado to auto resolve the conflict.

Q9. Which copado solution enables you to deploy metadata changes from salesforce org to another without building a new change set?

    a) Copado Continuous Delivery

    b) Copado Essentials

    c) Copado Robotic Testing

    d) Copado CI/CD

Answer: Copado CI/CD

Q10. Which of the following options has been added to the result record for troubleshooting?

    a) View result option.

    b) Logs option in the result record

    c) Status option the result record.

    d) All of the above.

Answer: All of the above.