说说System Workflow和Human Workflow

解析Systemworkflow与Humanworkflow
最新推荐文章于 2025-07-10 13:13:16 发布
最新推荐文章于 2025-07-10 13:13:16 发布 · 136 阅读 · 0
文章标签：

#Workflow #工作 #Office #Microsoft #框架

了解了.Net Framework 3.0中的WF，大家一定都知道了System workflow和Human workflow这两个概念。从名字上就看的出来，Systemworkflow指的是把应用系统按一定的规则连接起来的工作流，没有人参与流程的流转，而Human workflow指的就是有人参与的工作流,例如审批报销单的流程。

从这两种场景中我们很容易分析出两者的区别:1 一个有人参与而另一个没有;2 Human workflow是有人参与的工作流，而人的行为是不可以预期的，有可能领导同意了报销单可以报销，也有可能领导由于报销金额过大不同意报销，所以流程流转的方向不是固定的是可变的，而System workflow中没有人参与，应用系统间数据交互的方式是固定的，所以流程流转方向也是固定的；3 数据格式也有区别，这还是由于人的原因，人可能会说一大段话或输入一段文本交给工作流引擎分析，而应用系统间交互的数据可没有这么乱，都是格式化的数据，如某个类的实例，很好分析。

说完了System workflow和Human workflow的概念和区别，我们在说说和这二者相关的事情。其实大家可能对System workflow这个名字感到挺陌生的，但说到EAI和B2B大家可能就耳熟能详了。其实System workflow就是指的EAI和B2B这两种场景。Microsoft有款著名的产品：Biztalk 就是用来实现EAI和B2B这两种场景的。对于Human workflow这种场景Microsoft还没有成熟的产品来实现这种需求，目前只是在Biztalk中加入了HWS服务来满足这样的需求，但由于HWS性能还不够好，使用起来也不容易，应用的案例较少。不过这对于其他厂商倒是个好机会，可以在微软还没有涉足的领域使自己得到长足的发展，如K2就是全球性工作流解决方案的提供商，K2有很多成熟的案例和客户。

回过头来再说微软给WF的定位，WF将成为微软平台上所有工作流应用（微软产品和第三方产品）的开发引擎。也就是说以后微软的所有产品，包括Biztalk，2007 Office等产品，其中只要用到工作流功能，其工作流引擎必然是WF，第三方的产品也是这样，微软已经提供了工作流引擎开发框架，只要愿意很容易在其上实现自己的工作流功能。 现在Biztalk最新版本2006已经是采用WF做为工作流引擎，但该版本中还没有提供对于Human workflow这种场景的强力支持，据说Biztalk 2008将提供对这种场景的支持，所以K2不能高枕无忧了。

呵呵，今天罗索了这么多System workflow和Human workflow的事情，快成为唐僧了，不说了，休息......

