The service was approved. Operations needs the right document.
Use records, lists and rules to generate service orders and other recurring documents from the process in Salesforce.
See this flow in a demo- Customer
- Acme Industries
- Site
- Taubaté/SP
- Service
- Preventive maintenance
- Equipment
- 12
- Scheduled date
- 21/08/2026
TRIGGER
Service approved Service Order
{ Customer } { Site } { Scheduled_Date } The service was approved. Now the team needs to head into the field.
A technical services company schedules a preventive maintenance visit at a customer site.
Salesforce already holds the customer, service location, contracted service, equipment involved, responsible technician and scheduled date.
Before the work starts, though, the team needs a Service Order. If the document is assembled by hand, someone has to look up the record, carry over the information, relate the equipment, build the table and check everything before releasing the OS to the team.
When that process happens several times a day, a simple task turns into recurring operational work.
- Customer
- Acme Industries
- Site
- Taubaté/SP
- Service
- Preventive maintenance
- Customer
- Site
- Service
The queue moves slower than the operation.
Each OS waits for someone to open the record, copy the data and build the equipment table before the team can be released to the field.
- OS-00840 ready
- OS-00841 ready
- OS-00842 waiting for document
- OS-00843 waiting
- OS-00844 waiting
Service Order
| Equipment | Model | Service |
|---|---|---|
| Compressor 01 | XP-200 | Inspection |
| Compressor 02 | XP-200 | Preventive |
| Pump 04 | RT-10 | Inspection |
12 related equipment items
Record, related items and rules shape the document.
With docu2.me, Service Order information can feed the corresponding template.
Key data enters as dynamic fields, and related records can form lists and tables.
Rules can control which blocks or instructions appear depending on the service type.
Service Order
{ Customer }{ Site }{ Scheduled_Date }The OS enters the queue and comes out as a document ready for the team.
- OS-00840 ready
- OS-00841 ready
- OS-00842 Waiting Generating...
- OS-00843 waiting
- OS-00844 waiting
Service order
{ Customer } Acme Industries { Site } Taubaté/SP | Equipment | Model | Service |
|---|---|---|
| Compressor 01 | XP-200 | Inspection |
| Compressor 02 | XP-200 | Preventive |
| Pump 04 | RT-10 | Inspection |
Preventive and corrective service do not ask for the same checklist.
Preventive checklist
- inspection
- cleaning
- measurement
- validation
Corrective checklist
- diagnosis
- part replacement
- load test
- incident record
From the operational record to the released OS.
- 01
Record
Operations keeps the service data in Salesforce.
- 02
Relationships
Equipment, items or other related records are part of the context.
- 03
Rules
The template can present information according to the operational scenario.
- 04
Output
The Service Order is generated and moves to the next step defined by the company.
What changes for the operations team.
The operational data already exists. The document can be born from it.
With docu2.me, records, related items and rules can automatically compose the document that accompanies execution.