Extension of input form into another input form in Neolane | Community
Skip to main content
N
nidhiv77838491
Level 2
August 29, 2017

Extension of input form into another input form in Neolane

  • August 29, 2017
  • 1 reply
  • 9024 views

Hi Team,

Can suggest if we can extend input form into another input form in Neolane in order to make customise the factory input form of delivery.

Kindly help and put forward your suggestion.

Thank Much In Advance!

Nidhi

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

1 reply

Jean-Serge_Biro
Jean-Serge_Biro
Level 10
August 29, 2017

Hello Nidhiv,

No, a Factory XML form can't be extended, such as Schema extension way.

You must modify the factory form to customize it, or depending on your need, create a new form (with your own namespace) to provide a dedicated form on your own objects.

I recommend you to backup the factory form xml code, in order to revert if you did a mistake somewhere; for instance you can export it as a xml package on your computer local disk.

Regarding the changes that you need versus the default factory code, you can visibleIf, enableIf to hide or display sections/containers/fields. It is useful to customize the form depending on context.

Regards
Jean-Serge

Jean-Serge_Biro
Jean-Serge_Biro
Level 10
August 29, 2017

Hi Nidhiv,

During a product upgrade (version, build) the postupgrade task executed for all your instances displays the discrepency between factory forms and customized forms. So in the Conflict management node, you can manage to keep the current customized version or adapt it manually to take into account the default factory updates brought by the new version/build.

Regards
J-Serge

N
nidhiv77838491Author
Level 2
September 7, 2017

Hi Nidhi,

Using carefully the Conflict Management node after your postugrade, you should never loose your customisations.
Schemas extensions of factory schemas are done for this, by nature.
Factory forms changes are done in unique files, so can be owerwriten if you accept the new version in the Conflict management. Otherwise you may manage your customisation either by keeping the current version or by merging the new an current version by your own.

One more thing, it is a good practice to comment in XML <!-- --> the changes done, so it is common to comment also default form containers. Other way to do it

Regards.
JS


Hi Jean-Serge Biron​,

Can we give reference of customize form of delivery into nms:delivery form in order to avoid the same.

i.e. <form name="delivery" ref="adi:delivery:delivery" type="notebook"/>. Kindly Guide.

Terms & ConditionsAccessibility statement

Loading footer...