Hello,
We recently added a new state to our choice list in [wm_task], configured state flows, the whole works for a "Resolved" state that is directly prior in sequence to Closed Complete/Closed Incomplete. For some reason, the tasks disappear from the Dispatcher Workspace in the FSM Configurable Workspace once this state is changed, and then reappears once the state is pushed to Closed Complete or Incomplete.
Does anyone have any ideas what may have caused this? Relative noobie here, but I imagine it's some sort of filter present in the application files' script includes. Specifically, I've been digging through all script includes that have names starting with "DispatcherWorkspace". Some keywords I've come across in this are "popovers" and "task cards."
Thank you.
#dispatcher workspace. # FSM , #Asset Management
