@feedmepos/mf-hrm-portal 2.3.0-dev.2 → 2.3.0-dev.20

package/dist/src/views/scheduling/schedule-store.d.ts

@@ -1,6 +1,6 @@
 import ScheduleAPI from '@/api/schedule';
 import type { IFdtoPosUserSummary } from '@/types/employee';
-import type { FdtoScheduleAssignment, FdtoScheduleAutoScheduleApplyReq, FdtoScheduleAutoScheduleApplyResult, FdtoScheduleAutoScheduleCapabilities, FdtoScheduleAutoScheduleGenerateReq, FdtoScheduleAutoScheduleResult, FdtoScheduleBulkUpdateAssignmentStatusReq, FdtoScheduleCreateEmployeeProfileReq, FdtoScheduleSaveAssignmentReq, FdtoScheduleSavePositionReq, FdtoScheduleSaveScheduleDayReq, FdtoScheduleUpdateEmployeeProfileReq, FdtoScheduleCreateTimeOffReq, FdtoScheduleTimeOff, FdtoScheduleUpdateTimeOffStatusReq, FdtoScheduleSaveEmployeeConfigsReq, ScheduleReplaceDemandReq } from '@/types/schedule';
+import type { FdtoScheduleAssignment, FdtoScheduleAutoScheduleApplyReq, FdtoScheduleAutoScheduleApplyResult, FdtoScheduleAutoScheduleCapabilities, FdtoScheduleAutoScheduleGenerateReq, FdtoScheduleAutoScheduleResult, FdtoScheduleBulkUpdateAssignmentStatusReq, FdtoScheduleCreateEmployeeProfileReq, FdtoScheduleSaveAssignmentReq, FdtoScheduleSavePositionReq, FdtoScheduleSaveScheduleDayReq, FdtoScheduleSaveSettingsReq, FdtoScheduleSettings, FdtoScheduleUpdateEmployeeProfileReq, FdtoScheduleValidatePosAccessReq, FdtoScheduleCreateTimeOffReq, FdtoScheduleTimeOff, FdtoScheduleUpdateTimeOffStatusReq, FdtoScheduleSaveEmployeeConfigsReq, ScheduleReplaceDemandReq } from '@/types/schedule';
 import { isoDateKey } from './composables/schedule-calendar';
 export { businessEmployees, dataVersion, employeeOutletIds, loadError, loading, outletId, payload, restaurantEmployees, employeeConfigs, rosterLoading, scheduleSetupCompleted, } from './schedule-state';
 /** dayjs-free local-date key — the board's own isoDateKey, repeated here so the store does not
@@ -21,6 +21,8 @@ export declare function setOutlet(restaurantId: string): boolean;
  * headcounts sit nowhere near it. */
 export declare function ensureRestaurantEmployeesLoaded(restaurantId: string): Promise<void>;
 export declare function saveEmployeeConfigs(configs: FdtoScheduleSaveEmployeeConfigsReq['configs']): Promise<void>;
+/** Saves outlet settings and keeps the board payload authoritative for any later cache rebuild. */
+export declare function saveScheduleSettings(req: FdtoScheduleSaveSettingsReq): Promise<FdtoScheduleSettings>;
 export declare function setEmployeeSchedulingEnabled(employeeId: string, enabled: boolean): Promise<void>;
 /** Re-reads this outlet's POS roster. The roster is what the board's rows are built from and is
  * otherwise fetched once per outlet, so any write that changes who works here (add, remove)
@@ -30,11 +32,32 @@ export declare function refreshRestaurantEmployees(): Promise<void>;
 export declare function addEmployeeToOutlet(employeeId: string, roleId: string): Promise<void>;
 /** Adds an employee to several outlets at once. Scheduling does not require a POS role, so the
  * caller may pass an empty role id and assign the POS role later from Employee. */
-export declare function addEmployeeToOutlets(employeeId: string, restaurantIds: string[], roleId?: string): Promise<void>;
+export declare function addEmployeeToOutlets(employeeId: string, restaurantIds: string[], roleId?: string, enableScheduling?: boolean): Promise<void>;
 /** Takes a POS user off the given outlets' rosters; their other outlets are untouched. */
 export declare function removeEmployeeFromOutlets(employeeId: string, restaurantIds: string[]): Promise<void>;
 /** Takes a POS user off this outlet's roster only. */
 export declare function removeEmployeeFromOutlet(employeeId: string): Promise<void>;
