江苏移动 OA 项目流程核心主要依托于两个配置库：人员组织（ryzz.nsf）、流程配置库 （lcpzk.nsf）。在流程配置库，不同公文流程通过文件类型标记配置意见、稿纸，而在环节中 配置与之绑定的环节以及路径。在环节中将定义流程提交时的候选人方式（按部门职级、按 岗位以及按前溯处理环节）以及特殊操作。流程配置库决定了 OA 流程的流向，而人员组织 提供了候选人数据。
独立需求通常是由业务部门通过文字描述或者给出样例，由设计人员针对原始需求说明 给出大致原始表单页面供用户确认。最简单的就是一张表格，然后一对一地去设计。稍微复 杂的是，需要运用到脚本技术进行动态控制，甚至根据流程状态进行相应的控制。更复杂的 是，做出类似于票据的界面，进行相应的汇总。这是表单基础设计方面。需求中包含流程图 或者让你参照的流程。一般对流程没有特殊操作或者接口同步的，相应改动就比较少。
项目设计是需要经过严密的逻辑分析、细致的推敲论证，必须事 先把能涉及到问题考虑清楚、可能存在的问题研究透彻，才不至于上 线频频出现问题。
做开发最忌讳的是，没有全盘考虑的概念，想到什么就做什么。 做开发最谨慎的是，删除无法恢复的东西，做永远无休止的循环。
江苏移动 OA 开发指南······································································································1
2.4.4.1 定时任务························································································ 24 2.4.4.2 分页································································································ 24 2.4.4.3 组合查询························································································ 25 2.4.4.4 数据统计························································································ 25 2.5 LotusScript 梳理···················································································· 26 2.5.1 常用公式······························································································26 2.5.2 常用 Lotus 开发函数与对象梳理························································ 27 2.5.2.1 了解 NotesSession·········································································· 29 2.5.2.2 了解 NotesDatabase········································································ 29 2.5.2.3 了解 NotesView·············································································· 30 2.5.2.4 了解 NotesDocumentCollection······················································ 32 2.5.2.5 了解 NotesViewEntryCollection····················································· 34 2.5.2.6 了解 NotesViewEntry····································································· 34 2.5.2.7 了解 NotesDocument······································································ 36 2.5.2.8 了解 NotesItem··············································································· 38 2.5.2.9 了解 NotesRichTextItem································································· 38 2.5.2.10 了解 NotesEmbeddedObject························································· 39 2.5.2.11 了解 NotesDateTime····································································· 39 2.5.2.12 了解 NotesName··········································································· 40 2.5.2.13 了解 NotesACL············································································ 41 2.5.2.14 了解 NotesACLEntry····································································42 附录 1：公式、LOTUSSCRIPT、JAVASCRIPT 参考············································· 44 附录 2：全文检索查询运算符············································································ 51
一般情况下，开发大致路线是设计表单、流程、设计视图、配置入口。复杂一点可能会 涉及接口开发、字典配置。
优化需求通常会给出一段描述进行优化的背景，然后会通过文字描述叙述需要做的事 情。我们需要将这段描述转换成，在什么服务器上什么模块下的何种表单或者前台入口需要 做何种改动。当然也有需要增加校验、增加字段、增加接口。优化需求通常比开发需求要略 微简单，只是一些改善、优化。 关于公文流程
2.3.1 DOM 部分······························································································ 6 2.3.2 表单元素······························································································· 6 2.3.3 总结······································································································· 8 2.4 Domino 开发简介························································································ 9 2.4.1 OA 表单常规设计················································································ 12 2.4.2 OA 流程表单开发················································································ 17 2.4.3 OA 流程操作简介················································································ 21 2.4.4 常用算法简介······················································································24
本文档旨在帮助有志于从事 OA 项目开发人员了解如何充实自 己的知识储备，如何去学习新的开发环境去开发以及如何去进行项目 设计等等。
同时，需要告诫各位同仁的是，程序开发没有捷径可走。给大家 一句忠告是，先学会思考，再学会做事，多反复检验，多勤于练习。 一定要多学多问，不要放过任何一个细小的问题；一定要完整测试， 不要错过任何一个细微的细节。
2.1 HTML 知识梳理···························································································· 2 2.2 常用 CSS······································································································4 2.3 Javascript 梳理························································································ 6
说 明······················································································································2 目 录······················································································································3 第一章 OA 项目开发概述····················································································1 第二章 OA 项目开发必备····················································································2
实际上，一个微型 OA 系统原型需要具备这么几个要素。从起草开始，可供用户选取的 提交路径，选择适应路径后可供用户选择的候选人，当选择候选人后如何改变状态使文件办 理状态转为所提交的候选人。这是原型核心需要考虑的，另外是一些附属定义，包括退回、 补发、收回功能以及流程跟踪。大家有兴趣可以参见我的第一个处女作也就是微型 OA 系统 原型的相关代码（省公司增值业务一线市场需求），不依托于流程配置库，代码实现提交路径 以及更改状态包含退回操作。 关于发送与反馈
业务咨询
扫码，关注我们
