SlipStream Issue with QM02

[macds]

Hi All,

I have an issue with a flavour created on SlipStream for QM02. The basic issue is the transaction gets "stuck" on one screen depending on a certain sequence of events. If I run in the original screen, no issues, no errors or warnings.

The flavour has hidden some tabs, and merged data from the "subject" tab into the "Reference Object" tab.

Steps:

Run QM02, select a Quality Notification

This is the original screen for reference

The flavour merges information from the Subject tab into the reference object tab. Hides the subject, items, and activities tabs

Starting in the Reference Object Tab, I click the Processing tab, then the Tasks tab, finally back to the Reference Objects tab. No issues. All works.

When clicking from the Task tab back to the Reference Object tab, this is the profiler details

It submits the Tab01 request, and runs the collect process for the merge.

However, if I repeat the transaction and miss the Processing tab (enter on Reference Object tab, click Tasks tab, and finally back to Reference Objects tab) the transaction gets "stuck" on the Tasks tab.

This is the profiler response in this scenario

It submits the Tab01 request but a Restore activation State event happens. Basically, it goes to Tab01 (reference object) but immediately switches back to the Tasks tab.

I have no scripts attached to any screen events. There are no errors or warnings thrown by the back end. No errors in the browser developer tool logs.

Anyone have any ideas what is triggering this "Restore activation State"?

Cheers

James

[Tamas_Hoznek]

Any errors in the browser console after the flavor gets "stuck"?

[macds]

Hi Tamas,

No, there are no errors in the browser console.

Also, once "stuck" If I revert to the original screen in the browser, I can move between all the tabs without issue. No messages displayed, anywhere.

Cheers

James

[Tamas_Hoznek]

If there is no error in the browser console, then the problem may be related to tab merging. Try adding a script to the tab strip's onMergeError event to check if this is the case. Even a simple alert should be sufficient to confirm this.

[macds]

Hi Tamas,

[macds]

I've added a small alert script on the mergeerror events (Reference is one screen, tabs is another). neither is fired

[Tamas_Hoznek]

Well, then I guess the next step is to open a BC-PER support incident and provide access to the system, along with detailed description how to reproduce the problem.