Preface
Introduction
- Managed File Transfer General Features
  - Workflow Automation
  - Ad-Hoc File Transfers and Collaboration
- Getting Started
  - Screen Tips
  - Login
Dashboard
Resources
Workflows
Task Reference
Services Overview
Users
Logs and Reports
Encryption
System
Appendix
Glossary Terms
- AES
- Asymmetric
- Asymmetric Cryptology
- Authentication
- Certificate
- Certificate Authority
- CIDR
- Cipher
- Cryptology
- CSV
- Decryption
- Diffie-Hellman/DSS
- Digital Signature
- DSA
- Element
- Encryption
- Fingerprint
- FTP
- FTPS
- Hash Function
- HTTP
- HTTPS
- ICAP
- Icon
- ISO format
- JCE Service Provider
- JDBC drivers
- JKS
- Key
- Key Alias/Key ID
- Key Pair
- Key Store
- MDN
- MMS
- Non-Repudiation
- Passphrase
- PKCS12
- Private Key
- Project
- Public Key
- Public Key Cryptology
- Public Keyring
- RSA
- Run Priority
- SAML
- Secret Key
- Secret Keyring
- Self-Signed Certificate
- SFTP
- Signing
- SMS
- SMTP
- SSH
- SSL
- SSO
- Symmetric
- Symmetric Cryptology
- URL
- Variable
- Verification
- XML

User Guide

10.5.0
- 10.5.3
- 10.4.0
- 10.2.3
- 10.2.2 HotFix 1
- 10.2.2
- 10.2.1
- 10.2

Back Next

Example 1: Raise Error

In this example, if no files are found on a server (by checking the ${numberOFfiles} variable), then the task will raise an error and abort the Project.

From within the Project Designer page, expand the Miscellaneous folder in the Component Library, and then drag the Raise Error task to the Project Outline.

On the Basic tab of the Raise Error task, specify the Message to write to the Job Log. If no Message is specified, the system variable system.job.error will be written to the Job Log.

On the Control tab of the Raise Error Task, specify the condition that must be met to run this task. In this case we will check if the number of files is equal to 0.

Click the

Save

button when finished.

Raise Error Task

Download Guide

Watch

Comments

Communities

Knowledge Base

Success Portal