If I fire a sharepoint workflow manually, and it then runs automatically when a document is updated, will these run under the same permissions?
If its a declarative workflow then it will fire under the same permissions that the user has. For instance, let us assume you checked an item into a sharepoint list. A workflow might exist to send an email to the quality team that a new document was uploaded into the list. This workflow effectively uses the same permissions as the person who just kicked off that workflow.
Related
My team is embarking on moving from SharePoint 2010 to SharePoint 2016 with Nintex. They want to move content on an individual basis.
However, we also need to move running workflows and keep these intact.
What's the process of moving Nintex workflows and lists from SP2010 to a SharePoint 2016 environment?
Need to ensure the workflows/lists remain with the correct status
Thanks
You cannot move running workflows in SharePoint. The best suggestion is to pause or end the workflow, save the status and then kick them off after you move them. I recommend trying to complete whatever process is running before moving that content or workflow. This means scheduling the migration around business processes or informing your users that SharePoint will be down for a period of time. You can also copy the workflow and list over to the new site and have users start using that one while you wind down the old site. A tool like Sharegate is good for this type of stuff.
I wrote a support ticket system. Part of the ticket submission process allows the user to attach files. Once files are attached, the software creates a folder with the ticket ID number as the folder name, and stores the attachments there.
Each time the ticket is loaded, the contents of that folder are displayed in a listbox where they can be modified, added to or deleted, or opened.
The reason I did this was so that the attachment folders were easily accessible, even if the user was not using the software. This way they could send someone who doesnt have access to the software a link to the attachment folder.
The support ticket system is stored in an Access database, and runs out of a stand-alone Windows Form application.
Is this a bad practice? Will this lag the system out eventually? The software will be run off of a share drive, and the folders will be stored there as well.
I do not anticipate more than 60 users ever using this software.
I do not anticipate more than a few dozen requests per week, and requests could be archived once they were resolved.
I have created retention policy in SP2010 for Library and Document as folder based with some rules, also set information management policy and Expiration policy Timer job as in one after another running sequence, these all working fine for "Move in Recycle bin" option, but its not working for "Transfer To another Location" option, where I have already created the location as Drop off library using the Web service URL from Submission point.
If I am Sending the Document manual as "Send To " option its moving the document to Drop off library properly, but By Running the Above mentioned timer job , Documents are not moving to document even the Defined retention stage is already accorded.
and the "Compliance details" displaying status as Completed without moving the document and no error logging for same case.
Please guide me where If I am missing some thing in process...
Is this Drop off library located in the same site? If so this will not work because according to Microsoft, It was as per design. If you try to move documents to a different location using Retention policy, you have to move it a library in a different site collection. Preferably ‘Records center‘ site collection. Main idea of Microsoft is to have one Archival or Records center site collection for the whole organization.
So, if you are trying to move documents after expiration to a library in same site or site collection, you can use a workaround to start a workflow on expiration date which moves the document to archival library.
Hope this helps. Source
I have some issues with the Plone 4.3.1 permission settings. But I have come long way with the existing documentation and Aspelli's book. But I cannot figure out why I am unable to create any object in a folder, even as Site Administrator, after setting up a workflow-state that grants permissions to a specific user role.
The workflow-state is called "Show_External" and the permissions that are set through the Permissions tab of the workflow state are as follows:
Permission Acquire Site Admin Ext_Supplier
Access content information - X X
List folder contents - X X
Modify portal content - X X
View - X X
I do not want to "Acquire" any permissions because the new role is for an external supplier that has no business with anything else on this particular site.
The result - much against what I expected - is that no one can create any object. The option is shown in the interface, but any attempt results in Error Please correct the indicated errors.. No errors are indicated however.
What I can do is make the objects (folders and files) in another folder and then copy paste them to the folder that is set in the workflow-state. Stranger still, once I copy the folder as a subfolder to the External Supplier folder a can add files through QuickUpload, but not by selecting "Add file".
What am I missing in my understanding of the permissions?
You likely ran into a bug, which was fixed just now:
http://plone.293351.n2.nabble.com/Bug-on-sharing-page-upgrade-plone-app-workflow-to-2-1-6-td7566655.html
Does upgrading p.a.workflow help?
The solution in the end was to install plone.app.workflowmanager. For some reason that I do not understand the "Permission Roles" that show up under the workflow states created through ZMI did not have either the "Add" or the Review Permission.
Correcting the permissions through the workflow manager solved the problems.
If you try it out then note that you need to check the "Advanced Mode" checkbox to be able to update the permission settings on existing objects.
Having dregdged through ZMI screens for the past few days, the Workflow Manager is a great improvement! Very nicely done.
If someone can still explain why there is a difference between the permissions that I set through ZMI and the workflow manager I would very much like to know (feel free to edit this answer, marked as "community wiki").
I need to submit a form which triggers a workflow that goes through different stages.
How do I start first, is there a simple procedure to make it happen?
please help me.
You need to have permissions to create workflows. Find the particular list that contains the form and go to List Settings > Workflow Settings. If I remember correctly SP gives you Three-State as well as a Disposition Approval workflow.
Have you tried SharePoint Designer? It allows you to set custom triggers as well as develop more advanced workflows.
See if this material helps.