Create and update work
Create records from a template, update information and change status.
After approval, prepare the replacement task and mark the request ready for fulfillment.
Help people get it right, apply your business rules, and keep the next step moving. Build rules and workflows visually—so your process doesn’t depend on everyone remembering every detail.
Choose what starts the process, define the conditions, and connect the actions. Arrange tiles and configure each step without writing code.
Choose a request value to see which review path applies.
Reason and equipment details are included.
Request value: $750
A declined request follows its configured response instead of these fulfillment steps.
Different situations need different information. Show the fields that matter, require the details your process needs, and explain what to do next. Your people follow clear guidance while the software handles the rules behind it.
Respond when a form loads, a field changes, before saving, or on demand.
Is the request type Replacement? The true and false paths define what happens next.
Replacement: show details, require a reason and show guidance. Otherwise: hide the details and make the reason optional.
Battery no longer holds a charge for a site visit.
Describe the problem and how it affects your work. Include the equipment reference so the team can help.
Reveal relevant fields and sections for the situation.
Require information only when the condition applies.
Fill values or calculate them from the information provided.
Lock a field when it should no longer be edited.
Give people useful tips and messages where they need them.
Bring the appropriate option forward for the task at hand.
A decision becomes useful when the right action follows. Configure the handoffs that take a request from someone’s intention to someone’s next task.
Create records from a template, update information and change status.
After approval, prepare the replacement task and mark the request ready for fulfillment.
Assign a record or task to the appropriate person or team.
Send the equipment handoff to the team responsible for that location.
Send notifications, email and useful messages.
Tell the responsible person what needs attention and link them to the work.
Branch on conditions, wait where needed and launch another workflow.
Follow the appropriate approval path before the next process begins.
Include a configured API action in the process.
Pass permitted order information to an external purchasing system.
While someone works
Rules can respond when a record opens or a value changes, guiding the screen in front of the person.
When the process needs to move
Use a supported save event, a button, a schedule or an incoming external event to start the configured workflow.
The request, the review and the equipment handoff may belong to different applications. They can still be part of one configured process.
Bring together applications built by your team or independent publishers within your SmartWorx environment. Coordinate their permitted records and actions without building a separate API integration for each internal handoff.
When work belongs in another system, use a configured API connection. Each application keeps its permissions, configuration and support responsibilities; separate customer environments do not automatically share information.
Explore APIs & ConnectivitySmartWorx provides and supports the platform. Independent publishers provide their applications and the support stated in their offerings.
When work stops, the useful question is where—and why. Follow recorded activity, inspect the affected step and use the available context to decide what needs attention.
Start with a process your team knows. Shape the guidance, decisions and handoffs around how you want the work to happen.