Skip to main content

​
Tango Create MAC Request Inbound API

Generated from Tango Create MAC Request Inbound API Integration Design Specification V0.6.docx in SharePoint folder 03 Space Integrations. OAS spec: mac-request-inbound.yaml

​
Overview

Async REST API for creating MAC (Move/Add/Change) requests in Tango. Request type drives which from_* / to_* fields are populated. Owner: Tango Analytics Spec version: 0.6 Status: Draft (auto-generated — needs review)

​
Endpoints

​
Integration logic

​
Data model (required ✅)

​
Validations

  1. CLIENT_REQUEST_NUMBER NULL → Client Integration Id is missing
  2. requested_for NULL/invalid → Employee ID is invalid or missing
  3. requested_by NULL/invalid → Employee ID is invalid or missing
  4. request_type invalid → Request Type is invalid

​
Open Questions / Assumptions

  • from_area typed VARHCAR (typo for VARCHAR) in source mapping. Preserved.
  • Naming asymmetry: n_ext_lov* and d_ext_lov* use _lov suffix while c_ext_attr* and c_ext_lov* follow a different pattern. Likely a copy-paste error — confirm whether numeric/date extensions are _attr or _lov.
  • from_locker / to_locker flagged in source as not yet existing in Tango. Spec includes them but they may not be wired up.
  • Validation #1 references CLIENT_REQUEST_NUMBER but field is ext_request_number. Assumed same field, different label.
  • requested_date uses YYYY-MM-DD, not MM/DD/YYYY like other Tango APIs. Confirm.
  • Source references SNOW (ServiceNow) as the upstream system — the Field column in data mapping lists SNOW field names.
  • Host URL is placeholder <<hostname>>/<<context>> in source.

​
Changelog