NOTE: Crow Canyon will host a webinar with MVP Joel Oleson on July 21st to give guidance on the SharePoint 2010 Workflow retirement and moving off SharePoint 2010 Workflows. Register here: Making the Best Decision: Migrate or Upgrade SharePoint 2010 Workflows?
– – – – – – – – – – – –
Last week, Microsoft announced it’s SharePoint 2010 Retirement, that it will end the ability to run SharePoint 2010 workflows on Microsoft Office 365 starting in November this year, causing much consternation to people who use these workflows for important business processes.
Microsoft’s intent is to push customers to use its Power Automate tool, but commentators pointed out that this lacks (or makes it difficult to implement) certain critical features.
Two areas in particular were mentioned: setting item permissions and dynamic approval processes. As one commentator said:
“Both Power Automate and SPD [SharePoint Designer] 2013 workflows lack the ability to change the permissions on a SharePoint list item. Only SPD 2010 workflow has this ability. This is a critical step in many workflows.”
Fortunately, our NITRO Studio, which runs in Office 365 as well as in SharePoint on-premises, has both of these abilities and should be seriously considered as a pathway to moving off SharePoint 2010 workflows.
Setting Item-level Permissions
Setting item-level permissions on a SharePoint list item is a part of many workflows. For example, a user submits a request, and then needs to be blocked from making any further changes after submission. Item-level permissions enforce this security.
NITRO Studio workflows have this capability built-in. Simply add NITRO’s “Manage Permissions” action in the workflow at whatever point it is needed. Item-level permissions can be turned on, off, revised, and modified per user or per group, and based on any number of conditions.
NITRO Workflows have enough flexibility that they should be able to meet any item-level permission scenario that is needed. Permissions can be set on the current item or on other items in the same or different list. For example, say there is an action or approval in one list. The NITRO workflow can then add, modify, or delete permissions on an item in the same list or another list.
And these run in Microsoft Office 365 using the NITRO Studio engine. There is no need for Power Automate, scripting, or SharePoint workflows.
Dynamic and Circular Approvals
Dynamic and circular approvals are also an inherent part of NITRO Workflows. Simple or complex approvals can be set up as needed. For advanced approvals, there can be any number of levels. Each level has its own conditions and parameters – who needs to approve, what conditions trigger that level, what happens after the approval takes place, what happens if the request is denied, etc.
Importantly, the actual approver at each level is not just a designated, hard-coded person or group. The approver can be determined based on dynamic conditions on the ticket. The name can be pulled from Active Directory, a column on the form, another list, or via a lookup, with that selection based on certain criteria as the request makes its way through the approval process.
The workflows can also handle more than just “approve or deny”. Other options can be added, such as “Send Back” or “Request Modifications”. Also, the approval can be reassigned.
For each stage, notifications by email or in Microsoft Teams can be set up so that everyone who needs to know is kept informed at each step of the process.
NITRO Studio as a SharePoint 2010 Workflow Replacement
To assist you with Microsoft’s Sharepoint 2010 Workflow retirement, Our NITRO Studio is already serving well as an InfoPath Replacement option. We have materials and resources as well as an eBook download on our InfoPath Replacement page. In the same way, NITRO can replace SharePoint 2010 workflows, as well as SharePoint 2013 ones, for that matter.
NITRO Studio comes with a wide-range of capabilities. Along with workflows, it has a forms designer, custom actions, email manager, and list formatting, as well as printing and reporting tools. It also comes with portals and user pages that allow end users to engage in friendly, intuitive interfaces. It runs in the classic or modern UI’s and is fully responsive and mobile-friendly.
We are also building chatbots for business process automation in Microsoft Teams. These should be considered as another option for moving off SharePoint 2010 workflows and giving your users some new, cool technology to use.
Crow Canyon Brings Over 20 Years of Experience Working With Microsoft Platforms
Crow Canyon Software has worked in the Microsoft collaboration space for over 20 years. We are a Preferred member of the Microsoft 365 Business Apps Partner Program. We realize that when the 800-lb gorilla moves, the cascading effects send us all scrambling. Over the years, we have built tools and applications to help our fellow Microsoft users get the most out of these collaboration platforms — and to be able to rapidly adapt to the many changes Microsoft makes.
In this case, we are here to help again. Take a look at NITRO Studio, ask us questions, challenge us with various scenarios. It is likely we can meet your requirements and facilitate your move off SharePoint 2010 workflows, as well as other legacy systems, to new, modern solutions. Contact us for info and a demo.
NOTE: Crow Canyon will host a webinar with MVP Joel Oleson on July 21st to give guidance on moving off SharePoint 2010 Workflows. Register here: Making the Best Decision: Migrate or Upgrade SharePoint 2010 Workflows?
– – – – – – – – – – – –
Last week, Microsoft announced that it will end the ability to run SharePoint 2010 workflows on Microsoft Office 365 starting in November this year, causing much consternation to people who use these workflows for important business processes.
Microsoft’s intent is to push customers to use its Power Automate tool, but commentators pointed out that this lacks (or makes it difficult to implement) certain critical features.
Two areas in particular were mentioned: setting item permissions and dynamic approval processes. As one commentator said:
“Both Power Automate and SPD [SharePoint Designer] 2013 workflows lack the ability to change the permissions on a SharePoint list item. Only SPD 2010 workflow has this ability. This is a critical step in many workflows.”
Fortunately, our NITRO Studio, which runs in Office 365 as well as in SharePoint on-premises, has both of these abilities and should be seriously considered as a pathway to moving off SharePoint 2010 workflows.
Setting Item-level Permissions
Setting item-level permissions on a SharePoint list item is a part of many workflows. For example, a user submits a request, and then needs to be blocked from making any further changes after submission. Item-level permissions enforce this security.
NITRO Studio workflows have this capability built-in. Simply add NITRO’s “Manage Permissions” action in the workflow at whatever point it is needed. Item-level permissions can be turned on, off, revised, and modified per user or per group, and based on any number of conditions.
NITRO Workflows have enough flexibility that they should be able to meet any item-level permission scenario that is needed. Permissions can be set on the current item or on other items in the same or different list. For example, say there is an action or approval in one list. The NITRO workflow can then add, modify, or delete permissions on an item in the same list or another list.
And these run in Microsoft Office 365 using the NITRO Studio engine. There is no need for Power Automate, scripting, or SharePoint workflows.
Dynamic and Circular Approvals
Dynamic and circular approvals are also an inherent part of NITRO Workflows. Simple or complex approvals can be set up as needed. For advanced approvals, there can be any number of levels. Each level has its own conditions and parameters – who needs to approve, what conditions trigger that level, what happens after the approval takes place, what happens if the request is denied, etc.
Importantly, the actual approver at each level is not just a designated, hard-coded person or group. The approver can be determined based on dynamic conditions on the ticket. The name can be pulled from Active Directory, a column on the form, another list, or via a lookup, with that selection based on certain criteria as the request makes its way through the approval process.
The workflows can also handle more than just “approve or deny”. Other options can be added, such as “Send Back” or “Request Modifications”. Also, the approval can be reassigned.
For each stage, notifications by email or in Microsoft Teams can be set up so that everyone who needs to know is kept informed at each step of the process.
NITRO Studio as a SharePoint 2010 Workflow Replacement
Our NITRO Studio is already serving well as an InfoPath Replacement option. We have materials and resources as well as an eBook download on our InfoPath Replacement page. In the same way, NITRO can replace SharePoint 2010 workflows, as well as SharePoint 2013 ones, for that matter.
NITRO Studio comes with a wide-range of capabilities. Along with workflows, it has a forms designer, custom actions, email manager, and list formatting, as well as printing and reporting tools. It also comes with portals and user pages that allow end users to engage in friendly, intuitive interfaces. It runs in the classic or modern UI’s and is fully responsive and mobile-friendly.
We are also building chatbots for business process automation in Microsoft Teams. These should be considered as another option for moving off SharePoint 2010 workflows and giving your users some new, cool technology to use.
Crow Canyon Brings Over 20 Years of Experience Working With Microsoft Platforms
Crow Canyon Software has worked in the Microsoft collaboration space for over 20 years. We are a Preferred member of the Microsoft 365 Business Apps Partner Program. We realize that when the 800-lb gorilla moves, the cascading effects send us all scrambling. Over the years, we have built tools and applications to help our fellow Microsoft users get the most out of these collaboration platforms — and to be able to rapidly adapt to the many changes Microsoft makes.
In this case, we are here to help again. Take a look at NITRO Studio, ask us questions, challenge us with various scenarios. It is likely we can meet your requirements and facilitate your move off SharePoint 2010 workflows, as well as other legacy systems, to new, modern solutions. Contact us for info and a demo.
