Running the solution
RPA can be scheduled to run in unattended mode. Upon initiation, the automation downloads the list of blacklisted vendors from the OIG website in CSV format. After retrieving the file, the process compares vendor records from FSM against those in the OIG exclusion list. If a name match is found, the automation further validates the vendor using the associated TAX ID or SSN to ensure accurate identification before updating the OIG Exclusion Status on the vendor in FSM.
Once the automation run is complete, these fields for blacklisted vendors identified in FSM are updated accordingly.
- OIG Exclusion Status
- Last OIG Validation Date
OIG exclusion statuses
This table shows the OIG Exclusion statuses and their definitions.
| Status | Definition |
|---|---|
| Matched-Incomplete | This status is rarely assigned. This status indicates that the supplier's name in FSM matches a name on the OIG exclusion list; however, the process was unable to complete successfully due to an unexpected issue and was terminated before full verification. |
| Partial Match | This status means the supplier's name in FSM matches a name found on the OIG exclusion list, but the SSN or TAX ID does not match, which indicates a potential false positive. |
| Match Verified | This status confirms a complete match, both the vendor's name and the SSN/TAX ID in FSM align with the information listed on the OIG exclusion list. |
User arguments
This table shows the user parameters for RPA 1.
| User parameters | Description | Value |
|---|---|---|
| csvFileName | This user parameter is required to download the blacklist available on the OIG website. | UPDATED.csv |
| objectSchema | This is user parameter is required to push blacklisted list into Data Lake using Atlas widget. | OIG_VendorCheck |
| distributionType | This user parameter is used as a setting for sending notifications either for a single user or a group. | USER or GROUP |
| userIdentifier | This user parameter is used to specify the user information in the API to whom the notification must be sent. This information can be captured from user management, for example, IFS ION-Person ID/Group Name. | IFS ION-Person ID or Group Name from . Check for username that must receive the notification and click on the user details to get the ID. |
| ColemanTriggerUrl | This user parameter is the API URL used to trigger ION workflow. | ionapidomain/tenantname/IONSERVICES/process/application/workflow/start?logicalId=lid://infor.iondesk.iondesk |
| notificationAPIUrl | This user parameter is the Notification API URL used to send the notification to the user. | ionapidomain/tenant-name /IONSERVICES/process/application/v1/pulse/notification/create?logicalId=lid://infor.rpa.1 |
| Data Fabric url | This user parameter is the datafabric url to update the data lake. | ionapidomain/tenant-name/ /DATAFABRIC/ingestion/v1/dataobjects |
- notificationAPIUrl
- userIdentifier
- DataFabricUrl
- ColemanTriggerUrl
- distributionType
- csvFileName
This table shows the user parameters for RPA 2.
| User parameters | Value |
|---|---|
| distributionType | USER or GROUP |
| notificationAPIUrl | ionapidomain/tenant-name/ IONSERVICES/process/application/v1/pulse/notification/create?logicalId=lid%3A%2F%2Finfor.rpa.1 |
| fsmAPIUrl | ionapidomain/tenant-name/FSM/fsm/soap/classes/Vendor/actions/UpdateOIGExclusionStatus/batch |
| userIdentifier | IFS ION-Person ID/Group Name |
| cpExclusions_txtSPLastNameXpath | (//tbody)[2]/.//tr[2]/td/div/input |
| cpExclusions_txtSPFirstNameXpath | (//tbody)[2]/.//tr[2]/td[2]/div/input |
| SearchForASingleEntityXpath | //a[.='Search For A Single Entity'] |
| cpExclusions_txtSBNameXpath | (//tbody)[2]/.//tr[2]/td/div/input |
| cpExclusions_datatableXpath | /html/body/div[2]/div[1]/div/div[3]/div[1]/div[2]/form/div[3]/div/table/tbody/tr/td/div/table |
| singleEntity_datatableXpath | /html/body/div[2]/div[1]/div/div[3]/div[1]/div[2]/form/div[3]/div/div[2]/table |
| clickSearchXpath | //input[@id='ctl00_cpExclusions_ibSearchSP'] |
| verifyXpath | //a[.='Verify'] |
| taxSSNXpath | //input[@id='ctl00_cpExclusions_txtSSN'] |
| cpExclusions_ibtnVerifyXpath | //input[@id='ctl00_cpExclusions_ibtnVerify'] |
| cpExclusions_print_verificationXpath | //img[@id='ctl00_cpExclusions_print_verification'] |
| cpExclusions_IbBackToSearchXpath | //a[@id='ctl00_cpExclusions_lbBackToSearch'] |
| vendorResults | empty |
On the Your Arguments tab, include these arguments:
- distributionType
- notificationAPIUrl
- fsmAPIUrl
- userIdentifier
All remaining arguments are configured as Process Arguments.
Leave vendorResults blank, as it is populated through the ION workflow.