Uploaded image for project: 'CFA MX '
  1. CFA MX
  2. CFAMX-22697

Signal Integration -> Transfers -> Implement Actual Signal API Endpoints for Create and Receive/Deny Transfers instead of Dummy API Endpoints

    Details

    • Type: Story
    • Status: Closed (View Workflow)
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None
    • Sprint:
      2023.R3 Signal Int. Sprint 3
    • SCRUM Team:
      Globogym Purple Cobras
    • Story Points:
      3
    • Work Type Classification:
      Sustaining

      Description

      Story

      As an admin, I would like to have actual api calls implemented when creating, receiving, and transfers instead of dummy api endpoints. 

       

       

      Description 

      here is the okta authentication info:

      name: test-inform-signal-integration
      client_id: 0oa1i6qjcrmBMaqbH0h8
      client_secret: Gki6QnfU1Q5MRleW11cZ9KtU8gA4LfvuzZ2VC21x
      token_url: https://cfahome.oktapreview.com/oauth2/ause935uhauRMpJuP0h7/v1/token

       scope: inform-transfers:write

       

      Signal team will provide a GET transfers api in the near future to verify our API calls to signal side. 

       

      Sending Store is in Signal - Receiving Store is in Inform

      To Create

      Signal Calls -> Inform Create Transfer API​

      • Sending (Creator) Store won't have inv pages available in Inform​
      •  Signal will be calling create transfer Inform API. We will return inform transfer id​

      To Receive

      Inform Calls -> Signal Receive/Deny Transfer API    ​

      • Receiving Store is Inform store has access to Receive Transfer Page​
      • Inform calls Signal API endpoint to receive/deny transfers via inform transfer id

       

       

      Sending Store is in Inform  - Receiving Store is in Signal​

       

      To Create

      Inform Calls -> Signal Create Transfer API​

      • Sending store which is in Inform. The transfer will be created when the user clicks create button from UI.​

      To Receive

      Signal Calls -> Inform Receive/Deny Transfer API    ​

      • Receiving Store won't have access to Inform Inventory pages. So, the transfer will be received through Signal. ​
      • Signal calls Inform API endpoints to receive/deny transfers via signal transfer id​

       

       

      AC

      Confirm that via postman a transfer is created getting a success status should be sufficient for now

      Confirm that via postman a transfer is received getting a success status should be sufficient for now

      Confirm that via postman a transfer is partially received getting a success status should be sufficient for now

      Confirm that via postman a transfer is denied getting a success status should be sufficient for now

      Confirm that in case receiving store is in Signal, the Signal create transfer API is called and successful when creating

      Confirm that in case sending store is in Signal, the Signal receive/update transfer API is called and successful when receiving

       

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                caner.saritac Caner Saritac
                Reporter:
                caner.saritac Caner Saritac
              • Watchers:
                0 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Time Tracking

                  Estimated:
                  Original Estimate - 48h
                  48h
                  Remaining:
                  Remaining Estimate - 0h
                  0h
                  Logged:
                  Time Spent - 11h 8m Time Not Required
                  11h 8m

                    PagerDuty

                    Error rendering 'com.pagerduty.jira-server-plugin:PagerDuty'. Please contact your Jira administrators.