AWS deadline-cloud: Document Unreal Engine support for pre-GUI submission hooks
Summary
Clarifies that the Unreal Engine submitter, unlike other in-application (DCC) submitters, supports pre-GUI hooks, explains where those hooks run (DeadlineCloudRenderJob data asset editor and MRQ Preset Overrides panel), notes that hooks modify only the in-memory panel and do not save the .uasset, and updates the submission-method support list.
Security assessment
The changed line purely describes which submission hook phases run for which submitter (Unreal Engine vs. other DCC submitters). It is functional/behavioral documentation about hook execution timing, with no mention of credentials, permissions, encryption, or any weakness, so there is no security implication.
Evidence
+In-application (DCC) submitters such as Maya, Nuke, or Blender run environment hooks for the pre-submission and post-submission phases only. The Unreal Engine submitter also supports pre-GUI hooks. For more information, see Pre-GUI hooks.
Diff
diff --git a/deadline-cloud/latest/developerguide/submission-hooks.md b/deadline-cloud/latest/developerguide/submission-hooks.md index 8b30001..317c199 100644 --- a//deadline-cloud/latest/developerguide/submission-hooks.md +++ b//deadline-cloud/latest/developerguide/submission-hooks.md @@ -28 +28 @@ Both sources can be active at the same time. When both are present, environment -In-application (DCC) submitters such as Maya, Nuke, or Blender run environment hooks for the pre-submission and post-submission phases only. The pre-GUI phase does not apply to DCC submitters. For more information, see Pre-GUI hooks. +In-application (DCC) submitters such as Maya, Nuke, or Blender run environment hooks for the pre-submission and post-submission phases only. The Unreal Engine submitter also supports pre-GUI hooks. For more information, see Pre-GUI hooks. @@ -40 +40 @@ Pre-GUI hooks run before the submission dialog opens. You can use pre-GUI hooks -Pre-GUI hooks run only with the standalone GUI submitter (`deadline bundle gui-submit`). They do not run in in-application (DCC) submitters such as Maya, Nuke, or Blender, because those applications build their submission dialog directly and do not invoke the pre-GUI phase. Pre-GUI hooks also do not apply to CLI submission (`deadline bundle submit`), which has no GUI phase. Pre-submission and post-submission hooks work across all submission methods. +Pre-GUI hooks run with the standalone GUI submitter (`deadline bundle gui-submit`) and the Unreal Engine submitter. They do not run with CLI submission (`deadline bundle submit`) or other in-application submitters such as Maya, Nuke, or Blender. Pre-submission and post-submission hooks work across all submission methods. @@ -94,0 +95,15 @@ CLI-supplied `--parameter` values take precedence over hook-supplied `parameters +#### Submission hooks in Unreal Engine + +The Unreal Engine submitter has no Qt submission dialog. Its pre-GUI hooks run when Unreal Engine builds a job's C++ Details panel in either of these locations: + + * The `DeadlineCloudRenderJob` data asset editor. + + * The **Movie Render Queue** , **Deadline Cloud** , **Preset Overrides** panel. + + + + +**Render (Remote)** submits every queued MRQ job. Open the Details panel for each job that a pre-GUI hook must modify before you submit the queue. + +A pre-GUI hook changes only the in-memory panel and does not save the `.uasset` file. The hook runs again the first time you open a saved job's panel in a new Unreal Editor session. + @@ -399 +414,3 @@ Hooks work with the following submission methods: - * In-application (DCC) submitters – Pre-submission and post-submission hooks run. DCC submitters do not invoke the pre-GUI phase. + * In-application (DCC) submitters other than Unreal Engine – Pre-submission and post-submission hooks run. These submitters do not invoke the pre-GUI phase. + + * Unreal Engine submitter – All phases run. Pre-GUI hooks run when Unreal Engine builds a Deadline Cloud job's C++ Details panel.