Introduction

AM offers users the ability to perform vendor research by submitting a research request for a robotic task to retrieve vendor information.

There are four different robotic tasks that can be executed to complete research activities. All of the robotic tasks are related via the connected system AS AM CS Rpa, which is associated with a service account via the service account's API key. In order to retrieve data from the robotic task execution, the integration AS_AM_INT_getBotDetails is used to query the RPA endpoint using a robotic task execution ID that is returned from the following individual robotic task integrations:

1. FAPIIS: https://www.fapiis.gov/
   • Integration AS_AM_INT_executeFapiisBot
2. GSA: https://www.gsaelibrary.gsa.gob/ElibMain/home.do/
   • Integration AS_AM_INT_executeGsaBot
3. ICD: https://contractdirectory.gov/contractdirectory/
   • Integration AS_AM_INT_executeIcdBot
4. SBA: https://web.sba.gov/pro-net/search/dsp_dsbs.cfm/
   • Integration AS_AM_INT_executeSbaBot

Both the FAPIIS-related action and the initial research action via the Research tab execute a process using the process model AS AM Initiate Research Execution. This process model will:

1. Update the award record if the FAPIIS-related action is triggered.
2. Call the AS AM Execute Bot process model.
3. Create a confirmation checklist item if the FAPIIS-related action is triggered.

The AS AM Execute Bot process model is designed to generically call different robotic tasks. Depending on the robotic task type that is passed from the parent process model, it will call the respective robotic task integration object to initiate and receive the process ID for a robotic task execution, get the data using the robotic task execution ID, and call the respective document generation process model associated with the appropriate robotic task.