Orchestrator - Editing Transactions

orchestrator

2022.4

false

Orchestrator user guide

Getting started
- Introduction
- User Options
- Logging in to Orchestrator
- Resetting Your Password
- My Profile
- Robots
  - Robot Statuses
  - Robot Settings
- Auto Updating Client Components
- Orchestrator Configuration Checklist
Best practices
- Organization Modeling in Orchestrator
- Managing Large Deployments
- Automation Best Practices
- Optimizing Unattended Infrastructure Using Machine Templates
- Organizing Resources With Tags
Tenant
- About the Tenant Context
- Searching for Resources in a Tenant
- Robots
- Folders
- Monitoring
- Managing Access and Automation Capabilities
- Machines
- Packages
- Audit
- Credential Stores
- Webhooks
  - Types of Events
  - Managing Webhooks
- Licensing
  - Managing Your Licenses
- Alerts
  - Setting Up Alert Emails
- Settings
Resource Catalog Service
- About Resource Catalog Service
Folders Context
- About the Folders Context
- Home
Automations
- About Automations
Processes
- About Processes
- Managing Processes
- Managing Package Requirements
- About Recording
Jobs
- About Jobs
- Managing Jobs
- Job States
- Working with long-running workflows
Triggers
- About Triggers
- Managing Triggers
- Using Cron Expressions
Logs
- About Logs
- Managing Logs in Orchestrator
- Logging Levels
- Orchestrator Logs
Monitoring
- About Monitoring
- Machines
- Processes
- Queues
- Queues SLA
- Exporting usage data
Queues
- About Queues and Transactions
- Bulk Uploading Queue Items Using a CSV File
- Managing Queues in Orchestrator
- Managing Queues in Studio
- Managing Transactions
  - Editing Transactions
  - Field Descriptions for the Transactions .csv File
- Review Requests
Assets
- About Assets
- Managing Assets in Orchestrator
- Managing Assets in Studio
- Storing Assets in Azure Key Vault (read-only)
- Storing Assets in HashiCorp Vault (read-only)
Storage Buckets
- About Storage Buckets
  - CORS/CSP Configuration
- Managing Storage Buckets
- Moving Bucket Data Between Storage Providers
Orchestrator testing
- Test Automation
- Test Cases
  - Field Descriptions for the Test Cases Page
- Test Sets
  - Field Descriptions for the Test Sets Page
- Test Executions
  - Field Descriptions for the Test Executions Page
- Test Schedules
  - Field Descriptions for the Test Schedules Page
- Test Data Queues
Other Configurations
- Increasing the Size Limit of Package Files
- Setting up Encryption Key Per Tenant
- GZIP Compression
Integrations
- About Input and Output Arguments
  - Example of Using Input and Output Arguments
Classic Robots
- Robots
- Environments
  - Managing Environments
- Jobs
- Triggers
- Monitoring
  - Robots
- Resources
Host administration
- About the host level
- Managing system administrators
- Managing tenants
- Configuring host authentication settings
- Managing your host license
  - Allocating Licenses to Tenants
- Configuring system email notifications
- Configuring other host settings
- Audit logs for the host portal
- Maintenance Mode
Organization administration
- About organizations
- Managing organization administrators
- Configuring organization authentication
- Configuring security options
- Licensing
  - Activating your license
- Accounts and Groups
- Registering External Applications
  - Managing External Applications
- Overriding System Email Settings
- Audit Logs
Troubleshooting
- About Troubleshooting
- Frequently Encountered Orchestrator Errors
- Cron Expressions
- Upgrade troubleshooting

Editing Transactions

From the Transactions window you can edit the details of an individual queue item, or clone that item entirely. This is helpful for changing the priority or deadline of a transaction to respond to business needs, or editing the data input for failed transactions before retrying them.

Note: Editing is available for transactions with status New, Failed, or Abandoned, while cloning is available for transactions with status New, Failed,Successful, or Abandoned.

Editing a Transaction

To edit an individual queue item, follow these steps:

Click the More Actions button for the desired transaction. The More Actions menu appears.
Select Edit. The Edit queue item window is displayed:

The editable fields and their descriptions are:

Field	Description
Transaction priority	The processing priority level of the transaction, can be set to Low,Normal, or High. The priority is only editable for queues with disabled SLA predictions. If SLA predictions are enabled, the priority is set to High by default.
Postpone date and time	Enter the earliest date and time at which the transaction is available for processing.
Deadline date and time	Enter the latest date and time at which the transaction should be processed.
Specific data	Select download as JSON to obtain a file of the transaction item's specific data, for review and editing. The edited file, or an entirely new one, can replace the current transaction data via the upload JSON and override button. Note: The file cannot contain any arrays.
Transaction progress	Populated according to the progress property defined in Studio. You can Keep transaction progress as is, or Reset transaction progress by selecting the corresponding radio button.

Click Save to apply your edits to the transaction.

Cloning a Transaction

To clone an individual queue item, follow these steps:

Click the More Actions button for the desired transaction. The More Actions menu appears.
Select Clone. The Clone queue item window is displayed:

The editable fields and their descriptions are:

Field	Description
Transaction Reference	A unique identifier for the queue item. This key can be used in Elasticsearch to look for a specific item and view its logs.
Transaction priority	The processing priority level of the transaction, can be set to Low,Normal, or High. The priority is only editable for queues with disabled SLA predictions. If SLA predictions are enabled, the priority is set to High by default.
Postpone date and time	Enter the earliest date and time at which the transaction is available for processing.
Deadline date and time	Enter the latest date and time at which the transaction should be processed.
Specific data	Select download as JSON to obtain a file of the transaction item's specific data, for review and editing. The edited file, or an entirely new one, can replace the current transaction data via the upload JSON and override button. Note: The file cannot contain any arrays. Back slashes are not supported.

Click Create Queue Item to save the cloned transaction.

On this page

Editing a Transaction
Cloning a Transaction

Was this page helpful?

PREVIOUSManaging Transactions

NEXTField Descriptions for the Transactions .csv File