One platform for business processes, people and automation.
Explore the building blocks of a WorkflowRight application: structured data, versioned forms, executable processes and operational workspaces. See how shared governance connects these capabilities from configuration to daily use.
A shared operating model, from definition to outcome.
Applications bring records, forms, process definitions and reporting into one business context. Organizations supply the membership and access boundary. A person can work on an assigned task while the process retains the record, published version and operational history behind it.
This relationship matters after launch. A failed automated step needs an operator, a task needs an authorized person and a new version must preserve work already running. WorkflowRight treats those as connected responsibilities rather than separate utilities.
Configure your application, then fine-tune it.
Start with a blank application or browse the Industry Starter Library in Applications after signing in and choosing your organization. Professional Services, Accounting Office, Property Management, Service Company and Medical Office starters provide optional configuration over the same universal BPMS engine.
An installed starter becomes a normal editable application. Use native designers to adapt its data, forms, workflows, responsibilities, navigation and reporting. It is neither a fixed industry product nor permanently driven by the source JSON. Catalog updates do not silently change your installed application.
Choose a starter, destination workspace and unique application name.
Map its responsibilities to existing authorized roles.
Validate, inspect the preview and confirm installation.
Open the application's Setup tab to review and edit its native configuration.
Configure access, invite employees and assign responsibilities deliberately.
Test a representative process and its exceptions before beginning operations.
Starters do not invite staff, grant privileges or enable automations automatically. Setup separates your review acknowledgements from verified application facts; neither installation nor a completed checklist guarantees operational readiness. Your plan allowances and permissions still apply.
WorkflowRight Mobile Companion is the Android app for people who participate in WorkflowRight-powered business processes. Connect to your authorized organization, find your work and complete supported task actions. Build and govern the applications on the web.
Your organization defines its applications, business data, forms and processes in WorkflowRight Web. Published process definitions determine the work that participants can access. The Mobile Companion gives authorized people a focused way to participate in that work.
A process definition describes how a business record moves through people, decisions and automated steps. WorkflowRight turns that definition into work that can be assigned, completed and operated over time.
Begin with the business record and the event or person that starts the process. Place manual tasks where someone must review information or make a decision. Use exclusive decisions to choose a supported route based on business conditions, and structured actions to perform defined operations.
A workflow form is the point where business context becomes an authorized action. WorkflowRight connects form definitions and published versions to structured records and manual tasks.
Start with the application entity and the fields that represent the work. Form configuration determines how supported fields are presented and which values need validation. The purpose is to give a person the right context to complete a specific step, rather than ask them to reconstruct the process from a general record screen.
WorkflowRight processes operate on structured business data, not isolated task cards. Application entities and fields give the work a consistent subject that people, automation and reports can use.
An application entity defines a kind of business information. Its fields describe the supported values a record can hold. Individual records then represent the requests, items or cases your organization works on. Begin with the information needed to identify, route and complete the process.
Ordinary employees should be able to use a business application without entering its definition builder. WorkflowRight separates configuration work from the end-user workspace where records, process starts and tasks come together.
Builders and administrators configure the application, its definitions and its presentation. End users enter an application workspace with navigation appropriate to the work they need to perform. Home, record access and process starts provide a practical entry point into the configured application.
Business automation must account for waiting, repeated delivery and failure. WorkflowRight combines rules, structured actions, events and schedules with durable execution and an operational recovery model.
Event-driven automation starts in response to a defined business event, such as a supported record change. Scheduled workflow automation starts from a configured time or recurrence. The distinction is the source of the work; both need clear conditions, permissions and operational handling.
An integration is part of a business process, including its failure behavior. WorkflowRight provides configured REST connections, inbound webhooks and outbound service actions with mappings and operational history.
Start with the business information the external service needs and the result the workflow expects. A connection supplies the service configuration; mappings determine how supported values move between the workflow context and the external request or response.
Reporting should answer a concrete operating question: what is waiting, what needs attention or how the recorded work is distributed. WorkflowRight connects saved views and dashboards to the platform’s authorized data.
Saved views describe a repeatable way to inspect supported record, process, task or incident sources. Choose the source and fields that answer the question, then apply filters and sorting. Where the report supports grouping and aggregation, use them to summarize the selected information.
A decision often depends on more than structured fields. WorkflowRight associates comments, private attachments and activity with the business subject so people can understand a request and its handovers in context.
Comments belong to a record, process or task rather than a disconnected conversation. This gives the next person a place to understand clarification, supporting context and the reasoning shared during a handover. The subject’s access boundary remains important: participation follows authorization, not possession of a public link.
Workflow governance connects process ownership, permitted actions, controlled change and reviewable evidence. The platform implements the access controls that support this wider operating policy. WorkflowRight combines organizations, memberships, roles and scopes so application configuration does not become uncontrolled authority.
Organizations provide the tenant boundary for applications, people and data. Invitations bring people into that organization through a controlled membership flow. Roles and scoped permissions describe what a member may do and where that authority applies.
A business application changes after its first release. WorkflowRight’s package v2 model supports portable definitions, destination configuration and controlled upgrades while preserving the versions behind running and historical work.
An application release describes a configuration that can be exported as a portable package. Package validation examines supported definitions and their dependencies so an installation is more than a collection of unrelated files. Forms, processes and other assets must refer to compatible configuration.
My Work and candidate assignments support the person completing a task. Team Work, process instances and incidents support the coordinator looking across execution. Reporting turns selected records and operational sources into reusable views, dashboards and exports.
Evaluate the normal path and a controlled failure. Review how a person is assigned, how a timer resumes work and how an operator investigates an incident. The architecture overview explains these boundaries; security and governance explain how access is enforced.
Use plan allowances to frame your evaluation, then discuss a representative process. The useful starting point is the outcome your organization needs and the information and responsibility required to achieve it.
EVALUATE WITH YOUR BUSINESS CONTEXT
Bring a real process. Review how it should operate.
Discuss the information, responsibilities and controls your organization needs.