So finden Sie eine Migrationsjournalid

In dieser Anfrage haben wir mit der id 16nach Ergebnissen für die Migration gesucht.

<your_control_room_url>/v3/migration/16/results/list

Die Anfrage gab die id in jeder Objektliste als Journalid zurück. In diesem Beispiel gibt es zwei Journal-IDs, 30 und 31, für die Migrations-id 16.

{
    "page": {
        "offset": 0,
        "total": 2,
        "totalFilter": 2
    },
    "list": [
        {
            "sourceId": 12,
            "sourceName": "Dependency of IGN-23437.mbot",
            "sourcePath": "Automation Anywhere\\Bots\\My MetaBots\\Dependency of IGN-23437.mbot",
            "sourceType": "application/vnd.aa.mbot",
            "targetId": 0,
            "status": "FAILED",
            "reason": "The logic IGN-23437 has some commands or actions which are not yet supported for migration.",
            "selectedByUser": true,
            "userId": 9,
            "id": 30,
            "targetName": "",
            "targetPath": "",
            "targetType": ""
        },
        {
            "sourceId": 12,
            "sourceName": "Dependency of IGN-23437.mbot",
            "sourcePath": "Automation Anywhere\\Bots\\My MetaBots\\Dependency of IGN-23437.mbot",
            "sourceType": "application/vnd.aa.mbot",
            "targetId": 0,
            "status": "FAILED",
            "reason": "Migration of MetaBot failed.",
            "selectedByUser": false,
            "userId": 9,
            "id": 31,
            "targetName": "",
            "targetPath": "",
            "targetType": ""
        }
    ]
}

Sie können die Migrations-id und die Journal-id in einer Aktionszuordnungsanforderung verwenden.

<your_control_room_url>/v3/migration/16/journal/31/actionmappings/list