Reframe deprecated Workmate surfaces around durable workforce aggregates, then select the entitled Mappls modules that satisfy each complete journey.
The current Workmate Android source is the closest identity evidence, while InTouch, Location Capture, and REST remain adjacent modules. No single guide proves complete workforce journey compatibility; the product owner must issue the target contract and entitlements.
Legacy sources are fully covered. Candidate links expose the closest public evidence and its maturity; they do not silently upgrade it to an entitlement or support declaration.
mapmyindia-workmate-apisResolve each dimension explicitly. “It compiled” does not prove identity, lifecycle, failure, privacy, or operational compatibility.
Tasks, attendance, tracking, and proof can be coupled inside one SDK or API surface.
Model worker, task, assignment, visit, proof, and exception aggregates with explicit ownership and transitions.
State diagrams, invariants, event schemas, and recovery test per journey.
Local callback success can be mistaken for authoritative completion.
Persist commands, evidence hashes, observed time, sync state, and server acknowledgement separately.
Multi-day offline, duplicate sync, clock skew, rejected proof, and device replacement tests.
One product credential may have implied several capabilities.
Entitle tracking, capture, search, routing, or workflow modules independently and keep least authority.
Capability-by-role matrix plus negative authorization and revocation tests.
Do not advance on calendar alone. Each stage creates evidence that makes the next one safe and reversible.
Inventory every workforce journey, package, host, credential class, callback, and owner before changing production.
Resolve the exact entitled package or endpoint with Mappls and verify its supported toolchain, region, quotas, authentication, and lifecycle.
Move workforce journey calls behind a narrow application-owned interface without changing product behavior.
Replay approved fixtures and shadow eligible reads while preventing duplicate writes or user-visible duplicate assignments, attendance, or proof.
Release to internal users and bounded cohorts with health gates, ownership, automatic stop conditions, and immutable version evidence.
Remove legacy credentials and dependencies only after rollback and audit retention obligations expire.
These examples deliberately model the seam and verification pattern—not unconfirmed package symbols. Implement the adapters only after the exact target contract is issued.
type Command<T> = {
aggregateId: string;
expectedVersion: number;
idempotencyKey: string;
payload: T;
};
type Outcome = { providerId: string; version: number; state: string };
interface WorkforceProvider {
assign(command: Command<{ workerId: string; taskId: string }>): Promise<Outcome>;
reconcile(aggregateId: string): Promise<Outcome | null>;
}
// Never shadow a write. Send it through one provider, persist the outcome, then
// reconcile an ambiguous timeout by aggregate/idempotency identity before retry.The candidate and exact package/endpoint versions are approved by the owning Mappls product team for the target account and region.
Journey-level contract tests pass on every supported device, browser, architecture, and release build—not only a debug simulator.
Security, privacy, accessibility, performance, quota, observability, and support owners accept measured differences.
A bounded cohort completes the agreed observation window without an unresolved severity-one or severity-two regression.
Stopping traffic is not enough. Recover durable resources, sessions, events, and in-flight commands without duplicates or hidden divergence.
Prepare support packetKeep the previous signed artifact, dependency lock, configuration, and credential valid until the observation window closes.
Make the provider selection server- or release-controlled; define automatic stop signals and one accountable rollback owner.
For durable state, prove backward-readable records or a reversible data migration before allowing candidate writes.
After rollback, reconcile in-flight requests and resources by stable identifiers instead of replaying commands blindly.