Asset dependency

 The Asset dependency rule creates an asset before the current asset. The dependent assets are executed only when the previous asset status is completed. This rule is helpful and effective when the job has multiple dependencies on other assets.

• For the selected asset, let us configure an Asset dependency rule.
• Place the cursor on the asset and right-click on it to view various options ‘Add asset’, ‘Add rule’ and ‘Delete asset’.
• Click the Add rule.
• A Configure rules to the asset slide window appears from the right side of the page.
• Select the Asset dependency rule.

• The Configure Asset dependency slide window is displayed.
• Click the Select button to select dependent assets.

• The existing pipelines are displayed with a checkbox.
• Type a text in the ‘Search Pipeline’ field to search and select the required pipeline.
• Click the drop-down list beside the text Pipeline to view other Dextrus components (Recipe, AI/ML Models, Schedules, and Rest APIs).
• Click the Confirm button to confirm the selected assets. 

Note: Single/Multiple assets can be selected to create an Asset dependency rule.

• The selected asset dependency (CSV_190422) is updated with a delete icon.
• Based on the selected asset execution status the rule can be defined.
• Additionally, you can click Add Condition button to add a condition to the existing execution status.

In our use case, we selected execution status as ‘Success’.

• Click the Save and Close button to schedule a job.
• Click the Save and Add button that redirects to the ‘Configure rules to the asset’ slide window to add another rule to the existing asset.

• The dependent asset gets executed only when the previous asset execution status is ‘Success’.
• Click the Schedule button to schedule this job.

• Select the ‘Schedule Later’ radio button to execute the job at a later time.
• Select the Recurrence type as ‘Recursively’. The Recurrence type is classified into:
  • Once: The job gets executed only once for the selected date and time.
  • Recursively: The job gets executed repeatedly for the selected date and time.

Note: When the Recurrence type is selected as ‘Recursively’ then Repeat every, Recur on, End Recurrence by, and Select End Date options are displayed.

• Repeat every: The recursively scheduled job gets executed repeatedly based on the input interval provided in the text field.

Note: The Repeat every drop-down list consists of Day, Month, Minute, Hour, and Week options. Its value cannot be less than 1.

• Recur on: The Recur on can be defined on either one of two criteria:
  • Day of Week: All seven days of the week are displayed horizontally where single/multiple days can be selected.
  • Day of Month: The start date can be selected from the calendar.
• End Recurrence by: The End Recurrence can be defined on either one of two criteria:
  • Occurrence: A value is specified to execute the job multiple times.
  • Date: The end date can be selected from the calendar.
• Set the Repeat every option for the Month.
• Set the Recur on option for Day of Month.
• Select Start Date from the calendar.
• Select Start Time from the Clock.
• Set the End Recurrence by Date.
• Select the End Date from the calendar.
• The CRON Expression field is auto-generated based on the above-selected options.
• Click the Apply button.

Note: Based on the selected date and time the job gets executed accordingly.

• Alternatively, if you select Recur on as ‘Day of Week’, the seven days of the week are displayed.

• The Successfully Scheduled Job page displays the Job name.
• To view the job execution details, click the View Run Details button.

Note: You can click the Edit Job or Edit Schedule button to modify the job and schedule details as per your requirements.

The Run Results provides the job execution details with Job name, Tags, Sessions, Scheduled By, Started On, Ending On, and Alerts.

• The asset displayed in green color signifies the job is executed successfully or else the asset displayed in red color signifies the job execution has failed.

Important steps to follow if you want to abrupt the scheduled job and sessions:

Kill Session: Current session will be killed and other sessions will execute as per the schedule.

• Click the Kill Session button to kill the execution (current session) of the scheduled job.
• Click the Session Details tab.

While the scheduled job is executing, you can Stop, Pause and Resume the job.

• Go to the Job Details tab for the selected job.
• Click the Stop icon to stop the job.
  • Stop: All other sessions of the schedule will be stopped and you will have to create a new schedule.
• Click the Pause icon to pause the job.
  • Pause: All other sessions of the schedule will be paused, unless you resume them.
• Click the Resume icon if you want to continue the job execution.

To view the session history of any executed job.

• Go to the selected project dashboard page from the Project Details tab.
• Click the vertical ellipses against the chosen job to view: View run history and Delete/Archive options.
  • View run history: Displays the selected job session details.
  • Delete/Archive: Deletes the selected job.

• The Session Details page displays the session status (Success/Failed/In-Progress) with additional information.

• Navigate to the Run Results tab and click the vertical ellipses beside the text ‘Alerts’.
• The Job details, Edit Job, and Edit Schedule drop-down list appears.
• To view the executed job summary, select the Edit Job option from the drop-down list.

• The selected Job page is displayed.
• Place the cursor and double tap on the asset on which the asset dependency was configured.
• The selected asset (node) summary is displayed along with the configured Asset dependency rule.