jason/DigitalConsumer.FixMyGlass
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

CSR-1392

Browse source 
No need for this logic.  token is persisted in customerportallogintoken table and is pulled from there now in the api on final submit
This commit is contained in:
CarlNation 2023-11-09 14:46:19 -05:00
parent be2a0f4004
commit 621c1423f8
1 changed files with 1 additions and 8 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

9
src/store/index.js
View file

@ -1039,14 +1039,7 @@ export const actions = {
context.commit(storeMutations.UPDATE_CRM_CUSTOMER_ID, crmCustomerId); context.commit(storeMutations.UPDATE_CRM_CUSTOMER_ID, crmCustomerId);
context.commit(storeMutations.WORK_ORDER_NUMBER, workOrderNumber); context.commit(storeMutations.WORK_ORDER_NUMBER, workOrderNumber);
context.commit(storeMutations.LOCK_TOKEN, lockToken); context.commit(storeMutations.LOCK_TOKEN, lockToken);
context.commit(storeMutations.Customer_Portal_Login_Token, customerPortalLoginToken);
// 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);
}
}, },
logPageView( logPageView(