Migrating from Opalis – Identifying activities that have changed in Orchestrator

  • Article

Hi everyone

As we have previously indicated, there are some changes in the Standard Activities (what were referred to as Foundation Activities in the Opalis product) with the Orchestrator release. 

This raises the question for customers who are migrating from Opalis to Orchestrator for a way to identify which Opalis workflows contain objects that are deprecated runbook activities in Orchestrator. 

The following SQL query can be run on against either the Opalis 6.3 database or the Orchestrator database.  It will identify the Opalis 6.3 workflows that make use of objects no longer available in Orchestrator.  The query will return both the Opalis 6.3 workflow name as well as the name of the object in the workflow.  Any workflow identified by this query will need to be updated after it has been imported into Orchestrator to remove the reference to the deprecated object.

 Select 
 policies.[Name] as [Policy Name], 
 objects.[Name] as [Object Name] 
From 
 [Objects] objects join 
 [Policies] policies 
 on objects.[ParentID]=policies.[UniqueID] 
Where 
 objects.objecttype = '2081B459-88D2-464A-9F3D-27D2B7A64C5E' or 
 objects.objecttype = '6F0FA888-1969-4010-95BC-C0468FA6E8A0' or 
 objects.objecttype = '8740DB49-5EE2-4398-9AD1-21315B8D2536' or 
 objects.objecttype = '19253CC6-2A14-432A-B4D8-5C3F778B69B0' or 
 objects.objecttype = '9AB62470-8541-44BD-BC2A-5C3409C56CAA' or 
 objects.objecttype = '292941F8-6BA7-4EC2-9BC0-3B5F96AB9790' or 
 objects.objecttype = '98AF4CBD-E30E-4890-9D26-404FE24727D7' or 
 objects.objecttype = '2409285A-9F7E-4E04-BFB9-A617C2E5FA61' or 
 objects.objecttype = 'B40FDFBD-6E5F-44F0-9AA6-6469B0A35710' or 
 objects.objecttype = '9DAF8E78-25EB-425F-A5EF-338C2940B409' or 
 objects.objecttype = 'B5381CDD-8498-4603-884D-1800699462AC' or 
 objects.objecttype = 'FCA29108-14F3-429A-ADD4-BE24EA5E4A3E' or 
 objects.objecttype = '7FB85E1D-D3C5-41DA-ACF4-E1A8396A9DA7' or 
 objects.objecttype = '3CCE9C71-51F0-4595-927F-61D84F2F1B5D' or 
 objects.objecttype = '96769C11-11F5-4645-B213-9EC7A3F244DB' or 
 objects.objecttype = '6FED5A55-A652-455B-88E2-9992E7C97E9A' or 
 objects.objecttype = '9C1DF967-5A50-4C4E-9906-C331208A3801' or 
 objects.objecttype = 'B40FDFBD-6E5F-44F0-9AA6-6469B0A35710' or 
 objects.objecttype = '829A951B-AAE9-4FBF-A6FD-92FA697EEA91' or 
 objects.objecttype = '1728D617-ACA9-4C96-ADD1-0E0B61104A9E' or 
 objects.objecttype = 'F3D1E70B-D389-49AD-A002-D332604BE87A' or 
 objects.objecttype = '2D907D60-9C25-4A1C-B950-A31EB9C9DB5F' or 
 objects.objecttype = '6A083024-C7B3-474F-A53F-075CD2F2AC0F' or 
 objects.objecttype = '4E6481A1-6233-4C82-879F-D0A0EDCF2802' or 
 objects.objecttype = 'BC49578F-171B-4776-86E2-664A5377B178'

The migration guide on the Orchestrator TechNet Library is currently being updated with this information.

We hope this helps you migration testing and planning!

Adam

Adam Adam Hall Senior Technical Product Manager Orchestrator white blog

Send me an e-mail     Follow me on Twitter Connect with me on LinkedIn