
Joiner–Mover–Leaver Automation & Data Mapping
N.B. Include audit trail expectations and retention periods consistent with [ComplianceFramework]. Specify how to handle retroactive corrections and who approves them.
📄 Prompt Template
Design an automation blueprint linking [HRIS_System] (source of truth), [DirectoryService] (identity), and [ITSM_Tool] (approvals) to provision/deprovision access cards on JML events. Define field mappings, triggers, idempotency, and retries; include data retention [DataRetention_Days] days and [PIIRisk_Level] risk controls. Address API constraints such as [API_RateLimit].
Output format:
Field mapping table (Markdown): HR Field | Directory Field | Access System Field | Transform | Required.
Sequence diagram (Mermaid code block) from event to activation/deactivation.
Error-handling matrix (Markdown): Failure | Detection | Retry | Compensating Control | Owner.
Data quality checks (bulleted) with thresholds.
Governance roles and change control process (numbered).
Ensure SoD between requesters, approvers, and fulfilment.