D
DimonD
This is more a solution design question. What is the best way to implement
the following solution using InfoPath:
Our solutions` framework should have the following basic features:
- data entry
- reporting
- authentification (using AD?)
- roles (with different actions and views)
- digital signature (not windows built-in!)
- logging
- different transport (HTTP, MQ, SMTP)
- data exchange between forms-applications
As I can see there can be two basic ideas:
- make a .NET framework app that will use InfoPath inside, or just call it
as an external app
- make a framework app using InfoPath itself. Their will be one basiÑ app
form that will perform all tasks need, calling other forms when needed.
What way is preferable? Are there any other ideas?
the following solution using InfoPath:
Our solutions` framework should have the following basic features:
- data entry
- reporting
- authentification (using AD?)
- roles (with different actions and views)
- digital signature (not windows built-in!)
- logging
- different transport (HTTP, MQ, SMTP)
- data exchange between forms-applications
As I can see there can be two basic ideas:
- make a .NET framework app that will use InfoPath inside, or just call it
as an external app
- make a framework app using InfoPath itself. Their will be one basiÑ app
form that will perform all tasks need, calling other forms when needed.
What way is preferable? Are there any other ideas?