Table of Contents

Search

  1. Preface
  2. Introduction
  3. Dashboard
  4. Resources
  5. Workflows
  6. Task Reference
  7. Services Overview
  8. Users
  9. Logs and Reports
  10. Encryption
  11. System
  12. Appendix
  13. Glossary Terms

Managed File Transfer User Guide

Managed File Transfer User Guide

Call Project Task

Call Project Task

Projects can be designed to call other
Projects
in the same
Managed File Transfer
installation. This is useful when you want to create reusable logic that multiple Projects can execute.
One example usage would be to create a Project that accepts a file name from a variable and encrypts the file with a public key. Then other Projects that need that same functionality can simply call that Project and pass in the file to encrypt.
By default, the
Run In Same Job
attribute is set to true. When this attribute is set to true, the specified Project is called and the current Project will wait until the called Project completes. The called Project will not generate a new job number, job log or workspace. When set to false, the specified Project is submitted for execution as a separate job, which will have its own job number, job log, workspace etc.
If you specify to run the Project in a separate job you should consider whether you want the calling Project to wait for the job to finish (interactive mode) or if the calling Project should kick off the other Project and immediately continue executing (batch mode). By default, the
Mode
attribute is set to interactive. When calling the Project is in Batch Mode, the Advanced tab allows you to specify the Job Queue and queue priority the called Project will execute in. If no Job Queue is selected from the calling Project, the called Project will execute in the Job Queue specified in its own Project. If the called Project does not have a specified Job Queue, the Project will execute in the default Job Queue.
When calling a Project you need to indicate whether or not all user-defined variables should be passed over to the Project being called. By default, the
Pass User Variables
attribute is set to false. User-defined variables are variables that belong to the parent Project, whether they are Project variables, or variables created "on the fly" by some other task. Variable sub-elements of the Call Project Task will always be passed to the called Project, regardless of this setting. This setting is only valid if
Run In Same Job
is set to true. If
Run In Same Job
is set to false, this value will be ignored.
The Return User Variables indicates whether or not the user variables created by the called project are returned back to this project. If set to true, after the called project finishes, all user defined variables (except RowSets) will be accessible to this project. This setting is valid only when Run In Same Job is set to true. If
Run In Same Job
is set to false, this value will be ignored.

0 COMMENTS

We’d like to hear from you!