nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

DCR Preview Issue...

mishrav

Hi ,
In our current project, we have a requirement like we need to show/hide IWitems such as ‘Text’ and ‘Browser’ on Radio button selection.
We developed the validation script, and calling the same onFormInit event.
This functionality is working fine and the XML is generating in required format. But when we clicking the DCR file link like (attached docs) it’s not calling the init function onFormInit event, loading the default form.

Could you please let us know, which event needs to be handled here, when we click on the DCR form file itself like below.
PFA the DCT, DCR and Script files for your reference.

Thanks in advance.

Find more posts tagged with

Comments

ISCBorisB

But when we clicking the DCR file link [...] it’s not calling the init function onFormInit event...

There is absolutely nothing you can do within FormAPI approach. When you click a DCR link FormsPublisher opens it up in
the "View Only" Mode. In this Mode FormsPublisher does not load user Scripts and disables FormAPI

Adam Stoller

Hi ,
In our current project, we have a requirement like we need to show/hide IWitems such as ‘Text’ and ‘Browser’ on Radio button selection.
We developed the validation script, and calling the same onFormInit event.
This functionality is working fine and the XML is generating in required format. But when we clicking the DCR file link like (attached docs) it’s not calling the init function onFormInit event, loading the default form.

Could you please let us know, which event needs to be handled here, when we click on the DCR form file itself like below.
PFA the DCT, DCR and Script files for your reference.

Thanks in advance.

This comes up over and over again periodically (redundant?) - When you View (as opposed to Edit) a DCR - no FormAPI code will be executed - the DCR is in read-only mode and thus any FormAPI code that might alter the contents of the DCR would be wrong to run. Ergo - there's nothing you can do other than user training.

mishrav

Thanks for your valuable response...

Adam Stoller

Thanks for your valuable response...

I'll amend my own response - you can hard-code items in the DCT to be hidden and/or readonly and use FormAPI to un-hide and/or make them writable - this would default to letting you View the DCR mostly the way you think it should look - but again, without FormAPI code being run - the hidden fields would remain hidden regardless of the values that might be in any other field (e.g.: if you expose 5 fields when you click on checkbox-A, those 5 fields would remain hidden when you View the DCR regardless of the value of checkbox-A)

So, you do kind of have a choice as to which way you lean with this - either showing more (or all) fields in View mode, or potentially showing less fields in View mode - either way, user-training is always a good idea.

Faizi

I think DCT should be designed in way that minimal blank items be there. Try to use same item with different condition and handle the complexity with FormAPI. In that way minimal items come with blank value on viewing a DCR.

In DCT, don't hard-code items as hidden/read-only so that it will show on viewing a DCR.

In those way you can handle the issue.