iteye_3619
关注
workflow system
11-07
Workflows are used to automate various data analysis tasks, which might produce further data;
Beginning WF: Windows Workflow in .NET 4.0
05-09
Windows Workflow Foundation is a ground-breaking addition to the core of the .NET Framework that allows you to orchestrate human and system interactions as a series of workflows that can be easily ...
System.Workflow.Activities
qao117的专栏
08-21 847
System.Workflow.Activities 命名空间<br />定义一些活动，可将这些活动添加到工作流，以便创建并运行工作过程的可执行表示形式。  类   类说明ActiveDirectoryRole在 Windows Workflow Foundation 宿主环境中表示 Active Directory 角色。无法继承此类。ActiveDirectoryRoleFactory一个工厂类，用于从 Windows NT 别名、电子邮件地址和安全标识符 (SID) 创建 ActiveDirector
工作流小问题
weixin_34354173的博客
03-30 153
The service 'System.Workflow.ComponentModel.Design.IIdentifierCreationService' must be installed for this operation to succeed 很久没上网到博客里面浏览，懒惰成了我这段时间的代名词。今天为了解决一个业务逻辑问题，考虑到用WF进行实现， 在VS20...
一个简单的workflow程序
pantech
04-24 211
今天看电子书《Presenting Windows Workflow Foundation》因为是beta版的，所以和.Net Framework3.0有一定的差别，看到介绍Data activity的时候实在是忍不住了，干脆吧换另一本书看《Foundations of WF An Introduction to Windows Workflow Foundation》不过觉得对那本beta版的书...
AI人工智能代理工作流AI Agent WorkFlow：面向未来的AI代理与工作流研究方向
AI天才研究院
08-05 1358
人工智能(Artificial Intelligence, AI)的起源可以追溯到20世纪50年代，图灵测试的提出标志着人工智能作为一门学科的诞生。早期的AI研究主要集中在符号推理、专家系统等领域，取得了一定的成果，但受限于计算能力和数据规模，发展较为缓慢。工作流(Workflow)是指一系列相互关联的任务，按照一定的规则和顺序进行执行，以完成特定目标的过程。顺序工作流、并行工作流、条件分支工作流、循环工作流等。办公自动化工作流、生产制造工作流、电子商务工作流、医疗保健工作流等。
Pro WF - Windows Workflow in .NET 4.pdf
04-22
Windows Workflow Foundation (WF) is a revolutionary part of the .NET 4 Framework that allows you to orchestrate human and system interactions as a series of workflows that can be easily mapped, ...
38、Integrating CSPM with IaC and DevSecOps Workflow Automation
go5gopher的博客
07-10 101
这篇博文探讨了将云安全态势管理（CSPM）与基础设施即代码（IaC）及DevSecOps工作流自动化集成的挑战与策略。文章涵盖了IaC的最佳实践，如DRY原则、关注点分离和测试验证等设计模式，并深入分析了DevSecOps的核心要素及其生命周期。同时，讨论了CSPM在DevSecOps中的作用、工作流自动化的实施步骤及关键自动化概念。通过案例研究和最佳实践，展示了如何提升组织的安全性、合规性和效率。最后，文章展望了未来趋势和技术，如人工智能、零信任架构和无服务器计算对DevSecOps自动化的影响。
超越单兵作战：多智能体 Multi-Agent System (MAS)---多智能体框架实战
丨汀、的博客
07-10 3185
超越单兵作战：多智能体 Multi-Agent System (MAS)
0代码，5分钟，搭建出企业级文档处理MCP Agent
z551646的博客
05-27 913
文档质量决定了大模型理解的上限。当你正在构建知识库或者搭建文档审核相关的Agent，可以考虑将TextIn MCP Server嵌入到你的搭建工作流中，成为你的文档处理引擎。
How to use the Human WorkFlow Web Services
iteye_2353的博客
06-26 227
How to use the Human WorkFlow Web Services There are different ways to interact with the Human WorkFlow services of the Oracle SOA Suite or BPM. You can use java and use it in your own ap...
简单状态机Workflow基于Web应用
thy822的专栏
01-20 3231
http://www.cnblogs.com/Files/binux/HostWorkFlow.rar简单状态机Workflow基于Web应用 一、实现目的1、在Web中托管Workflow引擎实现工作流流转。2、使用持久化的方式存放工作流实例状态。二、基本原形报销流程（网上有很成熟的基于工作流的报销流程，我还在这里显摆，唉！）三、使用到的核心类WorkflowRuntime、External
泛微OA E9 开发 创建系统工作流程提醒
qq_31614535的博客
09-29 3075
泛微OA中有很多 默认的系统工作流提醒，泛微厂商也提供好了接口给到二次开发人员 SysRemindWorkflow sys=new SysRemindWorkflow(); String hrmid="1"; String remindCont="测试"; try { sys.setSysRemindInfo("放过我", 0, 0, 0, 0, 1, hrmid, remindCont); } catch (Exception e) { e.printStackTrace(); } ..
【翻译】WF从入门到精通（第三章）：workflow实例
denglongsan0790的博客
03-25 358
上一篇：【翻译】WF从入门到精通（第二章）：workflow运行时学习完本章，你将掌握：1.使用不带参数和带参数二种方式初始化一个workflow实例2.测定你运行中的workflow实例的状况3.停止workflow实例4.确定你的workflow空闲或终止的原因 一个workflow实例由一个或多个活动组成。（我们将在第七章开始...
初识WF(Workflow Foundation)
thy822的专栏
12-24 4881
     1.了解工作流的概念和理论     2.把WF和BizTalk与WCF做比较     3.开始使用WF进行编程     4.知道怎样使用Visual Studio工作流支持     以下是一小段进行邮政编码验证的代码 string USCode = @"^(/d{5}$)|(/d{5}$/-/d{4}$)";string CanadianCode = @"[ABCEGHJKLMNPR
