search

ben-garside / XCP

XML Content Pipelining
0 stars 0 forks source link

User testing: stage 20.05 to 20.10 (and others) #99

Closed VermaBSI closed 8 years ago

VermaBSI commented 8 years ago

Hi Ben,

I've now set up all the stages rules in XCP for the end-to-end process, and am beginning to use it in real-life to move the latest UPIs through the system.

My first glitch is this:

Moving from stage 20.05 to 20.10 in the Conversion tab does not update instantly - it goes back down into the UNCLAIMED list and stays at 20.05. It's only after a refresh that the correct result appears - the item back in the CLAIMED list (correct, since it's a sticky rule) and at 20.10.

Also the refresh I mention sometimes has to be a hard refresh from the browser because of issue #100 just raised - which makes this whole process a bit arduous.

This doesn't happen say moving an item from 20.00 to 20.05 (another sticky rule).

Thanks Varun

VermaBSI commented 8 years ago

Just to add, this pattern occurs updating the stage between other stages too, not just between 20.05 and 20.10.

This morning I moved for example UPI 30256178 (XCP5970509) through a whole re-work conversion scenario (see data history for this item to see all stages progressed through).

I.e. so seems like the cause is something in your code generally perhaps?

VermaBSI commented 8 years ago

Moving through stages is happening generally more smoothly now.