办公室内纸质表格和流程的自动化
我的任务是自动化人力资源部门的一些纸质表格。 这最终可能会变成“自动化所有表单”，所以我想以一种最适合长期的方式来解决这个问题，并且随着这个项目的发展将成为一个很好的框架。
首先想到的是：
-InfoPath/SharePoint（我们目前不使用 SharePoint，并且在接下来的两年内不会成为一个选项。）
-Workflow Foundation（我已经对此进行了研究，但没有看起来太有吸引力或合适）
我现在正在考虑的选项：
-Custom ASP.NET (VB.NET) & SQL Server，我的团队主要使用它来编写应用程序。 -利用 Infopath 以电子方式创建表单。 想知道是否有一个好的方法可以将其与自定义构建的 ASP.NET 应用程序集成。 - 考虑将应用程序创建为 MVC Web 应用程序。
我的问题是：
-我还想考虑其他选择吗？ - 是否有任何入门套件或基于 VB.NET 的开源项目可以作为起点或可以用作很好的参考。 这里我主要关心的是工作流程处理。 -走过这条路的人有什么评论吗？
I have been tasked with automating some of the paper forms in HR. This might turn into "automate all forms" eventually, so I want to approach this in a way which will be best for the long term and will be a good framework as this project grows.
The first things that come to mind were:
-InfoPath/SharePoint (We currently don't use SharePoint now, and wouldn't be an option for the next two years.)
-Workflow Foundation (I've looked into this and does not seem too attractive or appropriate)
Option I'm considering at this point:
-Custom ASP.NET (VB.NET) & SQL Server, which is what my team mostly writes their apps with.
-Leverage Infopath for creating the forms electronically. Wondering if there is a good approach to integrating this with a custom built ASP.NET app.
-Considering creating the app as an MVC web app.
My question is this:
-Are there other options I might want to consider?
-Are there any starter kits or VB.NET based open source projects there which would be a starting point or could be used as a good reference. Here I'm mostly concerned with the workflow processing.
-Any comnments from those who have gone down this path?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（4）
这听起来真的很愚蠢，但在我多年来帮助公司实现基于纸质表单的流程自动化的过程中，首先要理解这个流程。 你很可能会发现没有一个人能理解整件事。 您需要对整个过程中的许多路径进行角色扮演，以掌握整个过程。 一旦你展示你的发现，每个人都会感到震惊，因为他们不知道它是如此复杂。 以此为契机进行精简。
将一个损坏的流程自动化只会让它更快地搞砸并告诉很多人。
就工具而言，我的经验过时了，但尝试使用具有以下属性的工具：
不确定这是否有帮助 - 但自动化流程的成功 80% 不是技术。
This is going to sound really dumb, but in my many years of helping companies automate paper form-based processes is to understand the process first. You will most likely find that no single person understands the whole thing. You will need to role-play the many paths thru the process to get your head around it. And once you present your findings, everyone will be shocked because they had no idea it was that complex. Use that as an opportunity to streamline.
Automating a broken process only makes it screw up faster and tell a lot of people.
As far as tools, my experience dates me but try to go with something with these properties:
Not sure if this helps or not - but 80% of success in automating processes is not technology.
这有点偏离主题，但相关 - 缺陷跟踪系统通常具有工作流引擎/状态。 （事实上，我认为 Joel 或其他一些 FC 员工发布了一些有关使用 FB 来管理初始电子邮件和简历流程的内容）
我赞同有关在进行任何编码或技术选择之前对工作流程进行建模的其他建议。 您还希望它是灵活的。
This is slightly off topic, but related - defect tracking systems generally have workflow engines/state. (In fact, I think Joel or some other FC employee posted something about using FB for managing the initial emails and resume process)
I second the other advice about modeling the workflow before doing any coding or technology choices. You will also want this to be flexible.
正如 n8owl 提醒我们的那样，自动化混乱会产生自动化混乱 - 这并不是一种改进。 许多纸质表单系统已经发展了数十年，并且可能相当冗余且不守规矩。 有些人可能认为“弄乱表格”侵犯了他们的个人领地，所以要小心；-)
祝您好运！
--S
as n8owl reminded us, automating a mess yields an automated mess - which is not an improvement. Many paper-forms systems have evolved over decades and can be quite redundant and unruly. Some may view "messing with the forms" as a violation of their personal fiefdoms, so watch your back ;-)
good luck!
--S
我在这里发现对于基于工作流程的方法普遍持谨慎态度，并且必须同意。 请了解大多数工作流程的注意事项为了灵活性而牺牲可用性的技术。
I detect here a general tone of caution with regards to a workflow based approach and must agree. Be advised about the caveats of most workflow technologies which sacrifice usability for flexibility.