<h2>Service Catalog Item Designer deprecation helper tool</h2><br/><div style="overflow-x:auto"><p style="margin: 0in; font-family: Calibri; font-size: 11.0pt;"><span style="font-family: verdana, geneva;">We will end support for Item Designer in March 2024 and customers are encouraged to migrate fulfillment steps of catalog items to Catalog Builder. </span></p> <p style="margin: 0in; font-family: Calibri; font-size: 11.0pt;"> </p> <p style="margin: 0in; font-family: Calibri; font-size: 11.0pt;"><span style="font-family: verdana, geneva;">We understand that this change may have an impact on your workflow, which is why we have developed a script that will allow you to migrate the fulfillment steps of your catalog items from Item Designer to Catalog Builder compatible Service Fulfillment Steps. The script is attached as a <a href="/sys_attachment.do?sys_id=5d40419f473206d0f64de825126d4392">text document</a> to this article. When run in an instance, this script will create approval and task steps in the scope of the item, and migrate only the active definitions. Please review the considerations below when running the migration script:</span></p> <p style="margin: 0in; font-family: Calibri; font-size: 11.0pt;"> </p> <ul style="list-style-position: inside;"><li style="font-family: Calibri; font-size: 11pt;"><span style="font-family: verdana, geneva;">Approvals are created as custom approval service fulfillment types with an approval type of "All Approve". </span></li><li style="font-family: Calibri; font-size: 11pt;"><span style="font-family: verdana, geneva;">Task steps are created as task service fulfillment types. </span></li><li style="font-family: Calibri; font-size: 11pt;"><span style="font-family: verdana, geneva;">Approvals or tasks having the same order are created as parallel steps under one stage. </span></li><li style="font-family: Calibri; font-size: 11pt;"><span style="font-family: verdana, geneva;">For each item that is successfully migrated, a log will be printed to indicate that the approvals and tasks have been migrated successfully.</span></li><li style="font-family: Calibri; font-size: 11pt;"><span style="font-family: verdana, geneva;">The migration script will not migrate approvals of the type Predefined Approval of the type script, or tasks that have Predefined assignment with an assignment type of Scripted assignment. </span> <ul style="list-style-position: inside;"><li style="font-family: Calibri; font-size: 11pt;"><span style="font-family: verdana, geneva;">For items containing such steps, the complete migration will not be successful, and a log will be printed to indicate this. You'd have to do the migration manually for these steps.</span></li></ul> </li><li style="font-family: Calibri; font-size: 11pt;"><span style="font-family: verdana, geneva;">Please note that the script will migrate the fulfillment steps of all the catalog items created using Item Designer. If for some reason you want to go back to the previous behavior, you can remove the Step based request fulfillment as the process engine for Flow and add the relevant Workflow for Item Designer items in the catalog item.</span></li></ul> <p style="margin: 0in; font-family: Calibri; font-size: 11.0pt;"> </p> <p style="margin: 0in; font-family: Calibri; font-size: 11.0pt;"><span style="font-family: verdana, geneva;">We recommend that you migrate your custom items to Catalog Builder compatible Service Fulfillment Steps as soon as possible. This will ensure that your items are fully compatible with our latest product offerings and will help you take advantage of the latest features.</span></p></div>