Copy Job

With this node you can copy a Job.

It has the following configuration options:
  • Copy Job ID: here you can define the job to copy. The new job will be a copy of the specified Job record in the database, keeping all predefined information, tasks etc.
  • Parent Job ID: here you can enter a unique parent Job ID where the Job will be nested into. If you leave this field blank, the Job will stand on its own.

  • Job Type: here you can select the type of Job. You can use this to store several different sets of Jobs in one database collection. You can leave this blank if your template Job already contains a type.
  • Identifier: here you can define a (unique) identifier for this Job. This is not an auto assigned value, and there is no constraint on the contents. This value is intended to either provide a back-link to the Job in the master database or to provide a human way to reference the Job in an unique way. The fact that this key is unique is not enforced by CLOUDFLOW. The default value is an empty string.

  • Name: here you can define a name of the Job.
  • State: here you can define the (initial) state of the Job. You can leave this blank if your template Job already contains a type.
  • Description: here you can define a description for the Job.

  • Team name: here you can assign a team to the Job.

  • Clear Files: if you select this checkbox, all file references from the copied Job will be removed. This does not have an impact on files on disk.
  • Files: here you can selects (an initial) set of files for the Job.
  • Files Tag: here you can define a tag to assign to the added files. You can leave this blank if you do not want to assign a tag to the files (that is, if all the files in your Job have the same meaning).
  • Clear Folders: if you select this checkbox, all folder references from the copied Job will be removed. This does not have an impact on folders on disk.
  • Folder: here you can select (an initial) folder for the job.
  • Folder tag: here you can select a tag to assign to the added folder. You can leave this blank if you do not want to assign a tag to the folder (that is, if all the folders in your job have the same meaning).
  • Preview File: here you can select (an initial) file to use as preview for the job.

  • Copy variables in Job: here you can select if you want to copy all variables from the workable to the Job and where to save them. If you not want to copy and save the variables in the Job, you can leave this parameter blank. If you want to copy and save the variables, you need to set it to the location where you want to save variables (preferably in the custom section of the Job).
  • Define (custom) data to be assigned to the created Job: here you can set specific data in the new Job (in the database). You can save data in any location in the Job, but you should always save non-standard data in custom sections.

    In case you have used a template that also contains (custom) data, the specified data will overwrite any data from the used template, but will be overwritten by direct parameters in this node (for example Name, Identifier...).

    Select + to add (custom) data. For each entry you need to define:

    • A path: here you can define a JSON path that selects an element in the JSON document. You need to use a dot notation to reach specific data in the database. Select the pencil to open Expression Builder.
    • A value: here you can specify the value you want to set for the specified data path. Select the pencil to open Expression Builder..
    See Job data for more information.

  • Select Created Job: if you select this checkbox, the newly created Job will be active for all the following nodes.

Form name for 'list edit': here you can specify the form you want to use if the Job data need to be displayed and edited in the Job's list view. If you leave this field empty, a form with the name 'Job_' + <type-of-job> + 'ListEdit' will be searched/used.

Form name for 'form edit': here you can specify the form you want to use if the Job data need to be displayed and edited in the Job's details view. If you leave this field empty, a form with the name 'Job_' + <type-of-job> + 'FormEdit' will be searched/used.

  • Assign this WhitePaper as handler: if you select this checkbox, workables will be created when certain values in the Job change. If you want to select a Start From Job on this whitepaper to handle these Job changes, you need to select this checkbox. If you don't want to set or change the handler in the created Job, you need to leave this checkbox unselected.
  • Assign this WhitePaper to get forms from: if you select this checkbox, this whitepaper is used to get forms from this whitepaper and to edit them from this whitepaper. If you leave this checkbox unselected, the form setup in the created job is not set or changed from this whitepaper.