D
Doug_F
New to IP and still waiting for it to be installed. I have done a lot of
data and workflow driven app design in other platforms and I'm looking for
'gotchas' and ways to minimize design problems.
Assume we're using SQL Server + SharePoint 2007 + InfoPath 2007 and the user
interface is all web based.
I create a form that's intended to collect daily readings from some process.
I'm going to collect the date, a weight, and a user name.
I think I have two basic design options - each form collects data for one
day's readings OR the form is designed to allow users to append a new section
each day that collects the data for 'today'; not sure if I'm using 'section'
correctly here, but it's the design construct that lets the user keep adding
new copies of an existing set of fields on demand.
Let's assume that, to keep people happy and working with a layout they're
familiar with, I use the 2nd design option - they're used to writing down
data on a form that already contains data. Assume also, that the data is
going into SQL server.
Time passes....
Requirements change...
Now I need to collect date, weight, user name, and the NIST standard used to
test the balance.
I need the user to stop using the Rev A form and start using Rev B.
I believe that the user isn't calling up a 'fresh' form each time they enter
data so they have access to their copy of the Rev A form. This is bad...
What happens? If the user opens up his/her working copy of the form, does
it automagically turn into the Rev B format? If not, can I design the system
so the Rev A copy prevents data input and tells the user what to do (or takes
them to the right form format)?
Normally, I'd just build a model and try it out but the infrastucture isn't
in place so I'm looking for some general guidance on if this is something one
needs to design for or if InfoPath is smart enough to make rev changes easy
to manage.
TIS for any feedback or pointers.
Doug
data and workflow driven app design in other platforms and I'm looking for
'gotchas' and ways to minimize design problems.
Assume we're using SQL Server + SharePoint 2007 + InfoPath 2007 and the user
interface is all web based.
I create a form that's intended to collect daily readings from some process.
I'm going to collect the date, a weight, and a user name.
I think I have two basic design options - each form collects data for one
day's readings OR the form is designed to allow users to append a new section
each day that collects the data for 'today'; not sure if I'm using 'section'
correctly here, but it's the design construct that lets the user keep adding
new copies of an existing set of fields on demand.
Let's assume that, to keep people happy and working with a layout they're
familiar with, I use the 2nd design option - they're used to writing down
data on a form that already contains data. Assume also, that the data is
going into SQL server.
Time passes....
Requirements change...
Now I need to collect date, weight, user name, and the NIST standard used to
test the balance.
I need the user to stop using the Rev A form and start using Rev B.
I believe that the user isn't calling up a 'fresh' form each time they enter
data so they have access to their copy of the Rev A form. This is bad...
What happens? If the user opens up his/her working copy of the form, does
it automagically turn into the Rev B format? If not, can I design the system
so the Rev A copy prevents data input and tells the user what to do (or takes
them to the right form format)?
Normally, I'd just build a model and try it out but the infrastucture isn't
in place so I'm looking for some general guidance on if this is something one
needs to design for or if InfoPath is smart enough to make rev changes easy
to manage.
TIS for any feedback or pointers.
Doug