Governance & lifecycle
Manage deletion history, retention and recovery through a common record lifecycle.
Deleted Record Vault · Retention · Audit historySecurity, policies, audit, recovery, notifications and lifecycle controls come from the platform, so they don’t have to be rebuilt inside each application.
A small team can run a demanding workload. Choose hosting capacity around the work your business needs to do, with capacity and cost considered together.
SmartWorx’s hosting model gives each customer a separate application environment, with compute resources allocated to that environment.
SmartWorx does not ration APIs, workflows, or application capabilities simply to protect other customers’ workloads. When an environment needs more capacity, the underlying resources can be increased.
Size and validate the environment for your work. Supported concurrency, scheduling, infrastructure, and connected-service constraints still apply.
Hosting is separate from software licensing. Choose resources for the work, with additional capacity scoped to the environment.
See hosting pricingAn application from your team and one from an independent publisher can take part in the same work. SmartWorx supplies the common services beneath them, so you can connect a process across applications without building a separate API integration for every handoff.
Each application keeps its own purpose, configuration and support arrangements. Shared records, permitted actions and workflows bring them together where your organization needs them to.
See how work connects across applicationsYour information does not have to stay tied to your old software. Bring files, documents and records into SmartWorx in the way that fits them—then decide how you want to use them.
Upload files. Convert supported documents to HTML.
Map and import spreadsheets or files from a directory.
Collect records through APIs. Keep selected information updated.
Recreate a familiar record structure as SmartWorx entities and relationships, or map and transform the information to fit a new application. Historical records can stay useful as reference material alongside your current work.
Once the information is migrated and checked, you can access it in SmartWorx without relying on the old application to display it.
Upload a document for people to use, import a set of records, or configure a workflow to collect information from another system through its API. Repeat imports and connected workflows can keep selected information updated while both systems remain in use.
Explore APIs & ConnectivityPlatform-level backups and operator-executed recovery are part of the service foundation. Keep recovery scope, responsibilities, and verification aligned with the needs of your organization.
Baseline system backups support the platform’s recovery arrangements.
Work with the platform team to review a recovery request and agree the appropriate operation.
Confirm recovery objectives, retention, and verification responsibilities in the applicable service agreement.
Authorized administrators can inspect retained deletion records and related impacts. Supported record restoration depends on the record type and retention scope.
A retained deletion record and an environment backup are different recovery starting points. Match the request to the information and scope you need to recover.
Discuss recovery requirementsCapture diagnostic context for administrators while giving useful guidance to the person who encountered the problem. Connect error references, user-facing tips and support procedures instead of leaving people with an unexplained failure.
External service timeout
“Refresh failed. Contact support if it continues.”
Reference: connection troubleshootingError reference · time · affected operation
Manage policies for identity, data lifecycles and content from a common workspace. Reuse the applicable controls as applications grow.
Surface in-app notifications and banners where people work. Give users updates, useful guidance and a clear way to acknowledge or dismiss a message. Configured email processing can also be part of a business workflow.
You don’t have to replace everything to make work better. Put one process to work in SmartWorx, connect the systems you rely on, and move more work when you’re ready.
See how gradual adoption worksStart with a useful application and shape it around the way your team works.
Bring the information and supported actions into the process. Keep the systems that need to remain the source of truth.
Add applications and extend workflows as you’re ready. Replace an old system when its replacement is ready to take over.
SmartWorx provides the shared foundation. The applications you build or choose supply the business capabilities with their own dependencies and support arrangements.
Explore Application BuilderGive your applications a consistent foundation for controlled access, traceable changes and recovery. Your people can focus on their work, while your organization stays in control of its information.