Fixed bug where relaunching a workflow job from the details view was throwing a 404. Also fixed bug where relaunching a workflow from the details view was not redirecting the user to the new details view.

This commit is contained in:
Michael Abashian 2017-01-11 20:43:43 -05:00
parent 258405aefe
commit 83a6b8ba53
2 changed files with 4 additions and 3 deletions

View File

@ -120,7 +120,7 @@ export default
Rest.post(job_launch_data)
.success(function(data) {
Wait('stop');
var job = data.job || data.system_job || data.project_update || data.inventory_update || data.ad_hoc_command || data.workflow_job;
var job = data.job || data.system_job || data.project_update || data.inventory_update || data.ad_hoc_command;
if($rootScope.portalMode===false && Empty(data.system_job) || (base === 'home')){
// use $state.go with reload: true option to re-instantiate sockets in
@ -131,7 +131,8 @@ export default
if(_.has(data, 'job')) {
goToJobDetails('jobDetail');
}
else if(_.has(data, 'workflow_job')) {
else if(data.type && data.type === 'workflow_job') {
job = data.id;
goToJobDetails('workflowResults');
}
else if(_.has(data, 'ad_hoc_command')) {

View File

@ -126,7 +126,7 @@ export default ['$q', 'Prompt', '$filter', 'Wait', 'Rest', '$state', 'ProcessErr
},
relaunchJob: function(scope) {
InitiatePlaybookRun({ scope: scope, id: scope.workflow.id,
relaunch: true, job_type: 'workflow_job_template' });
relaunch: true, job_type: 'workflow_job' });
}
};
return val;