Human Task Captures

[Dan Munns]

Hi all,

Is there a reason why the PC within tasks behaves differently from the actual PCs? 

When a field is left blank it defaults to 'No answer given' rather than just staying blank. However in my BPM i need the behaviour to be the same as the PC as I need to do 'x' if blank (not set) and 'y' if set

[Victor]

@Dan Munns you can actually blame me for this... I have asked devs to put this in there a while back because I thought it looks ugly to have a "Reason: (blank)" 

[Dan Munns]

@Victor when did the behaviour change as it is now stopping my BPMs working. 

Can we have a setting for this as we do for PCs?

[Dan Munns]

Anyone? 

[Victor]

@Dan Munns apologies, I missed your reply... I have just re-read this and I can only take blame for the "Reason: No reason given" as the custom fields in tasks were added only recently...

So, to make sure I understand this right, if you have a custom field in PCF and that will not be filled in it will appear as blank (so you can use "is set" or "is not set") but with custom fields in tasks, if the field is not filled in it will have the value of "No answer given"?

[Dan Munns]

@Victor that is correct. I tried setting the decision node to be either ‘No answer given’ or no match but that doesn’t appear to work either. 

I also tried copying the answer to a custom field but it shows as blank if the system sets ‘No answer given’ 

it’s confusing me a little to be honest. 

[Victor]

14 minutes ago, Dan Munns said:

it’s confusing me a little to be honest.

@Dan Munns ah, ok then...  is working as designed  

 

I'll have a look and come back to you.

[Dan Munns]

Thanks @Victor 

I have attached the BPM so you can more easily pick out the simple setting I have messed up

 

marketing---new-marketing-request.bpm.txt

[Victor]

@Dan Munns - I have tested this in my instance and using "is not set" works fine for me ... 

[Dan Munns]

@Victor that is strange. Can you look at my BPM and see if that is still the case? 

Looking in the database it sets 'undefined' when the system sets 'No answer given' 

[Victor]

@Dan Munns  - I can't properly test your BP as I do not have all the configuration in place (dynamic lists) or the stuff in first two stages... May I ask you to try it again with this configuration?

 

[Dan Munns]

@Victor, this works now. But it didn't yesterday. I am (almost) certain I had it set this way and I kept getting a 'No goto if' error.

Oh well, sorted anyway. 

[Victor]

4 minutes ago, Dan Munns said:

I kept getting a 'No goto if' error.

@Dan Munns hmm...  not sure where you were getting this because the decision nodes have "No Match" branches.. unless you changed this since yesterday? Or perhaps the error occurred somewhere else?

[Dan Munns]

@Victor yesterday I had it set to one branch was 'if is set' and the other 'if not set'. Then I got the no goto if error. 

I changed it to no match this morning, but then I got a 'the specified user....' error.

[Victor]

5 minutes ago, Dan Munns said:

one branch was 'if is set' and the other 'if not set'. Then I got the no goto if error. 

@Dan Munns ... er... how??  

Can I have a look at the process? I assume is there as a previous published version...

[Dan Munns]

@Victor

It is what was confusing me. It may have been because I was looking at a custom field rather than the output directly from the task. 

The custom field was empty in the request, populated with 'undefined' in the database and failed any kind of decision node check I could think of. 

I will dig out the version (it has gone up by about 20 versions since last night) 

[Victor]

@Dan Munns the "is set" / "is not set" is basically checking if a field is NULL or not... and it can only be one of these... either NULL ... or not NULL... is not like there is a third option there like "partially NULL" or "almost NULL" and that's what intrigues me...