This has so many strange things going on, I don't know where to start. We can make changes.. Save and make live, and would disappear from the module list. they would Cycle, ask the normal question, do you want this to disappear etc. I can make other changes, make them live, and the client comes back, and shows correctly, and the earlier deleted modules dont come back.
Then the strangest thing happens.... We make a change, and when it comes back, all of the earlier deletions are back, and most strangely, the condition editor just flat out disappears. The button is still on the tool bar, but pressing it has no response. The box does not appear on screen. Additionally, any test conditions in the call flow are still there, but the condition you are trying to edit , disappears from the module. It is blank and there is nothing to populate the box, no conditions are listed.
, we have made a lot of attempts to pin point the issue. Sometimes a new module will allow the condition editor to come up When it comes back, all of the conditions are back and they populate the call flows, in the modules where they were originally used.
We have done a lot of testing to try to determine what causes this issue. We have not had much success. We have been working with a Very Good Knowledgeable tec from a long time Avaya Business Psrtner, and he is frustrated too. This is really causing us a lot of issues. Any Thoughts ?
Then the strangest thing happens.... We make a change, and when it comes back, all of the earlier deletions are back, and most strangely, the condition editor just flat out disappears. The button is still on the tool bar, but pressing it has no response. The box does not appear on screen. Additionally, any test conditions in the call flow are still there, but the condition you are trying to edit , disappears from the module. It is blank and there is nothing to populate the box, no conditions are listed.
, we have made a lot of attempts to pin point the issue. Sometimes a new module will allow the condition editor to come up When it comes back, all of the conditions are back and they populate the call flows, in the modules where they were originally used.
We have done a lot of testing to try to determine what causes this issue. We have not had much success. We have been working with a Very Good Knowledgeable tec from a long time Avaya Business Psrtner, and he is frustrated too. This is really causing us a lot of issues. Any Thoughts ?
