Pro InfoPath 2007
Electronic forms are the bane of developers everywhere. Laying out a form is generally designing a business process, so while it may seem like a fairly straightforward thing to do (I need this data, so I’ll put these controls on the form), you start running into issues of validation, presentation...
Đã lưu trong:
Tác giả chính: | |
---|---|
Định dạng: | Sách |
Ngôn ngữ: | English |
Được phát hành: |
Apress
2012
|
Những chủ đề: | |
Truy cập trực tuyến: | https://scholar.dlu.edu.vn/thuvienso/handle/DLU123456789/31812 |
Các nhãn: |
Thêm thẻ
Không có thẻ, Là người đầu tiên thẻ bản ghi này!
|
Thư viện lưu trữ: | Thư viện Trường Đại học Đà Lạt |
---|
Tóm tắt: | Electronic forms are the bane of developers everywhere. Laying out a form is generally
designing a business process, so while it may seem like a fairly straightforward thing to do
(I need this data, so I’ll put these controls on the form), you start running into issues of validation,
presentation, showing and hiding optional fields, and so on. InfoPath is a great tool exactly
because the designer is so straightforward that the developer can have the business stakeholders
design their own forms (or design the forms in conjunction with them in a joint-analysis design
session).
InfoPath 2007 has evolved far beyond that initial vision. With the addition of browsercompatible
forms, developers can design a form once and reuse it as a rich desktop form or
a browser-based form, and even embed the form in their own solutions. And since InfoPath is
completely XML-based, they’re not locking into some proprietary stack—an InfoPath form
could be the front end for a Java process, for example |
---|