Switch between skills and skill versions

This overview compares how to switch between skills and skill versions depending on how users access the skill. For detailed procedures, follow the links in the table.

Case	API or connectors	Process skill
Update the Classification/Document skill version	Publish the skill. Users are switched to the new version automatically. Edit a skill that is available in production	Publish the skill, update the Process skill’s reference, and then publish the Process skill. Edit a skill after documents have been accumulated
Roll back to the previous version	Delete the latest skill version. Users are switched to the previous version automatically. Roll a skill back to a previous version	Either delete the latest Process skill version, or create a new Process skill version that references the older Classification/Document skill version. Roll back or switch strategies
Switch to another Classification/Document skill	Get the new skill’s ID (via Vantage API or from the end of the URL shown when editing the skill in the Skill Editor), and then replace the old ID in your API calls or connector settings.	Edit the Process skill’s Classify or Extract activity to reference the new skill, and then publish the Process skill. Users are switched to the new Process skill version automatically and access the new referenced skill through it.
Transfer a new skill version to another environment	Publish the skill, export its latest version, switch environments, and import it under the same name with Create new version. The skill ID does not change across environments, so API calls and connector settings need no updates. Continued development using separate environments	Either transfer just the skill and update the Process skill’s reference in the target environment, or transfer the Process skill with its embedded skills. Either path ends with publishing the Process skill in the target environment. Continued development using separate environments

​Related topics

Related topics