Craig: can you log a ticket for the first issue? I've occasionally seen that in the demo environment, but we should be able to troubleshoot it. (Sonali Kshirsagar was looking at it with me).
As for the second, I believe it creates a new NSH Script Job once you complete the operation. I'll touch base with Matthew Salerno about recommended behavior. (wouldn't be a bad idea to open a ticket for this one either)
Will do on the first issue. It doesn't seem to affect anything, other than the execute option is grayed out on the operations home page. To get it to run I need to open the result and use the Execute button.
You are correct, sir, on the second issue. The result of the create operation in the portal is an NSH job in the 'Jobs' workspace. It's almost like it 'forgets' that the new job was not based on an existing job and so it disallows changes.
The first issue is kind of known issue where if we change the underline job from BSA the operation becomes orphan and cannot be synced.
If its a demo environment then we can remove these stale entries from DCAPORTALOPERATION table and avoid them showing on the UI.
>> If its a demo environment
Thanks for the information, Sonali. Unfortunately, this is in our production environment.
Case 00264003 has been opened for the portal job status showing an operation is running after being canceled in the BSA console.