ke00163927 KE00163927 - Service ID variable has no value when used in custom form conditional fields

[Martyn Houghton]

Is there any update on the fix being deployed for the Known Issue KE00163927, in relation the the Service ID variable not being populated for conditional fields and decision nodes in the progressive capture?

Cheers

Martyn

 

[Nanette]

@Martyn Houghton

We can confirm that this should be fixed now.  The following will need to be done on the ones that aren't working, open affected decision node conditions and resave. 

Many thanks, Nanette

[Martyn Houghton]

@Nanette

Can you confirm which build this was fixed in?

I will refresh our Progressive Captures and test.

Cheers

Martyn

[Martyn Houghton]

@Nanette

Just to confirm this is still an issue even after opening and resaving the decision node conditions and the conditional fields.

I will log a new support request.

Cheers

Martyn

[Nanette]

@Martyn Houghton

Sorry to hear this, I can see a support request has been raised. We will follow this up and provide an update as soon as we have one.

Kind regards, Nanette.

[Victor]

@Martyn Houghton the fix suggested by above should be:

1. Open/Edit the affected decision expression

2. Make a change (any change) for example change the service ID from 90 to 91 (do not save)

3. Undo the change for example change the service ID from 91 back to 90

4. Save the PCF

The expression syntax will be corrected at Step 2 automatically without the need of saving the PCF at that point. This is why saving the PCF in Step 2 is not required, it only needs a change, any change, to trigger the correction. The correct syntax is stored in the session therefore when saving the PCF is Step 4 it will store the correct syntax for the PCF configuration.

[Martyn Houghton]

@Victor

As per our conversation I will give this a go. I will do a similar change in the conditional field criteria.

Cheers

Martyn