Page 1 of 115. Showing 1,143 results (0.016 seconds)

  1. Integration Pattern for Looking Up Data During Run Time

    Looking Up Data During Runtime
    Jitterbit Success CentralMay 10, 2018
  2. When to Use a Schema

    that are adjacent to the transformation, or they can be defined directly in the transformation.  When to Use a Schema Whether a file schema is required depends … activity is any activity that receives data within the operation. This data can come from a source activity, from a transformation, or from other input
    Cloud StudioApr 09, 2020
  3. Operation Logs

    for downstream operations are also included. Child operation logs are sorted in the order the operations were executed (that is, by Time Started). You can limit … the calendar datepicker: image2020-2-28_8-54-13.png Refresh Logs The initial logs are displayed based on the date and time that the last operation was run
    Cloud StudioJun 01, 2020
  4. Operation Options

    Introduction Each operation can be configured with options such as when the operation will time out, what to log, and the timeframe for debug logging … is the maximum amount of time the operation will run for before being canceled. In the first field, enter a number and in the second field use the dropdown to select
    Cloud StudioApr 15, 2020
  5. Operation Actions

    : The action will be triggered when the operation is successful. TIP: You can force a success trigger even if the operation failed. This setting is available under … . These actions can be configured: Run Operation: This option is used to kick off the operation selected in the next dropdown, and can be used to link
    Cloud StudioMar 04, 2020
  6. Operation Options

    : Operation Time Out The Operation Time Out is the maximum amount of time the operation will run for before being canceled. If your operation has large datasets or is complex, this may cause the operation to take a longer time to run. By default, the Operation Time Out is set to 2 hours. If the operation is running for more
    Jitterbit Success CentralDec 18, 2019
  7. Looking Up Data During Runtime

    Use Case A common need is to pass data to a target system which must be 'enriched' with data that is not native to the source. The source may contain a value that can be used in a lookup that is done on-the-fly. NOTE: This design pattern uses Design Studio as an example; you may apply the same concepts in Cloud
    Jitterbit Success CentralApr 19, 2019
  8. Upserting Clarizen Data with a Chain of Operations

    to use for the upsert operation using the standard Jitterbit functionality. You can use a variety of sources of data. For this example, we will query all … ). This will be used as the source for our upsert data in the next operation. Run a new transformation operation upon success (right-click on operation background > On Success
    Jitterbit Success CentralApr 19, 2019
  9. Operation Deployment and Execution

    that are automatically deployed at the time of execution. When you run an operation, any downstream (linked) operations are also executed. As described below, you can execute operations manually at design time, using a script (in either Cloud Studio or Design Studio), from a command line on an agent, using an API trigger
    Cloud StudioApr 15, 2020
  10. Operation Schedules

    Introduction Each operation can be configured to run automatically by applying a schedule. Schedules contain information about when an operation … at [hh:mm] [AM/PM]: The schedule will activate the operation only once at the time in the text box to the right, which can be specified either using the dropdown
    Cloud StudioApr 15, 2020