தளம் › உள்ளமைவு
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 |