Progress Capture Broken?

[QEHNick]

I'm updating a PC again and I'm seeing some odd behaviour which is breaking the PC.

I have a node which asks a question and then branches off to other custom forms. However, on the initial node, two responses do not produce the desired result. 

One reports that "The Intelligent Capture flow has reached a point that does not have any forward path. " which is not the case. (I've just made a slight change and now this one is doing the same as below).

Another choice results in the second node content appearing in the same window; so you end up with the first custom form contents above the second custom form contents.

The third (and final) choice actually works.

Very bizarre.

This on top of a previous problem to do with a branching issue in a PC lead me to think there's a larger issue here. 

Is anyone else experiencing problems with Progress Captures?

[QEHNick]

I've deleted the initial node and recreated it. It seems to have righted the problem.

[QEHNick]

I'll add an observation - it seems if you copy and paste a node, change elements in it, the Progress Capture does not present the changes to the user. This is where this problem seems to stem from. It's as if it continues to use the original nodes settings.

 

Indeed this is exactly what it is doing - I just changed the text in the node I copied from and, in the progress capture, it shows that nodes content instead of the one it should be displaying.

[Victor]

1 hour ago, QEHNick said:

if you copy and paste a node, change elements in it, the Progress Capture does not present the changes to the user. This is where this problem seems to stem from. It's as if it continues to use the original nodes settings.

@QEHNick where is this, is it when you design the PC or when a user actually uses it to raise a request?

[QEHNick]

@Victor When the customer raises the request.

[Victor]

@QEHNick have you refreshed (F5) the app page (where you raise a request) after changes to PC? The PC data is cached in browser (for performance reasons) so any changes to PC definition will require a page refresh for the browser to then cache the new PC (with the changes)...

[QEHNick]

@Victor Yes mate, I'm well versed in this now.

[QEHNick]

@Victor I have verified there is a fault; in my previous thread I had some weird behaviour associated with a node which, I now understand, was a copied and modified node.

By removing and recreating that node, the fault has cleared.

The issue I am having here is the same, I have copied and modified a node (it has a lot of elements in it) and the PC is not recognising, or even referring to it, as a different node.

[Victor]

@QEHNick ok, I understand. May I suggest a support request so we can gather all info we need to discuss this with dev team?

[QEHNick]

@Victor Indeed.

 

Done.