View Issue Details

IDProjectCategoryView StatusLast Update
0000204HTMLApppublic2018-11-17 10:21
ReporterpvlasovAssigned To 
PrioritynormalSeverityminorReproducibilityhave not tried
Status newResolutionopen 
Product Version 
Target VersionFixed in Version 
Summary0000204: Input Actions
Description

Consider adding InputAction - an action which requires user input. Rendered as a form.
The challenge might be versatility of forms - validation, etc.
Maybe the solution is to have a standard form-handling approach with Knockout bindings, generated view model served as a module or inline - whatever is easier. Use eval() approach - if result is success then body shall contain "action" key with JavaScript expression value, e.g. navigation to another page.
So, have a "Knockout form" in the knockout bundle or something similar and implement InputAction on top of it.
Leverage the Knockout form in other places, e.g. for editing, EOperations, wizards.

One use of input actions - inline forms such as login and search.

In the case of InputAction basic settings such as color etc. are applied to the submit button.

TagsNo tags attached.
Estimated effort
Sprint

Activities

There are no notes attached to this issue.

Issue History

Date Modified Username Field Change
2018-11-17 10:15 pvlasov New Issue
2018-11-17 10:15 pvlasov Description Updated View Revisions
2018-11-17 10:19 pvlasov Description Updated View Revisions
2018-11-17 10:21 pvlasov Description Updated View Revisions