Information Systems:Infonet Feedback and Recommendations - Revision history

Norwinu: /* Business Partners */

2017-11-16T20:27:18Z

Business Partners

Norwinu: /* Business Partners */

2017-11-16T20:24:10Z

Business Partners

Norwinu: Undo revision 9946 by Norwinu (talk)

2017-11-16T20:22:42Z

Undo revision 9946 by Norwinu (talk)

Norwinu at 20:22, 16 November 2017

2017-11-16T20:22:21Z

Norwinu at 20:22, 16 November 2017

2017-11-16T20:22:11Z

Norwinu at 20:20, 16 November 2017

2017-11-16T20:20:32Z

Norwinu at 20:16, 16 November 2017

2017-11-16T20:16:26Z

Norwinu: Created page with "This page is intended for Infonet users to provide feedback and recommend changes to the site or to individual programs. Rather than enforce any structure, we'll just see if o..."

2017-11-16T20:16:09Z

Created page with "This page is intended for Infonet users to provide feedback and recommend changes to the site or to individual programs. Rather than enforce any structure, we'll just see if o..."

New page

This page is intended for Infonet users to provide feedback and recommend changes to the site or to individual programs. Rather than enforce any structure, we'll just see if one evolves (-[[User:Norwinu|norwizzle]] ([[User talk:Norwinu|talk]]) 12:16, 16 November 2017 (PST)).

===Business Partners===
* Paginated 'add partner' form: It's common sense for long forms to be filled in sections/pages so that the data can be processed faster e.g. at each step. Currently, it is one huge, scrollable form, validated and submitted only at the end. Besides user convenience, this would actually lead to greater server-side efficiency of this program as the HTTP request is currently massive (with all that form data).
* Dynamic form input: Input data should be processed dynamically for smarter forms. For example, populating the Province field with Alberta should populate subsequent fields like price list with corresponding defaults. This process should also be used to validate many of the fields in real-time (upon typing or leaving the input field).
* Use of temporary tables:
:* Prevents the problem as described in the previous section.
:* Able to run logic on ALL form data prior to writing ANY information to tables.
:* Able to have the user confirm all entered data prior to writing.
:* Able to cancel and cleanup partially filled information. Currently, records are not deleted if the user cancels the process, leaving stale, blank entries in tables.
:* Able to accommodate multiple users using the Add Partner form without having to 'grab first dibs' on a partner number by immediately writing a record.

@@ Line 7: / Line 7: @@
 :* Corrects the design flaw as described '''[[Information_Systems:IN-NAMECHG_-_Business_Partners | here]]'''.
 :* Able to run logic on ALL form data prior to writing ANY information to tables.
-:* Able to have the user confirm all entered data prior to writing.
+:* Able to have the user confirm all entered data prior to writing to tables.
 :* Able to cancel and cleanup partially filled information. Currently, records are not deleted if the user cancels the process, leaving stale, blank entries in tables.
-:* Able to accommodate multiple users using the Add Partner form without having to 'grab first dibs' on a partner number by immediately writing a record.
+:* Able to accommodate multiple users using the Add Partner form in a manner that doesn't involve having to 'claim' a partner number by immediately writing a record.
 [[Category: Infonet]]

← Older revision		Revision as of 20:16, 16 November 2017
Line 10:		Line 10:
	:* Able to cancel and cleanup partially filled information. Currently, records are not deleted if the user cancels the process, leaving stale, blank entries in tables.		:* Able to cancel and cleanup partially filled information. Currently, records are not deleted if the user cancels the process, leaving stale, blank entries in tables.
	:* Able to accommodate multiple users using the Add Partner form without having to 'grab first dibs' on a partner number by immediately writing a record.		:* Able to accommodate multiple users using the Add Partner form without having to 'grab first dibs' on a partner number by immediately writing a record.
		+
		+	[[Category: Infonet]]

@@ Line 5: / Line 5: @@
 * Dynamic form input: Input data should be processed dynamically for smarter forms. For example, populating the Province field with Alberta should populate subsequent fields like price list with corresponding defaults. This process should also be used to validate many of the fields in real-time (upon typing or leaving the input field).
 * Use of temporary tables:
-:* Corrects the design as described '''[[Information_Systems:IN-NAMECHG_-_Business_Partners | here]]'''.
+:* Corrects the design flaw as described '''[[Information_Systems:IN-NAMECHG_-_Business_Partners | here]]'''.
 :* Able to run logic on ALL form data prior to writing ANY information to tables.
 :* Able to have the user confirm all entered data prior to writing.

@@ Line 2: / Line 2: @@
 ===Business Partners===
-* Paginated 'add partner' form: It's common sense for long forms to be filled in sections/pages so that the data can be processed faster e.g. at each step. Currently, it is one huge, scrollable form, validated and submitted only at the end. Besides user convenience, this would actually lead to greater server-side efficiency of this program as the HTTP request is currently massive (with all that form data).
+* Paginated 'add partner' form: It's common sense for long forms to be filled in sections/pages so that the data can be processed faster e.g. at each step. Currently, it is one huge, scrollable form, validated and submitted only at the end. Besides user convenience, this would actually lead to greater server-side efficiency of this program as the HTTP request of each form-submit is currently massive (with all that form data).
 * Dynamic form input: Input data should be processed dynamically for smarter forms. For example, populating the Province field with Alberta should populate subsequent fields like price list with corresponding defaults. This process should also be used to validate many of the fields in real-time (upon typing or leaving the input field).
 * Use of temporary tables:
-:* Prevents the problem as described in the previous section.
+:* Corrects the design as described [[Information_Systems:IN-NAMECHG_-_Business_Partners | here]].
 :* Able to run logic on ALL form data prior to writing ANY information to tables.
 :* Able to have the user confirm all entered data prior to writing.