From 621c1423f87d68674949494ad7dd320f40dd15c3 Mon Sep 17 00:00:00 2001
From: CarlNation <32103961+CarlNation@users.noreply.github.com>
Date: Thu, 9 Nov 2023 14:46:19 -0500
Subject: [PATCH] CSR-1392

No need for this logic.  token is persisted in customerportallogintoken table and is pulled from there now in the api on final submit
---
 src/store/index.js | 9 +--------
 1 file changed, 1 insertion(+), 8 deletions(-)

diff --git a/src/store/index.js b/src/store/index.js
index de2e6b45b..94a50f46d 100644
--- a/src/store/index.js
+++ b/src/store/index.js
@@ -1039,14 +1039,7 @@ export const actions = {
         context.commit(storeMutations.UPDATE_CRM_CUSTOMER_ID, crmCustomerId);
         context.commit(storeMutations.WORK_ORDER_NUMBER, workOrderNumber);
         context.commit(storeMutations.LOCK_TOKEN, lockToken);
-
-        // if we already have the token, do not update it.  pia does 2 work order submits and the value is not persisted after the first submit
-        if (
-            state.order.customerPortalLoginToken != null &&
-            state.order.customerPortalLoginToken != "00000000-0000-0000-0000-000000000000"
-        ) {
-            context.commit(storeMutations.Customer_Portal_Login_Token, customerPortalLoginToken);
-        }
+        context.commit(storeMutations.Customer_Portal_Login_Token, customerPortalLoginToken);
     },
 
     logPageView(