+/** Sets the POS role each of these outlets grants a user — every other outlet on their roster
+ * is untouched. An empty roleId means "linked to this outlet, no role assigned" (the same thing
+ * `addEmployeeToOutlets`' default gives), not "remove them from it" — use
+ * `removeEmployeeFromOutlets` for that. A duplicate restaurantId keeps only the last entry. */
+export declare function setEmployeePosRoles(employeeId: string, assignments: {
+    restaurantId: string;
+    roleId: string;
+}[]): Promise<void>;
+/** Saves the POS-owned part of an existing scheduling employee. The scheduling profile and the
+ * POS user are separate records, so passcode/master-user changes must use the POS user API too.
+ * A normalized comparison avoids rewriting the POS user when the employee form was unchanged. */
+export declare function saveEmployeePosAccess(employeeId: string, request: {
+    name: string;
+    passcode: string;
+    masterUser: boolean;
+    masterCode: string;
+    roles: {
+        restaurantId: string;
+        roleId: string;
+    }[];
+}): Promise<void>;
 /** The cached business roster, fetched on first use. `force` re-reads it (after a write, or to
  * refresh a list that is already on screen). Concurrent callers share one request. */
 export declare function ensureBusinessEmployees(force?: boolean): Promise<IFdtoPosUserSummary[]>;
@@ -54,6 +77,7 @@ export declare function reload(): Promise<void>;
  * Throws on failure (a duplicate profile, a network error) — the caller decides how to show
  * that, this just doesn't pretend it succeeded. */
 export declare function createEmployeeProfile(req: FdtoScheduleCreateEmployeeProfileReq): Promise<void>;
+export declare function validateSchedulePosAccess(req: FdtoScheduleValidatePosAccessReq): Promise<void>;
 /** Edits a profile already on this outlet's schedule. The caller (useScheduleAddEmployee's
  * `updateExisting`) applies the form to the live `Employee` object itself for instant feedback,
  * so this does not bump `dataVersion` — nothing needs a board cache rebuild. The raw payload is
@@ -77,28 +101,29 @@ export declare function deletePosition(id: string): Promise<void>;
  * to land there for that seed to stay correct — without a `dataVersion` bump, which would
  * invalidate the per-week employee cache and risk reverting an unsaved shift. */
 export declare function saveScheduleDay(date: string, req: FdtoScheduleSaveScheduleDayReq): Promise<void>;
-/** Replaces one date/weekday's UI demand by expanding every period into flat ShiftDemand rows.
+/** Replaces one date's UI demand by expanding every period into flat ShiftDemand rows.
  * Position-specific headcount becomes its own row; any remaining headcount becomes an
  * unpositioned row for the same time range. */
 export declare function saveDemand(req: ScheduleReplaceDemandReq): Promise<void>;
+export declare function saveDemandsBulk(requests: ScheduleReplaceDemandReq[]): Promise<void>;
 /** Copies one date's own demand rows onto another date, as that date's own rows. A date that
  * already has demand of its own is left alone (nothing is overwritten), and a source date with
- * none has nothing to copy: the standing weekday rule already covers the same weekday in every
- * week, so repeating it per date would only shadow later edits to the rule. Returns how many rows
- * were written. */
+ * no explicit rows has nothing to copy. Returns how many rows were written. */
 export declare function copyDateDemand(fromDate: string, toDate: string): Promise<number>;
 export declare function generateAutoSchedule(req: FdtoScheduleAutoScheduleGenerateReq): Promise<FdtoScheduleAutoScheduleResult>;
 export declare function getAutoScheduleCapabilities(): Promise<FdtoScheduleAutoScheduleCapabilities>;
 export declare function applyAutoSchedule(req: FdtoScheduleAutoScheduleApplyReq): Promise<FdtoScheduleAutoScheduleApplyResult>;
 /** A one-off shift assignment — someone working these hours on this date, not answering any
- * Shift requirement. Deliberately does not reload: unlike `createEmployeeProfile` above, there
- * is nothing here a reload could bring back that the caller doesn't already have — `commitShift`
- * writes `assignmentId` onto the slot itself once this resolves, and a reload would only risk
- * discarding some OTHER unsaved shift elsewhere on the board (shifts have no write path of
- * their own to read back from yet). */
+ * Shift requirement. Keep the raw payload in sync without bumping `dataVersion`: the current
+ * board owns the live draft, while a later roster refresh may rebuild the week cache from this
+ * payload. */
 export declare function createAssignment(req: FdtoScheduleSaveAssignmentReq): Promise<FdtoScheduleAssignment>;
 export declare function updateAssignment(id: string, req: FdtoScheduleSaveAssignmentReq): Promise<FdtoScheduleAssignment | null>;
 export declare function bulkSaveAssignments(req: Parameters<typeof ScheduleAPI.bulkSaveAssignments>[1]): Promise<Awaited<ReturnType<typeof ScheduleAPI.bulkSaveAssignments>>>;
