@zeniai/client-epic-state 5.2.28 → 5.2.30

package/lib/entity/jeSchedules/jeSchedulesState.d.ts

@@ -145,9 +145,16 @@ export interface JEAccruedScheduledTransactionState extends Omit<JEScheduledTran
 export interface OneTimeAccrualEdits {
     expectedReversalDate?: ZeniDate;
     jeCreditAccountId?: ID;
+    /**
+     * Carried beside the id, not derived from it later: the accrual document stores the name too, so
+     * an id sent without its name leaves the row displaying the account the user just moved away
+     * from.
+     */
+    jeCreditAccountName?: string;
     jeDebitAccountId?: ID;
     jeDebitAccountingClassId?: ID;
     jeDebitAccountingClassName?: string;
+    jeDebitAccountName?: string;
     memo?: string;
     /**
      * The Auto Reversal toggle, modelled as the same boolean the New form and the create payload use

package/lib/esm/view/expenseAutomationView/epics/jeSchedule/oneTimeAccrualActionsEpic.js

@@ -73,17 +73,39 @@ export const promoteOneTimeAccrualEpic = (actions$, state$, zeniAPI) => actions$
     const debitClassId = edits?.jeDebitAccountingClassId ?? accrual?.jeDebitAccountingClassId;
     const debitClassName = edits?.jeDebitAccountingClassName ??
         accrual?.jeDebitAccountingClassName;
+    // The accrual document stores names alongside ids, so every id below travels with its name.
+    // Sending an id on its own leaves the stored row -- and the JE posted from it -- naming the
+    // account the user just moved away from. Create has always sent the full set; promote did
+    // not, which is the difference the two paths were showing.
+    const debitAccountName = edits?.jeDebitAccountName ?? accrual?.jeDebitAccountName;
+    const creditAccountName = edits?.jeCreditAccountName ?? accrual?.jeCreditAccountName;
+    // Credit-side class is never edited on this form -- the liability side is the Balance Sheet
+    // class the draft was born with -- so it is echoed straight back from the draft.
+    const creditClassId = accrual?.jeCreditAccountingClassId;
+    const creditClassName = accrual?.jeCreditAccountingClassName;
     const payload = {
         amount,
         memo: edits?.memo ?? accrual?.memo ?? '',
         je_debit_account_id: debitAccountId,
         je_credit_account_id: creditAccountId,
+        ...(debitAccountName != null
+            ? { je_debit_account_name: debitAccountName }
+            : {}),
+        ...(creditAccountName != null
+            ? { je_credit_account_name: creditAccountName }
+            : {}),
         ...(debitClassId != null
             ? { je_debit_accounting_class_id: debitClassId }
             : {}),
         ...(debitClassName != null
             ? { je_debit_accounting_class_name: debitClassName }
             : {}),
+        ...(creditClassId != null
+            ? { je_credit_accounting_class_id: creditClassId }
+            : {}),
+        ...(creditClassName != null
+            ? { je_credit_accounting_class_name: creditClassName }
+            : {}),
         // Mirrors the create payload: reverse_next_month alone decides the policy, and the date is
         // only meaningful when it is true -- agent-je derives the reversal from the bill otherwise.
         reverse_next_month: reverseNextMonth,

package/lib/view/expenseAutomationView/epics/jeSchedule/oneTimeAccrualActionsEpic.js

@@ -76,17 +76,39 @@ const promoteOneTimeAccrualEpic = (actions$, state$, zeniAPI) => actions$.pipe((
     const debitClassId = edits?.jeDebitAccountingClassId ?? accrual?.jeDebitAccountingClassId;
     const debitClassName = edits?.jeDebitAccountingClassName ??
         accrual?.jeDebitAccountingClassName;
+    // The accrual document stores names alongside ids, so every id below travels with its name.
+    // Sending an id on its own leaves the stored row -- and the JE posted from it -- naming the
+    // account the user just moved away from. Create has always sent the full set; promote did
+    // not, which is the difference the two paths were showing.
+    const debitAccountName = edits?.jeDebitAccountName ?? accrual?.jeDebitAccountName;
+    const creditAccountName = edits?.jeCreditAccountName ?? accrual?.jeCreditAccountName;
+    // Credit-side class is never edited on this form -- the liability side is the Balance Sheet
+    // class the draft was born with -- so it is echoed straight back from the draft.
+    const creditClassId = accrual?.jeCreditAccountingClassId;
+    const creditClassName = accrual?.jeCreditAccountingClassName;
     const payload = {
         amount,
         memo: edits?.memo ?? accrual?.memo ?? '',
         je_debit_account_id: debitAccountId,
         je_credit_account_id: creditAccountId,
+        ...(debitAccountName != null
+            ? { je_debit_account_name: debitAccountName }
+            : {}),
+        ...(creditAccountName != null
+            ? { je_credit_account_name: creditAccountName }
+            : {}),
         ...(debitClassId != null
             ? { je_debit_accounting_class_id: debitClassId }
             : {}),
         ...(debitClassName != null
             ? { je_debit_accounting_class_name: debitClassName }
             : {}),
+        ...(creditClassId != null
+            ? { je_credit_accounting_class_id: creditClassId }
+            : {}),
+        ...(creditClassName != null
+            ? { je_credit_accounting_class_name: creditClassName }
+            : {}),
         // Mirrors the create payload: reverse_next_month alone decides the policy, and the date is
         // only meaningful when it is true -- agent-je derives the reversal from the bill otherwise.
         reverse_next_month: reverseNextMonth,

package/lib/view/expenseAutomationView/payload/jeSchedulesPayload.d.ts

@@ -119,8 +119,10 @@ export interface PromoteOneTimeAccrualPayload {
     je_debit_account_id: ID;
     memo: string;
     expected_reversal_date?: string;
+    je_credit_account_name?: string;
     je_credit_accounting_class_id?: ID;
     je_credit_accounting_class_name?: string;
+    je_debit_account_name?: string;
     je_debit_accounting_class_id?: ID;
     je_debit_accounting_class_name?: string;
     reverse_next_month?: boolean;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@zeniai/client-epic-state",
-  "version": "5.2.28",
+  "version": "5.2.30",
   "description": "Shared module between Web & Mobile containing required abstractions for state management, async network communication. ",
   "main": "lib/index.js",
   "module": "lib/esm/index.js",