Bug: Task object personality failure

[Bob_Zimmerman]

When you run 'show tasks' with 'details-level full', each task has a uid and a task-id, which are different:

[Expert@labStandalone:0]# mgmt_cli -r true show tasks --format json limit 1 details-level full
{
  "tasks" : [ {
    "uid" : "e3a07b41-cb04-4df7-aaf1-310fba048cf6",
    "type" : "task",
    "domain" : {...},
    "task-id" : "924fb037-9b19-4e8d-8290-c2173e213dce",
    "task-name" : "Policy installation - Standard",
...

'show object uid ____' works for the UUID in the task object:

[Expert@labStandalone:0]# mgmt_cli -r true show object uid "e3a07b41-cb04-4df7-aaf1-310fba048cf6" --format json
{
  "object" : {
    "uid" : "e3a07b41-cb04-4df7-aaf1-310fba048cf6",
    "type" : "task",
    "domain" : {
      "uid" : "41e821a0-3720-11e3-aa6e-0800200c9fde",
      "name" : "SMC User",
      "domain-type" : "domain"
    }
  }
}

Out of curiosity, I tried adding 'details-level full', and got an error:

[Expert@labStandalone:0]# mgmt_cli -r true show object uid "e3a07b41-cb04-4df7-aaf1-310fba048cf6" --format json details-level full
{
  "code" : "generic_error",
  "message" : "Runtime error: com.checkpoint.management.coresvc.ngm_api.task_notifications.TaskNotification incompatible with java.util.Collection"
}

 This doesn't affect me right now, it's just something I found odd, and thought was worth reporting.

Edited to add: Forgot to include my version. I'm on R80.40 jumbo 87. Updating to 91 later tonight, but I doubt it will change the behavior.

[PhoneBoy]

@Omer_Kleinstern 

[Or_Soffer]

Hi,

Sorry, tasks are not supported in show-object API.

[Bob_Zimmerman]

I figured, but it should give consistent results, and ideally that result should be a specific error rather than an internal Java error propagated upwards.