Kdtyjb

Is Diceware more secure than a long passphrase?

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

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

Is there really no use for MD5 anymore?

What makes accurate emulation of old systems a difficult task?

Suing a Police Officer Instead of the Police Department

Are there moral objections to a life motivated purely by money? How to sway a person from this lifestyle?

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

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

How do I reattach a shelf to the wall when it ripped out of the wall?

Unable to completely uninstall Zoom meeting app

Should the Product Owner dictate what info the UI needs to display?

Negative Resistance

What to do with someone that cheated their way through university and a PhD program?

Israeli soda type drink

Check if a string is entirely made of the same substring

Sharepoint Designer Discontinuation - software to modify existing workflows

Crossed out red box fitting tightly around image

Jaya, Venerated Firemage + Chandra's Pyrohelix = 4 damage among two targets?

A Paper Record is What I Hamper

Is this homebrew arcane communication device abusable?

Unknown code in script

How exactly does Hawking radiation decrease the mass of black holes?

Do I need to watch Ant-Man and the Wasp and Captain Marvel before watching Avengers: Endgame?

Sharepoint Designer Discontinuation - software to modify existing workflows

.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?

2013 sharepoint-designer flow powerapp on-premise

share|improve this question

asked 5 hours ago

TallyTally

1,5662630

add a comment | 

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?

2013 sharepoint-designer flow powerapp on-premise

share|improve this question

asked 5 hours ago

TallyTally

1,5662630

add a comment | 

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

asked 5 hours ago

TallyTally

1,5662630

share|improve this question

asked 5 hours ago

TallyTally

1,5662630

share|improve this question

asked 5 hours ago

TallyTally

1,5662630

asked 5 hours ago

TallyTally

1,5662630

asked 5 hours ago

TallyTally

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

answered 4 hours ago

Mike2500Mike2500

6,06631532

add a comment | 

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

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Sign up using Google

Sign up using Facebook

Sign up using Email and Password

Post as a guest

Name

Email

Required, but never shown

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

Name

Email

Required, but never shown

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

answered 4 hours ago

Mike2500Mike2500

6,06631532

add a comment | 

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

answered 4 hours ago

Mike2500Mike2500

6,06631532

add a comment | 

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

answered 4 hours ago

Mike2500Mike2500

6,06631532

share|improve this answer

answered 4 hours ago

Mike2500Mike2500

6,06631532

answered 4 hours ago

Mike2500Mike2500

6,06631532

answered 4 hours ago

Mike2500Mike2500

6,06631532