+/** Replaces demand and/or assignments in one backend transaction. */
+export declare function copySchedule(req: Parameters<typeof ScheduleAPI.copySchedule>[1]): Promise<Awaited<ReturnType<typeof ScheduleAPI.copySchedule>>>;
+/** Clears demand and/or assignments in one backend transaction. */
+export declare function clearSchedule(req: Parameters<typeof ScheduleAPI.clearSchedule>[1]): Promise<Awaited<ReturnType<typeof ScheduleAPI.clearSchedule>>>;
 /** Deletes a batch of existing assignments in a single request — see
  * `ScheduleAPI.deleteAssignments`. Deleting one is just this with a single-id array. */
 export declare function deleteAssignments(ids: string[]): Promise<void>;

package/dist/src/views/scheduling/types.d.ts

@@ -8,6 +8,8 @@ export interface WorkSlot {
     start: string;
     end: string;
     role: string;
+    /** The persisted position identity, retained even when the position is soft-deleted. */
+    positionId?: string;
     status: ShiftStatus;
     clock?: ShiftClock;
     conflict?: boolean;
@@ -98,13 +100,18 @@ export interface Employee {
     /** Full-time-equivalent percentage, e.g. 100 for a full-timer, 60 for 0.6 FTE. */
     pct: number;
     /** Hours per week this person is contracted to, as agreed with them. Per-person rather than
-     * a venue default: ScheduleSettings holds pay rates only, and EmployeeProfiles.workingHour
+     * a venue default: ScheduleSettings holds pay rates and employee-hour defaults, and EmployeeProfiles.workingHours
      * is where the figure is actually stated. Undefined means nobody has agreed one. */
     contractHours?: number;
     rate: number;
     positions: string[];
+    /** Position references that remain on the employee profile but are no longer active in the catalogue. */
+    archivedPositions?: string[];
     /** One entry per visible day of the horizon; null = day off. */
     shifts: DaySlot[];
+    /** Dated time-off records are kept beside shifts so an off/leave card remains visible when
+     * a manager adds a shift on the same day. */
+    timeOff?: Array<LeaveSlot | null>;
     remarks: EmployeeRemark[];
     section: string;
     compGroup?: string;
@@ -117,11 +124,18 @@ export interface Employee {
      * hourly figure derived from this and is what the grid actually costs shifts with. */
     payAmount?: number;
     maxHours?: number;
-    maxOtHours?: number;
     /** Shortest shift, in hours, this person will come in for. Asking for less is allowed but
      * warned about in the shift popover. */
     minHours?: number;
-    otAfterDaily?: number;
+    minHoursPerDay?: number;
+    workingHours?: {
+        minHoursPerDay: number | null;
+        maxHoursPerDay: number | null;
+        maxHoursPerWeek: number | null;
+    };
+    overtime?: {
+        maxHoursPerMonth: number | null;
+    };
     preferences?: string[];
     seniority?: 'senior' | 'junior' | '';
     /** Recurring days off (full-timer) or days available (part-timer) — see
@@ -130,6 +144,8 @@ export interface Employee {
     availHours?: EmployeeAvailHours[];
     /** POS sign-in code. Optional: rostering, costing and publishing never depend on it. */
     passcode?: string;
+    /** POS master-user code, when this employee is a master user. */
+    code?: string;
     masterUser?: boolean;
 }
 export interface Section {
@@ -200,7 +216,6 @@ export interface ScheduleRules {
         end: string;
     }>[];
     payRate: PayRate;
-    otAfterDaily: number;
     /** Weekly sales forecast (RM) — the stats row's editable input and the figure the
      * per-day forecast curve distributes across the week. */
     salesForecast: number;
@@ -215,7 +230,12 @@ export interface ScheduleRules {
     /** Weekly labour cap (RM), editable directly when budgetFromSales is false. */
     budget: number;
     /** Monthly OT cap (hours) — Settings page "Overtime" tab. */
-    otCapHours: number;
+    otCapHours: number | null;
+    workingHours: {
+        minHoursPerDay: number | null;
+        maxHoursPerDay: number | null;
+        maxHoursPerWeek: number | null;
+    };
     /** Monthly OT budget (RM), advisory only. */
     otBudget: number;
     notify: {
@@ -290,6 +310,8 @@ export interface ScheduleDayNote {
  * "any position" remainder, which is derived and never stored. */
 export interface DemandRole {
     position: string;
+    /** Persisted position identity; the name is only the display label. */
+    positionId?: string;
     n: number;
 }
 /** A stretch of a day and how many people the floor needs across it. Deliberately not a shift:
@@ -353,4 +375,6 @@ export interface Proposal {
     weekKey?: string;
     /** Why this person, for the card's tooltip. */
     reason?: string;
+    /** Set when the server already knows applying this row would be refused; it starts rejected. */
+    rejectReason?: string;
 }