Confirming and completing the run request
When you run the job manually, you can either validate or execute the upgrade.
In validation mode, Poetic only emails a report of the anticipated results (number of orders generated, number of affected entitlements or machines).
In execution mode, Poetic performs the configured actions for the job:
Users cannot run a job in execution mode if they have not run it in validation mode, unless they have the security CAN_RUN_EXECUTION_WITHOUT_VALIDATION_RUN.
You cannot run an upgrade job that is inactive or that has future runs scheduled.
To create a run request for an upgrade job:
The Configure page of the Run Automated Upgrade Job process displays.
In the Upgrade run name field, type a name for the run.
To run the job in validation mode, click the Validate radio button. In validation mode, Poetic only generates a report of the anticipated results of executing the job.
To run the job in execution mode, click the Execute radio button. In execution mode, Poetic performs the actual upgrade.
When running in execution mode, you can set the following additional parameters:
| Maximum affected entitlements | In the Maximum affected entitlements field, type the maximum number of affected entitlements for the execution request.
For example, if the job is set to mark machines as upgradeable, then to restrict the number of marked machines to 200, type 200 in the field. |
| Ignore previous runs | This setting only applies for notification-only jobs and jobs configured to generate upgrade orders.
If you have already executed this job, you have the option to ignore the results of that previous run. To disregard the results of previous execution runs, and re-send the notifications or regenerate the upgrade orders, check the Ignore previous runs check box. For example, if one of the products was set up incorrectly, you could rerun the job to regenerate the orders. |
Whenever you run an upgrade job manually, either in validation or execution mode, you can email a report of the run results.
When the report is sent, the subject line is Automated Upgrade Report -runName - runMode, where:
The report includes:
When you finish configuring the run, click Next.
The Confirm page of the Run Automated Upgrade Job process displays.
If you are running the job in execution mode, then at the top of the Confirm page is a summary of the affected machines and entitlements.
Before you can complete the execution run, you must check the check box indicating that you understand the potential impact of running the job.
If you have not run the job in validation mode since the last time the job was updated, then an additional check box displays indicating that you accept the risks of running the job without a validation run. Before you can complete the execution run, you must check this check box.
You can provide notes concerning this run. These notes will be included on the Transactions tab for the transaction created when the job is run.
To complete the run request, click Finish.
The Complete page of the Run Automated Upgrade Job process displays.
If you are running in validation mode, then the Complete page includes the identifier of the event triggered by the request.
If you are running in execution mode, then the event information is not yet available. The Complete page displays the date and time when the job will next run.