平台 › 配置
Process & Structure
What this company adds to the product without code: its own statuses and the moves between them, who approves what, the kinds of organisation unit it has, the lists it extends, and which parts of a module it uses.
在 平台 → 配置 · 11 屏幕
工作区Feature TogglesSwitch a section of a module off for this company: its screens leave every menu, its routes refuse, and ASK stops offering it. Everything is on until you say otherwise.行政打开记录StatusesThe statuses a document can hold. The built-in ones are locked; add your own (On hold, Awaiting vendor) and join them with moves under Status Transitions.打开记录Status TransitionsA move from one status to another with a name: who may make it, the fields that must be filled first, a condition the record must meet, and whether a note is needed. A move named like a built-in verb (confirm, close) also lets that built-in action start from this status. Moves are made through the move route and ASK.打开记录Approval Document TypesWhat can be sent for approval. The built-in types are run by their own modules' rules (listed under Approval Rule Catalogue) or by self-service; add a type of your own by naming the table it lives in. No code needed.打开记录Approval RoutesThe first active route (lowest priority number) a document meets decides who approves it. Steps are added on Approval Steps: the same level is parallel, levels run in order. A step with no reachable approver and no fallback stops the document being sent -- nothing is approved by default.打开记录Approval StepsWho decides, in what order. Steps with the same level number are parallel (all must approve). Name a fallback for when the approver has left, is the requester, or the role is empty.打开记录Approval RequestsEvery document sent through this company's own routes, and where it stands. Approvers decide in My approvals.打开记录Approval Rule CatalogueEvery approval rule in the company in one list: the routes written here and the rules the purchasing, sales, hiring and journal screens keep. The older ones still run exactly as before and are edited where they are kept.打开记录Unit TypesThe kinds of organisation unit this company has. Company, business unit, division, department, cost center and site are built in and locked; add region, plant, branch or school beside them.打开记录Unit Type RulesWhich type may sit under which. A type with no rule here can sit anywhere, as before; once it has one, only the parent types named are allowed.打开记录Extendable PicklistsThe drop-down lists a company can add values to. Add a value under Admin > Configuration Lists with the list key shown here; the form then offers it and the record accepts it.打开
列、字段和操作
| 屏幕 | 种类 | 它是什么 | 列 | 田野 | 行动 |
|---|---|---|---|---|---|
| Feature Toggles | 工作区 | Switch a section of a module off for this company: its screens leave every menu, its routes refuse, and ASK stops offering it. Everything is on until you say otherwise. | 0 | 0 | 0 |
| Statuses | 列表 | The statuses a document can hold. The built-in ones are locked; add your own (On hold, Awaiting vendor) and join them with moves under Status Transitions. | 6 | 7 | 0 |
| Status Transitions | 列表 | A move from one status to another with a name: who may make it, the fields that must be filled first, a condition the record must meet, and whether a note is needed. A move named like a built-in verb (confirm, close) also lets that built-in action start from this status. Moves are made through the move route and ASK. | 7 | 11 | 0 |
| Approval Document Types | 列表 | What can be sent for approval. The built-in types are run by their own modules' rules (listed under Approval Rule Catalogue) or by self-service; add a type of your own by naming the table it lives in. No code needed. | 6 | 18 | 0 |
| Approval Routes | 列表 | The first active route (lowest priority number) a document meets decides who approves it. Steps are added on Approval Steps: the same level is parallel, levels run in order. A step with no reachable approver and no fallback stops the document being sent -- nothing is approved by default. | 8 | 11 | 0 |
| Approval Steps | 列表 | Who decides, in what order. Steps with the same level number are parallel (all must approve). Name a fallback for when the approver has left, is the requester, or the role is empty. | 8 | 13 | 0 |
| Approval Requests | 列表 | Every document sent through this company's own routes, and where it stands. Approvers decide in My approvals. | 8 | 0 | 0 |
| Approval Rule Catalogue | 列表 | Every approval rule in the company in one list: the routes written here and the rules the purchasing, sales, hiring and journal screens keep. The older ones still run exactly as before and are edited where they are kept. | 10 | 4 | 0 |
| Unit Types | 列表 | The kinds of organisation unit this company has. Company, business unit, division, department, cost center and site are built in and locked; add region, plant, branch or school beside them. | 4 | 5 | 0 |
| Unit Type Rules | 列表 | Which type may sit under which. A type with no rule here can sit anywhere, as before; once it has one, only the parent types named are allowed. | 2 | 2 | 0 |
| Extendable Picklists | 列表 | The drop-down lists a company can add values to. Add a value under Admin > Configuration Lists with the list key shown here; the form then offers it and the record accepts it. | 6 | 0 | 0 |