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.
Related
After (or before) we convert from TFS 2012.2 to TFS 2015.3 (which we have done just fine in a test run) we would like to revert our team project to the standard TFS 2015 Agile process template, and no longer use the customized agile process that we had modified from TFS 2012. We are quite willing to delete all of our work items and start over, but need to keep the team project history and change sets. Anyone know how to do this? Answers to prior questions on this did not address this situation. Thanks.
There is no easy way to do it. Basically the steps require you to use a lot of witadmin commands. Start by deleting any work item types that were added and don't exist in the default template.
Then push the standard work item definition for each work item type.
Then push the categories
Then push the process configuration
Then delete any fields that are no longer used
That should bring you back to the standard template.
An alternative you could try is to use the WitMorph project. You can write a set of rules to migrate your data back into working order.
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 created a time recording program in vb.net with a sql-server as backend. User can send there time entries into the database (i used typed datasets functionality) and send different queries to get overviews over there working time.
My plan was to put that exe in a folder in our network and let the user make a link on their desktops. Every user writes into the same table but can only see his own entries so there is no possibility that two user manipulate the same dataset.
During my research i found a warning that "write contentions between the different users" can be occur. Is that so in my case?
Has anyone experience with "many user using the same exe" and where that is using datasets and could give me an advice whether it is working or what i should do instead?
SQL Server will handle all of your multi-user DB access concerns.
Multiple users accessing the same exe from a network location can work but it's kind of a hack. Let's say you wanted to update that exe with a few bug fixes. You would have to ensure that all users close the application before you could release the update. To answer you question though, the application will be isolated to each user running it. You won't have any contention issues when it comes to CRUD operations on the database due to the network deployment.
You might consider something other than a copy/paste style publishing of your application. Visual Studio has a few simple tools you can use to publish your application to a central location using ClickOnce deployment.
http://msdn.microsoft.com/en-us/library/31kztyey(v=vs.110).aspx
My solution was to add a simple shutdown-timer in the form, which alerts users to saving their data before the program close att 4 AM.
If i need to upgrade, i just replace the .exe on the network.
Ugly and dirty, yes... but worked like a charm for the past 2 years.
good luck!
I have one sharepoint2010 site. Suddenly i saw today that site has been put into READ only mode. How to audit, who has done this. I want to know who put the site into READ only mode(through CA->Site quotas and locks). Is there any way to find? (through powershell command, SPD, Database or through anyother things)
Thanks
Sivakumar. P
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.