Web wizard

Code is active and executes ok. I am attaching some screenshots for you to see. Also the interface has a simple IsDeleted property. I am including its definition in the zip also. Hope tpo hear from you soon.

Reagards
Greg

Hello Sasha,

Unfortunately i have already implemented the suggestion as i followed your guide step by step. The only difference is that all xafari related code is not in module or module.web but a new one i created for the test. I don't think this is a cause for error since this is exactly the reason behind module design in XAF, to isolate related code.

Either this is a bug with the wizard or my use case has something not taken into account in the implementation and/or documentation of the wizard.
I really cannot understand it as every debug/test has related controllers and actions fired correctly as can be seen by the screenshots i send you before.

Regards
Greg

Good morning Sasha,

Any updates on the issue?

Regards,
Greg

Hello Sasha,

Your example works. Strange thing is that i cannot see any difference between your code and mine apart from the fact that you use XPO and i use EF. Is there any restriction to the use of Wizards? Maybe wizard templates are not loaded if not using XPO?

I also tried to create a very simple solution based on yours but using EF (without classes) and a domain component class TestClass1 as my base object (with a NotPersistentObjectSpaceProvider). I copied the controller logic and created the wizard in the model but when code tries to find it there is an exception that Model.Xafari.Wizard node is null. Can you please check my solution?

Hello Sasha,

Sorry for the late reply but i have been engaged in something else and could not get back to you sooner.

Unfortunately your video did not help. I copied the detail views but the error (empty Xafari() node in model at runtime) still persists.
No point using it until these errors or peculiarities are worked out.

Please inform me if there is any further development or solution in the future. In any case please include if possible a test use case solution for a web project using EF and a wizard displaying several detail views of a non persisted entity.

Regards,
Greg

Hello Sasha
Is this fixed in your new release?

Hello again,

Due to vacation and extra time needed to migrate to devexpress 15.2 i have delayed testing the new version of xafari framework. I installed it today and upgraded the references but i still receive NullReferenceException when trying to access Application.Model.Xafari().Wizards. So i cannot proceed to test the displayed popup. The Wizards node is seen fine in the model editor but in code it raises the exception.

Please advice what to do.

OK ignore the above comment. It seems i have commented the XafariShowViewStrategy part in the WebApplication code.After i restored it i no longer have this error.

But we are back to the original problem (check first post in ticket). The displayed popup view only has the cancel button. It is exactly the same behavior as the previous version.

What gives?

Update on the issue. I have tested with the included solution and it works. But when i use it in my full solution i have the same problem. Apart from missing the 2 buttons (back, next) i also miss the layout in the header. In one case i get the blue bold header with the name of the current step (Solution2) and in the full project i get the default view name in XAF without any background or bold font. So my guess is that something prevents the wizard from loading its template or view strategy?!

In an effort to simplify changes i moved TestClass1 code from solution2 to current project but i get the same results. All related wizard code between solutions is the same down to the line. Same domaincomponent class, same detail views, same wizard settings in model, same code in wizard controller. Only different thing in my full solution is that i have an active db connection with EFObjectSpace and of course many detail window & viewcontrollers doing things for list, details and objectspaces. But i think that the part that shows the popup window in wizard (SetupWizardShowViewParameters()) should be self contained and not dependent upon other active controllers. ill send a zip file soon with the relevant files in solution2 and full project if you can compare and find anything. i would like to send the whole project but a db connection is also needed. i will also send the two logs up to the point i open the wizard and screenshots to show the differences. Hope we will find something.

Posting the files mentioned in my previous reply.

Hello Sasha,

Ok i enabled the diagnostic actions and run the action info. I can clearly see that (among a great number of controllers and actions) at the end there are both Wizard_Next and Wizard_Back action both active and one enabled as per your screenshot. But no buttons. I am attaching the log plus a screenshot for you to view.

Greg

Hello again Sasha,

Indeed after removing our custom dialog templates the wizard loaded correctly. For now we wont use any custom templates but it would be nice if we could still have that ability without breaking the wizard in the future.

As for the immediate concern. In my continued testing i encounter a new issue. Wizard is loaded fine and CustomNextStep and CustomizaeNextView events are fire correctly but then (all this when pressing next button but on cancel also) i get a javascript exception in http://localhost:7470/WebResource.axd?...
with message '0x800a1391 - JavaScript runtime error: 'ClientParams' is undefined'. Stack trace indicates that this is a devexpress exception rather than xafari but it still prevents wizard from doing its job. I am starting to suspect that 15.2 has some javascript issues as i encountered another similar case (but not the same) using the new html5 report viewer and devexpress label it as but pending fix. Have you encountered anything similar? Any suggestions to fix/avoid it so i can integtrate wizard into our app?

Below is the code that throws it

function ProcessMarkup(callbackResult, processScripts) {
if (callbackResult.cpClientInfo) {
ClientParams.Clear();
var clientInfo = JSON.parse(callbackResult.cpClientInfo);
for (var key in clientInfo) {
ClientParams.Set(key, clientInfo[key]);
}
}

and here is part of the xaf log

26.01.16 12:12:25.938 phziklxaqks0wzsib5bu44qa Type: DevExpress.ExpressApp.Actions.SimpleAction
ID: WizardNext
Category: WizardActions
Controller.Name: Xafari.Web.WebWizardDialogController
Context.Name: Undo Deleted Record Parameters Step1
Context.IsRoot: True
Context.SelectedObjects.Count: 1
Context.CurrentObject: DCFramework.FilterFeature.Module.BusinessObjects.UndoDeletedParameters

26.01.16 12:12:25.984 phziklxaqks0wzsib5bu44qa Action 'WizardNext' done
Unhandled exception at line 847, column 3 in http://localhost:7470/WebResource.axd?d=vTHACo8ymh56b07R2nmYThNHOBiiU3JOHbRHgN1ZbT1yUKJhSo-VqBAKssXkKuSxs4CjAkxdjLwAO5WcifrrY_mPpINzqVx_0fCLoekZKM2FlX-35XHBDzzAUI5bPZwudq-N7R6k1xhV8ah8mYKCmFoggxvhHUQxnMhl9FdJaIkh7_bZOYlDp5Q1cFx6UbEe8Fk5BUDg0M0we6eet2MO0UkO7gAviyMv6MNvKy7Y_h81&t=635893982350156892
0x800a1391 - JavaScript runtime error: 'ClientParams' is undefined