Modern business process is essential for transforming organizational productivity in Microsoft 365. Since the release of SharePoint workflows, Microsoft has evolved workflow orchestration to not only...
Published Jul 06, 2020
Version 1.0
Blog Post
Most of the comments here are based on the actual functionality of SP2010 workflows - which as far as I can see is not fully duplicated in PA for Sharepoint permissions in the same manner as a SP2010 workflow.
Even if the functionality were duplicated - what about the UI for existing "classic" applications?
Many apps use the "Classic mode" Ribbon to trigger 2010 workflows.
As an example:
Imagine a FOUR or more level approval cycle
- A user creates an item "DRAFT" and saves it.
- On save the draft changes security so that only that user can see the item (all approvers are unaware of the item)
- When viewing the item, the "EDIT" and "SEND TO" ribbon buttons are visible in their ribbon.
- When they are ready they click the "SEND TO" button on the ribbon and the item goes to the first level approver. A 2010 workflow triggers and changes permissions on the item.
- The item is locked from editing by the original creator
- If the original CREATOR looks at the item then they see no ribbon actions.
- If the first level approver looks at the item they see "EDIT", "REJECT" and "APPROVE AND SEND ON" buttons. At this point the second level approver is totally unaware of anything so will not even see the item.
Just an example - but all the users are familiar with triggering workflows from buttons in the ribbon.
What impact will forcing PA have on the existing UI's?