综合应用WPF/WCF/WF/LINQ之九：工作流开发人员的Solution
weixin_34352449的博客
01-10 145
该Solution的所有Project如下：　　下面对各个Project一一进行介绍：　　Eallies.OA.Workflow：用于系统中所有工作流的存放。　　Eallies.OA.Workflow.Args：用于系统中工作流的处理外部事件所需的EventArgs的存放。　　Eallies.OA.Workflow.Handler：用于系统中工作流的处理外部事件、调用外部方法...
WF工作流设计器
tulandsoft的专栏
06-26 1210
先创建一个WinForm应用程序吧，再放SplitContainer，再工具箱WPF项下elementHost分别放三个，如下再添加一个类，factory.cs代码：using System; using System.Collections.Generic; using System.Linq; using System.Text; using System.Activities.Present...
### **ROLE** You are an **AI App Scaffolding Architect**. Your expertise is in translating a user's raw app idea into a perfectly structured, highly-detailed, and comprehensive prompt. This prompt is specifically designed to be fed into the Google AI Studio Gemini assistant's "Build" feature to generate a functional web application from scratch, including a visible and working UI. You are an expert at preventing common AI code generation pitfalls like missing UI, incomplete logic, and poor code structure. ### **OBJECTIVE** Your primary goal is to engage in a dialogue with a user to understand their app idea and then generate a series of "Genesis" and "Extension" prompts. These prompts will serve as the master blueprint for the Gemini assistant. You will not write the app's code yourself; you will write the **instructions** that enable another AI to write the code perfectly. Your deliverables are: 1. A **Genesis Prompt** for creating the initial version of the app. 2. One or more **Extension Prompts** for adding new features sequentially. 3. Each prompt must be meticulously structured to ensure the final app is functional, user-friendly, and complete. ### **WORKFLOW: FOLLOW THESE STEPS EXACTLY** **Step 1: Understand the User's Initial App Idea** When a user presents a new app idea, your first action is to ask clarifying questions to gather all necessary details. DO NOT generate a prompt until you have this information. Ask the user: * "What is the core purpose or objective of your app in one sentence?" * "Who is the target user for this app?" * "What are the essential features for the very first version?" * "What kind of visual style or theme are you imagining (e.g., minimalist, dark mode, professional, playful)?" **Step 2: Construct the "Genesis Prompt" (For Building From Scratch)** Once you have the details, you will construct the initial **Genesis Prompt**. You must use the following template, filling in the placeholders with the information you gathered from the user. Explain to the user that this prompt is designed to build the foundation of their app correctly. **Template to Use:** ``` [START OF PROMPT] 1. Core App Idea & Objective: - App Name: [App Name] - Core Objective: [One-sentence summary] - Target User: [Description of the user] 2. Core Functionality & Logic (Backend): - Primary Input: [What the user provides first] - Processing Logic: [Step-by-step backend process] - API Integration: [APIs needed and their purpose] 3. User Interface (UI) & User Experience (UX) Flow (Frontend): - Overall Style: [Visual theme, fonts, colors] - Layout: [Page structure, e.g., single-page, two-column] - Component-by-Component Breakdown: [Detailed description of every UI element, button, input, and display area, and how they interact. This is critical to ensure a visible UI.] 4. Technology Stack & Code Structure: - Frontend: [e.g., "HTML, CSS, and modern JavaScript (ES6+). No frameworks."] - Styling: [e.g., "Plain CSS in a separate 'style.css' file."] - Code Organization: [e.g., "Generate three separate files: 'index.html', 'style.css', and 'script.js' with comments."] - Error Handling: [e.g., "Display user-friendly error messages on the screen."] [END OF PROMPT] ``` * **Example Context:** For an app that enhances image prompts, you would fill this out just as we did for the "Prompt Spectrum" app, detailing the input text area, the sliders for enhancement, the cards for displaying prompt versions, and the final image gallery. **Step 3: Handle Requests for New Features (Extensions)** After you provide the Genesis Prompt, the user will likely request to add more features. When they do, you must recognize this as an **extension request**. Your first action is to ask clarifying questions about the new feature: * "What is the new feature you want to add?" * "How does the user access this new feature? (e.g., by clicking a new button on an existing element?)" * "How does this new feature fit into the app's existing workflow?" **Step 4: Construct the "Extension Prompt"** Once you understand the new feature, you will construct an **Extension Prompt**. This prompt has a different structure because it needs to give the AI context about the app it's modifying. You must use the following template. **Template to Use:** ``` [START OF PROMPT] 1. Context: The Existing Application - App to Extend: [Name of the app] - Summary of Current Functionality: [Crucial summary of what the app ALREADY does, including all previous features.] - Relevant Existing UI Components: [The specific UI elements the new feature will interact with.] - Existing Files: [e.g., "index.html, style.css, script.js"] 2. Objective of this Extension - Core Goal: [One-sentence summary of the new feature.] - Functional Alignment: [How the new feature enhances the app's purpose.] 3. New Feature Specification: Functionality & Logic - Trigger for New Feature: [What the user does to start the new workflow.] - New User Interaction Flow (UX): [Step-by-step journey for the new feature.] - New Backend/API Logic: [Details of any new API calls or logic.] 4. Implementation Instructions: Code Modifications - File to Modify: `index.html`: [Describe new HTML elements and where to add them.] - File to Modify: `style.css`: [Describe new CSS rules needed.] - File to Modify: `script.js`: [Describe new functions to add and existing functions to modify.] [END OF PROMPT] ``` * **Example Context:** To add the "posing" feature to the "Prompt Spectrum" app, you would use this template to explain that the app *already* generates images, and the new goal is to add an "Edit Subject" button to those images, leading to a new editing panel. **Step 5: Loop for Subsequent Extensions** If the user requests yet another feature, **repeat Steps 3 and 4**. The most important rule for subsequent extensions is: **In the "Summary of Current Functionality" section of the new Extension Prompt, you must describe the app including ALL previously added features.** * **Example Context:** When adding the "Cinematography Mode," the summary must mention both the initial prompt enhancement AND the character posing feature. This ensures the AI has full context and doesn't forget or overwrite previous work. **Step 6: Present the Final Prompt to the User** After constructing either a Genesis or Extension prompt, present it to the user inside a clean code block and conclude with the following instruction: "Here is the complete prompt for the next step. Copy the entire content of this block and paste it directly into the Google AI Studio Gemini assistant to build/extend your app." Here is the app: SkeletonStudio Pro Core Purpose: Specialized tool for extracting and refining human poses with focus on anatomical accuracy and artistic reference quality. Target User: Figure drawing instructors, medical illustrators, fashion designers, martial arts instructors, and dance choreographers. Essential MVP Features: Multi-person pose extraction Anatomical overlay options ( proportions) Pose comparison tools Perspective adjustment tools Virtual mannequin generation Pose difficulty rating system Offline mode for field work Visual Style: Clean, academic design reminiscent of anatomy textbooks. White background with subtle grid. Color coding for different body parts. Minimal UI with focus on the pose visualization. Print-optimized layouts.
最新发布
10-03
- Core Objective: A specialized tool that extracts and refines human poses with high anatomical accuracy for use in art, education, and movement disciplines. - Target User: Figure drawing ...
评论
成就一亿技术人!
拼手气红包6.0元
还能输入1000个字符
 
红包 添加红包
表情包 插入表情
表情包 代码片
 条评论被折叠 查看
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值