Automate the nightly core export
How to connect the pieces you already know -- a workflow, a frequency, a wait for file, dependencies, and a failure event -- into one unattended nightly core export.
8 docs tagged with "Outcome"
An end-to-end business requirement, built by threading several features together.
View all tagsAutomation outcomes
Complete business requirements, built end to end -- each threads the individual features together into one thing you actually need to deliver.
Create reusable container jobs
How to build a child workflow as a container job, then deploy it so other workflows can reuse the same set of steps.
Exchange files with a partner
How to wait for an inbound file from a partner, validate and process it, and handle failures, without a person watching for the file to arrive.
Monitor critical paths and SLAs with Vision
How to build Vision cards with service-level agreements so an at-risk critical path is visible before the deadline is missed.
Publish a self-service request for business users
How to build a workflow and a service request, deploy them, and hand business users a guided form so they can trigger the automation themselves.
Recover a failed run automatically
How to build a failure-triggered recovery dependency and event so a failed run retries or reroutes on its own, before an operator needs to step in.
Set up failure notifications
How to create a notification group, target the jobs that matter, and prove it works, so a failure overnight never goes unnoticed.