How Next and Back Buttons Work on Wizard Form Pattern?

(4) Share

Report

Posted on by Momochi

1,044

Hi dear community !

I'm trying to learn to implement the wizard form pattern similar to what is implement in the standard form named: "WMSLocationWizard".

The form looks nice and it has great use cases through user guidance idea, but somehow I'm unable to find any detailed documentation regarding how to implement this form pattern (Wizard).

After reviewing the form example in "WMSLocationWizard" form, I'm still unable to locate the controls for the next and back buttons on the form design.

Also, I'm unable to locate the stage control (little circles that indicates which stage you are at right now in the wizard process).

Following the pattern design requirements on Visual Studio, I found out that this form consists of tab pages. And each page represents a different tab page.

But I'm unable to locate where the logic for the "Next" and "Back" buttons is implemented. The same for the stages circles control.

Screenshot:

Where the "Next" and "Back" buttons logic is implemented?

I want to know how to switch tab pages.

If there are any guides on how to implement the wizard form pattern, it would be helpful !

Any advice is appreciated !

Thanks in advance !

Categories:

Dynamics 365 Finance

I have the same question (0)

All responses (2)

Answers (1)

Sort by

Verified answer

Martin Dráb 239,647 Most Valuable Professional on at

Like (1)

Report
Copy link

Link copied!

It's not just about the form, but there also is a class involved that inherits from SysWizard, where you'll find what you're looking for.

For example, in prompt(), you can see the buttons added at runtime, the extended style buildTabPage set to wizard_stepsPage and so on. The class also has methods like next() and enableButtons(); you can open them to see how they're implemented.

Your example uses WmsLocationWizard class for this purpose. It extends SysDefaultDataWizard class (which extends SysWizard) and adds some extra logic for the given scenario.

It may be easier for you if you look at classes extending SysWizard directly (you can easily find them through references), such as SmaAgreementWizard class.

Notice that menu items opening wizards point to the classes, not the form. It's the class who creates the form; it has the name provided by its formName() method.

1 people found this reply helpful.

Was this reply helpful? Yes No
Momochi 1,044 on at

Like (1)

Report
Copy link

Link copied!

Hi there @Martin Dráb,

Thanks a lot ! following your suggestion to check out "SmaAgreementWizard" actually simplified it to me. It was more easier to follow through the implementation.

Appreciated !

Was this reply helpful? Yes No