Sharepoint Designer Discontinuation - software to modify existing workflows Announcing the arrival of Valued Associate #679: Cesar Manara Unicorn Meta Zoo #1: Why another podcast?SharePoint Designer 2013 ReplacementiOS: implement SharePoint Designer (Workflows only) functionalityCannot modify page layouts in SharePoint designerWorkflows Dissapearing SharePoint Designer 2010Designer based workflows issueSharePoint Designer: Append Changes to Existing Text in EmailWorkflows not opening in SharePoint DesignerHow to modify the list form in SharePoint 2013 designer?SharePoint Designer Workflows - stuck or stopped runningDeleting old workflows from SharePoint DesignerSharePoint Designer support for sharepoint online sites

Is it acceptable to use working hours to read general interest books?

Check if a string is entirely made of the same substring

Has a Nobel Peace laureate ever been accused of war crimes?

What *exactly* is electrical current, voltage, and resistance?

Double-nominative constructions and “von”

How do I prove this combinatorial identity

What was Apollo 13's "Little Jolt" after MECO?

Is Electric Central Heating worth it if using Solar Panels?

Why do distances seem to matter in the Foundation world?

What is purpose of DB Browser(dbbrowser.aspx) under admin tool?

Where was the County of Thurn und Taxis located?

How to keep bees out of canned beverages?

Which big number is bigger?

I preordered a game on my Xbox while on the home screen of my friend's account. Which of us owns the game?

Could moose/elk survive in the Amazon forest?

Bayes factor vs P value

"My boss was furious with me and I have been fired" vs. "My boss was furious with me and I was fired"

What is the term for a person whose job is to place products on shelves in stores?

"Whatever a Russian does, they end up making the Kalashnikov gun"? Are there any similar proverbs in English?

Negative Resistance

Obeylines and gappto from etoolbox

What's the difference between using dependency injection with a container and using a service locator?

Retract an already submitted recommendation letter (written for an undergrad student)

How much cash can I safely carry into the USA and avoid civil forfeiture?



Sharepoint Designer Discontinuation - software to modify existing workflows



Announcing the arrival of Valued Associate #679: Cesar Manara
Unicorn Meta Zoo #1: Why another podcast?SharePoint Designer 2013 ReplacementiOS: implement SharePoint Designer (Workflows only) functionalityCannot modify page layouts in SharePoint designerWorkflows Dissapearing SharePoint Designer 2010Designer based workflows issueSharePoint Designer: Append Changes to Existing Text in EmailWorkflows not opening in SharePoint DesignerHow to modify the list form in SharePoint 2013 designer?SharePoint Designer Workflows - stuck or stopped runningDeleting old workflows from SharePoint DesignerSharePoint Designer support for sharepoint online sites



.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;








2















I am looking for alternatives to Sharepoint Designer, I also discovered that it is due to be discontinued. I use SPD primarily for Workflows (using SP2010 workflows and a handful of SP2013 workflows).



I found a useful previous post by Mohamed El-Qassas on our beloved SPSE, but I cannot quite discern what will be compatible with my own situation.



Some of the solutions I've seen are for SP Online, but I am using Sharepoint 2013, I have a lot of existing workflows that I'd like to be able to continue to use & maintain with the new software. Switching to a new 'platform' is a daunting prospect given how much work has gone in to setting up the workflow infrastructure and fairly complex, custom workflows.



Would PowerApps or MS Flow be able to modify existing SP 2010 & 2013 workflows?










