Navigate to your Home screen and switch the Application to the Clues Application. You will use this Application to obtain your next clue in the form of a mapping file to map Suspects to their Aliases.
1. Click the “Create Record” Button to create a new clue request, and follow the instructions on the record form.
-
- Request Clue 1 - You will be prompted to set up an Automated Evidence Collection to collect the mapping file needed.
-
Copy of the AEC Form Instructions:
To collect the mapping file for Suspects & Aliases, click + Create New Automation below and follow these steps:
-
Evidence Setup:
- Where is the evidence coming from: Risk Cloud
- Which Application do you want to collect from: Clues
- Which Table Report should be used as evidence: Build Bash 2025 - Mapping File
-
Automation Setup:
-
Keep the following default values as is:
- In which workflow should the evidence be added: Your Mission Clues Workflow in your Application
- In which step should the evidence be added: Clue Repository
- In which field should the evidence be added: Mission Attachments
- Complete the remaining selections however you want to
-
Keep the following default values as is:
-
Review:
- Review the automation you've set up and click "Save" when complete.
-
Evidence Setup:
Review the Create and Configure AEC Automations Help Center page for support.
With your automation setup, navigate to Options → Run Now to run the automation and collect your mapping evidence file.
Navigate to your Mission Clues Table Report, and find the evidence attached in the “Mission Attachments” Field. Now that your team has collected the Mission Mapping File, you can successfully match Suspects to their Aliases. Follow these steps to get one step closer to finding the rogue agent:
- Navigate to the [Work] tab → Link Records to map Suspects to their Aliases in your Application.
ALERT: If you get an error message when trying to bulk map your records, this means the rogue agent may have tampered with the files to create confusion by assigning aliases to multiple suspects. If this occurs, carefully examine the error message and correct the mapping file by reviewing and deleting all duplicate records causing errors. Complete the mapping and take note of the suspects that caused the errors, as these are likely your primary suspects.
2. Once you've completed the mapping of Suspects to Aliases, you will have suspects that are not linked to an alias because of the rogue agent tampering with the mapping file. Navigate to the Suspects Workflow and create a new "Linked Records Count" Field to easily flag which suspects do or do not have a linked alias. Create label ranges so Linked = 1, Not Linked = 0. Add this new Field to your Suspects Table Report you created earlier. Visit the Linked Record Count Fields Help Center Article for support.
3. You've narrowed down the list of suspects to the unlinked records. To focus on these primary suspects, navigate to the [Work] tab → Bulk Actions → Update Fields. Use the Bulk Update Fields action to update the "Primary Suspect?" Field in the Suspects Workflow to Yes for the unlinked records. Create a new table report called "Primary Suspects" and add a filter to only include the primary suspects. Add this report to your Home Screen.
4. Once complete, navigate back to the request clues record for your team and request clue #2.
Once you've requested Clue #2 and completed the instructions outlined there, move on to the final phase. Search the Help Center for the article "Build Bash - The Final Code" to get started.