@7365admin1/module-hygiene 4.29.1-staging.12 → 4.29.1-staging.14

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -0,0 +1,5 @@
1
+ ---
2
+ "@7365admin1/module-hygiene": patch
3
+ ---
4
+
5
+ Area import: units listed on an imported area are saved. The import passed each unit id as an ObjectId, which the area schema refuses, so every imported area that listed units failed to save.
@@ -0,0 +1,9 @@
1
+ ---
2
+ "@7365admin1/module-hygiene": patch
3
+ ---
4
+
5
+ Decide which approve finishes a checklist set from approve/reject, the same rule
6
+ the units list uses, instead of the unit `status` field. Units at rest carry
7
+ "open" or "closed", so the old check never saw a set as finished: a set holding a
8
+ rejected unit could not be completed, and the finishing tick was not recognised.
9
+ No change to when a photo is required, and no schema or data change.
@@ -0,0 +1,9 @@
1
+ ---
2
+ "@7365admin1/module-hygiene": patch
3
+ ---
4
+
5
+ Require the completion photo only on the approve that FINISHES a set, not on
6
+ every unit tick. A task in this product is a set: both the web checklist and the
7
+ five field apps tick units one at a time and open the photographs dialog on the
8
+ tick that completes the set. The previous rule demanded a photo on every
9
+ approve, which refused every intermediate tick on both platforms.
package/dist/index.d.ts CHANGED
@@ -388,6 +388,10 @@ declare function useAreaChecklistRepo(): {
388
388
  updateAreaChecklist: (_id: string | ObjectId, value: TAreaChecklistUpdate, session?: ClientSession) => Promise<number>;
389
389
  updateAreaChecklistStatus: (_id: string | ObjectId, status: (typeof allowedStatus)[number], session?: ClientSession) => Promise<number>;
390
390
  updateAreaChecklistUnits: (_id: string | ObjectId, set: number, unitId: string | ObjectId, value: TAreaChecklistUnitsUpdate, session?: ClientSession) => Promise<number>;
391
+ readSetCompletionState: (_id: string | ObjectId, set: number, unitId: string) => Promise<{
392
+ completesSet: boolean;
393
+ hasEvidence: boolean;
394
+ }>;
391
395
  getMaxSetNumberForArea: (areaId: string | ObjectId, session?: ClientSession) => Promise<any>;
392
396
  closeExpiredAreaChecklists: () => Promise<number>;
393
397
  pushScheduleTaskSets: (scheduleId: string | ObjectId, serviceType: TAppServiceType, areaId: string | ObjectId, scheduleTaskId: string | ObjectId, newSets: TAreaChecklist[]) => Promise<number>;