The Earn Badge Action is still undergoing beta testing. Before configuring this Action, you should be aware that breaking changes may be made to this feature's code and may require you to manually change this Action's configuration.

To turn on the Badges Beta Feature, navigate to your corporation's Administration page and select Edit Corporation from the left-hand menu.

Select the Beta Features tab.

Select the Badges (Experimental, breaking changes likely) checkbox.

Select Update to save.

Navigate to the Actions node of your Orchestrating App.  

Add a new Earn Badge Action.

The configuration of this Action is highly customizable. We'll run through some tips for configuring the available properties and then show a quick example of a possible configuration:

• Badge Name: This is the name of the badge that will be earned by the Orchestrating App after all target Records have completed earning their badges. App Creators often include this name in the Portal Widget we'll configure in Step 3.
• Badge Work Type: This property determines what type of relationship the App and the Action are supposed to track progress on:
  • Direct Action: If your Orchestrating App and your Target App are the same, you'll want to choose this option. You will need to define the Orchestrating App under App if you select this option.  You do not need to define the Relationship, or App Filter property .
  • Loop on Related Transactions: If badges should be earned on a related App's Records, you'll want this option. If you select this option, you'll also need to select the related Field name for the Relationship property below.  You also need to define the App, which is related by the Relationship Field. 
  • Loop on Filtered App: If badges should be earned on an unrelated App's Records, use this option. You can then select the Orchestrating App for the App property and select a Filter for the App Filter property.

• Actions: Select the Actions the target Records will need to process in order to earn their badge in the order that they should be triggered. The Actions selected here should belong to the related, filtered App.  Only in the case of Direct Action being selected as Badge Work Type do the actions belong to the current App.
• Actions to run when complete: You can optionally provide one or more Actions that should be triggered after all the target Records have earned their badges.  Actions ALWAYS belong to the Current App.
• Success Condition: You can optionally trigger Actions if Records meet or fail to meet some criteria. This property comes populated with a condition that will check to ensure the number of target Records with badges equals the number of successful badges received.
• Actions to run when successful: You can optionally use this property to trigger any Actions when your Success Condition is met, (i.e., returns a value of `true`).  Actions ALWAYS belong to the Current App.
• Actions to run when not successful: Similarly, you can optionally use this property to trigger any Actions when your Success Condition is not met, (i.e., returns a value of False).  Actions ALWAYS belong to the current App.

Let's look at an example configuration quickly. In the screenshot below, we're configuring an Earn Badge Action on an Orchestrating App that is responsible for executing some Actions on a Target App:

1. The Actions, which were previously configured on the child App, update each Target App's child Record and add a comment to it.
2. Once all children Records have received their badges, the Orchestrating App fires an Add Comment Action to add a comment to the orchestrating Record.
3. A success condition checks to see that all the child Records have successfully earned their badges.
4. If successful, they fire a Send Success Notification Action.
5. If unsuccessful, they fire a Send Failure Notification Action.

The last thing you'll need to do is configure a Portal Widget that will provide your end users insight into the progress, success, and failure of the Earn Badge Action.

You'll want to use the following Liquid filters to retrieve this information:

{{atom.badges.last.name}}
{{atom.badges.last.total_time}}
{{atom.badges.last.child_badges.size}}
{{atom.badges.last.failed_badges.size}}
{{atom.badges.last.successful_badges.size}}

Below is some HTML that will build out a very simple Widget to get you started. However, in more advanced configurations you may use Liquid and Javascript to create a more dynamic presentation for this information:

<table align="center" width="100%">
<tbody>
<tr>
  <td>
  <div class="counterwidget panel" style="margin: 0; box-shadow: 0 2px 2px 0 rgba(0,0,0,.14),0 3px 1px -2px rgba(0,0,0,.2),0 1px 5px 0 rgba(0,0,0,.12) !important;">
    <table align="left" width="90%" style="margin:10px; font-size: 13px; color: #000; background-color: #fff; border-top: 0px; padding-top: 0px; padding-bottom: 0px;">
      <tbody>
      <tr>
        <td><b>Badge earned:</b></td>
        <td>{{atom.badges.last.name}}</td>
      <td><b>Total:</b></td>
      <td>{{atom.badges.last.child_badges.size}}</td>
      </tr>
      <tr>  
        <td><b>Status:</b></td>
        <td>{{atom.badges.last.status}}</td>       
      <td><b>Succeeded:</b></td>
      <td>{{atom.badges.last.successful_badges.size}}</td>
      </tr> 
      <tr>
        <td><b>Total Time:</b></td>
        <td>{{atom.badges.last.total_time}}</td>
      <td><b>Failed:</b></td>
      <td>{{atom.badges.last.failed_badges.size}}</td>
      </tr>
      </tbody>
    </table>
  <div class="clearfix"></div>
  </div>
  </td>
</tr>
</tbody>
</table>

Below is a screenshot of that Portal Widget rendered on the View Page:

Your Earn Badge Action can be triggered as part of your Orchestrating App's workflow but it is most common to configure an Action Button to fire it.

For purposes of this tutorial, we have created an Action Button named Earn Updated Badge.

That's all there is to setting up a basic Earn Badge Action.

You can test out your configuration by hopping over to one of your Orchestrating App's Records and using the Action Button. Notice that your Portal Widget's data will update at minimum every five seconds, displaying how many badges are still pending, are successful or have failed.