AXIS API integration Analysis

[abin-aot]

Title of ticket:

Description

Dependencies

Are there any dependencies?

DOD

• [ ] API Integration POC
• [ ] Low level code integration with API endpoint to do REquest POST, GET etc.
• [ ] Get request number from AXIS
• [ ] Request opened in Flow is opened in AXIS

[abin-aot]

As per meeting with ATIP/Vendor, the APIs are not still not ready as promised. So for AXIS integration or Technically, to make a data sync. between AXIS and new FOI Flow, a Plan B development route is possible. Lets discuss that possibility , if we feel that AXIS Vendor dependency is not viable option. @lmullane @m-prodan @mpilchar @arielleandrews

[abin-aot]

@arielleandrews @mpilchar @m-prodan @lmullane

Plan B for AXIS Integration

• Create/Develop an API inside firewall accessing AXIS Database

• This API will fetch the Request Details from AXIS DB(SQL Server) and serve it for our FOI Flow Application

• Benefits : there is no need for manually entering AXIS Updates to FOI Flow app. Anyhow, we need to create a reference on FOI Flow with AXIS Request Identifier . This "Sync-ing" process can be automatically as well as with a user interaction upon a proper review on the data. This can be decided.

• Why API inside Firewall ? - Reason is because of the same reason we had with "File Conversion". Accessing an IP on Openshift need a full opening of entire IP Range - which will be an issue for IMB and OC folks - same as earlier

• Bit to plan , design, architect around integrate area - including Data flow, data fields to be Sync'd etc.

• IF NOT DONE, what is issue ? - Manual Data Entering is required, Source of truth confusions around Data even with Pilot ministries.

• How much is effort ? - API Development, Deployment on VMs we have, Integration with FOI Flow App(automated or user triggered) - ~ 2-3 sprints

• IMB Involvement will be required to expose API endpoints to DMZ/Openshift. So need to plan , strategize accordingly to align with their schedules.** IStore requests***