share|improve this question




























    2















    I am looking for alternatives to Sharepoint Designer, I also discovered that it is due to be discontinued. I use SPD primarily for Workflows (using SP2010 workflows and a handful of SP2013 workflows).



    I found a useful previous post by Mohamed El-Qassas on our beloved SPSE, but I cannot quite discern what will be compatible with my own situation.



    Some of the solutions I've seen are for SP Online, but I am using Sharepoint 2013, I have a lot of existing workflows that I'd like to be able to continue to use & maintain with the new software. Switching to a new 'platform' is a daunting prospect given how much work has gone in to setting up the workflow infrastructure and fairly complex, custom workflows.



    Would PowerApps or MS Flow be able to modify existing SP 2010 & 2013 workflows?










    share|improve this question
























      2












      2








      2








      I am looking for alternatives to Sharepoint Designer, I also discovered that it is due to be discontinued. I use SPD primarily for Workflows (using SP2010 workflows and a handful of SP2013 workflows).



      I found a useful previous post by Mohamed El-Qassas on our beloved SPSE, but I cannot quite discern what will be compatible with my own situation.



      Some of the solutions I've seen are for SP Online, but I am using Sharepoint 2013, I have a lot of existing workflows that I'd like to be able to continue to use & maintain with the new software. Switching to a new 'platform' is a daunting prospect given how much work has gone in to setting up the workflow infrastructure and fairly complex, custom workflows.



      Would PowerApps or MS Flow be able to modify existing SP 2010 & 2013 workflows?










      share|improve this question














      I am looking for alternatives to Sharepoint Designer, I also discovered that it is due to be discontinued. I use SPD primarily for Workflows (using SP2010 workflows and a handful of SP2013 workflows).



      I found a useful previous post by Mohamed El-Qassas on our beloved SPSE, but I cannot quite discern what will be compatible with my own situation.



      Some of the solutions I've seen are for SP Online, but I am using Sharepoint 2013, I have a lot of existing workflows that I'd like to be able to continue to use & maintain with the new software. Switching to a new 'platform' is a daunting prospect given how much work has gone in to setting up the workflow infrastructure and fairly complex, custom workflows.



      Would PowerApps or MS Flow be able to modify existing SP 2010 & 2013 workflows?







      2013 sharepoint-designer flow powerapp on-premise






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked 5 hours ago









      TallyTally

      1,5662630




      1,5662630




















          1 Answer
          1






          active

          oldest

          votes


















          4














          SPD is still supported with SharePoint 2016. Mainstream support ends in 2021, and extended support ends in 2026. So one answer is to keep maintaining existing workflows in 2013, and look into the new tools for new solutions. (if you're concerned about the 2021 date, then you should already be concerned that the end of mainstream support for 2013 has already passed).



          Can PowerApps and Flow modify existing 2010/2013 workflows? Not at all. These are new tools with new capabilities, and there is no migration path, compatibility, etc., of any kind.



          Also, while MS will tell you that you can simply rebuild your infopath and spd workflows using these new tools, my experience is that the existing processes will often need to be redesigned to work well with the new tools.



          I'd recommend to begin planning how to migrate to SharePoint 2016/2019/online, if that hasn't happened already. I'd also suggest that you begin ramping up on PowerApps and Flow, as these tools are not necessarily intuitive, and can be quite challenging to work with, especially when attempting to recreate complex SPD solutions. Once you've built out a couple new forms/workflow (using the available connector to connect to On-prem sharepoint servers), then start creating the inventory of existing workflows/forms that will need to be rebuilt.



          Good luck!!






          share|improve this answer























            Your Answer








            StackExchange.ready(function()
            var channelOptions =
            tags: "".split(" "),
            id: "232"
            ;
            initTagRenderer("".split(" "), "".split(" "), channelOptions);

            StackExchange.using("externalEditor", function()
            // Have to fire editor after snippets, if snippets enabled
            if (StackExchange.settings.snippets.snippetsEnabled)
            StackExchange.using("snippets", function()
            createEditor();
            );

            else
            createEditor();

            );

            function createEditor()
            StackExchange.prepareEditor(
            heartbeatType: 'answer',
            autoActivateHeartbeat: false,
            convertImagesToLinks: false,
            noModals: true,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: null,
            bindNavPrevention: true,
            postfix: "",
            imageUploader:
            brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
            contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
            allowUrls: true
            ,
            onDemand: true,
            discardSelector: ".discard-answer"
            ,immediatelyShowMarkdownHelp:true
            );



            );













            draft saved

            draft discarded


















            StackExchange.ready(
            function ()
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsharepoint.stackexchange.com%2fquestions%2f262480%2fsharepoint-designer-discontinuation-software-to-modify-existing-workflows%23new-answer', 'question_page');

            );

            Post as a guest















            Required, but never shown

























            1 Answer
            1






            active

            oldest

            votes








            1 Answer
            1






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes









            4














            SPD is still supported with SharePoint 2016. Mainstream support ends in 2021, and extended support ends in 2026. So one answer is to keep maintaining existing workflows in 2013, and look into the new tools for new solutions. (if you're concerned about the 2021 date, then you should already be concerned that the end of mainstream support for 2013 has already passed).



            Can PowerApps and Flow modify existing 2010/2013 workflows? Not at all. These are new tools with new capabilities, and there is no migration path, compatibility, etc., of any kind.



            Also, while MS will tell you that you can simply rebuild your infopath and spd workflows using these new tools, my experience is that the existing processes will often need to be redesigned to work well with the new tools.



            I'd recommend to begin planning how to migrate to SharePoint 2016/2019/online, if that hasn't happened already. I'd also suggest that you begin ramping up on PowerApps and Flow, as these tools are not necessarily intuitive, and can be quite challenging to work with, especially when attempting to recreate complex SPD solutions. Once you've built out a couple new forms/workflow (using the available connector to connect to On-prem sharepoint servers), then start creating the inventory of existing workflows/forms that will need to be rebuilt.



            Good luck!!






            share|improve this answer



























              4














              SPD is still supported with SharePoint 2016. Mainstream support ends in 2021, and extended support ends in 2026. So one answer is to keep maintaining existing workflows in 2013, and look into the new tools for new solutions. (if you're concerned about the 2021 date, then you should already be concerned that the end of mainstream support for 2013 has already passed).



              Can PowerApps and Flow modify existing 2010/2013 workflows? Not at all. These are new tools with new capabilities, and there is no migration path, compatibility, etc., of any kind.



              Also, while MS will tell you that you can simply rebuild your infopath and spd workflows using these new tools, my experience is that the existing processes will often need to be redesigned to work well with the new tools.



              I'd recommend to begin planning how to migrate to SharePoint 2016/2019/online, if that hasn't happened already. I'd also suggest that you begin ramping up on PowerApps and Flow, as these tools are not necessarily intuitive, and can be quite challenging to work with, especially when attempting to recreate complex SPD solutions. Once you've built out a couple new forms/workflow (using the available connector to connect to On-prem sharepoint servers), then start creating the inventory of existing workflows/forms that will need to be rebuilt.



              Good luck!!






              share|improve this answer

























                4












                4








                4







                SPD is still supported with SharePoint 2016. Mainstream support ends in 2021, and extended support ends in 2026. So one answer is to keep maintaining existing workflows in 2013, and look into the new tools for new solutions. (if you're concerned about the 2021 date, then you should already be concerned that the end of mainstream support for 2013 has already passed).



                Can PowerApps and Flow modify existing 2010/2013 workflows? Not at all. These are new tools with new capabilities, and there is no migration path, compatibility, etc., of any kind.



                Also, while MS will tell you that you can simply rebuild your infopath and spd workflows using these new tools, my experience is that the existing processes will often need to be redesigned to work well with the new tools.



                I'd recommend to begin planning how to migrate to SharePoint 2016/2019/online, if that hasn't happened already. I'd also suggest that you begin ramping up on PowerApps and Flow, as these tools are not necessarily intuitive, and can be quite challenging to work with, especially when attempting to recreate complex SPD solutions. Once you've built out a couple new forms/workflow (using the available connector to connect to On-prem sharepoint servers), then start creating the inventory of existing workflows/forms that will need to be rebuilt.



                Good luck!!






                share|improve this answer













                SPD is still supported with SharePoint 2016. Mainstream support ends in 2021, and extended support ends in 2026. So one answer is to keep maintaining existing workflows in 2013, and look into the new tools for new solutions. (if you're concerned about the 2021 date, then you should already be concerned that the end of mainstream support for 2013 has already passed).



                Can PowerApps and Flow modify existing 2010/2013 workflows? Not at all. These are new tools with new capabilities, and there is no migration path, compatibility, etc., of any kind.



                Also, while MS will tell you that you can simply rebuild your infopath and spd workflows using these new tools, my experience is that the existing processes will often need to be redesigned to work well with the new tools.



                I'd recommend to begin planning how to migrate to SharePoint 2016/2019/online, if that hasn't happened already. I'd also suggest that you begin ramping up on PowerApps and Flow, as these tools are not necessarily intuitive, and can be quite challenging to work with, especially when attempting to recreate complex SPD solutions. Once you've built out a couple new forms/workflow (using the available connector to connect to On-prem sharepoint servers), then start creating the inventory of existing workflows/forms that will need to be rebuilt.



                Good luck!!







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered 4 hours ago









                Mike2500Mike2500

                6,06631532




                6,06631532



























                    draft saved

                    draft discarded
















































                    Thanks for contributing an answer to SharePoint Stack Exchange!


                    • Please be sure to answer the question. Provide details and share your research!

                    But avoid


                    • Asking for help, clarification, or responding to other answers.

                    • Making statements based on opinion; back them up with references or personal experience.

                    To learn more, see our tips on writing great answers.




                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function ()
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsharepoint.stackexchange.com%2fquestions%2f262480%2fsharepoint-designer-discontinuation-software-to-modify-existing-workflows%23new-answer', 'question_page');

                    );

                    Post as a guest















                    Required, but never shown





















































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown

































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown







                    Popular posts from this blog

                    ParseJSON using SSJSUsing AMPscript with SSJS ActivitiesHow to resubscribe a user in Marketing cloud using SSJS?Pulling Subscriber Status from Lists using SSJSRetrieving Emails using SSJSProblem in updating DE using SSJSUsing SSJS to send single email in Marketing CloudError adding EmailSendDefinition using SSJS

                    Кампала Садржај Географија Географија Историја Становништво Привреда Партнерски градови Референце Спољашње везе Мени за навигацију0°11′ СГШ; 32°20′ ИГД / 0.18° СГШ; 32.34° ИГД / 0.18; 32.340°11′ СГШ; 32°20′ ИГД / 0.18° СГШ; 32.34° ИГД / 0.18; 32.34МедијиПодациЗванични веб-сајту

                    19. јануар Садржај Догађаји Рођења Смрти Празници и дани сећања Види још Референце Мени за навигацијуу