I want to create the Designer workflow which should work on the
specific folder only. Lets say I have xyz library and it has the Test
folder, so now when the document/file is added in this folder then
mail should hit to the Admin/Creator of this folder. I did not get any
such method till now in designer
SharePoint Workflow could not be associated with folder, but you could create a List Workflow and specify the following condition to verify if item is located under a folder named Test:
CurrentItem:Path ends with Test
Related
Office 365 - SharePoint 2013 Workflow
I have two Document Libraries:
Work In Progress
Archived
There is a SharePoint 2013 List Workflow Add Document attached to Work In Progress with attribute "Start workflow automatically when an item is created" set. This workflow copies the new document to the Archived library.
There is a SharePoint 2013 List Workflow Archive Rename attached to Archived with attribute "Start workflow automatically when an item is created" set. This workflow renames the new document.
Both Workflows were designed in SharePoint Designer - there is no custom code.
The Archive Rename Workflow is not starting when the document is copied by the Add Document Workflow, although it does start correctly when a document is uploaded manually through the UI.
I've seen a similar topic here [SharePoint workflow does not start for automatically uploaded documents][1]
[1]: SharePoint workflow does not start for automatically uploaded documents but that is concerned with custom code. This project cannot use custom code.
Does anyone have any ideas why the second Workflow is not being triggered?
Thanks
Edward
This is done to prevent workflow recursion. You can start another workflow using Start Sharepoint 2010 workflow action or rest api. There is one possile solution in details: http://blogs.msdn.com/b/sridhara/archive/2014/08/21/fix-sharepoint-2013-workflow-recursion-prevention-part-2.aspx
We use TFS integrated with Sharepoint for storing artefacts. Examples: end user documentation.
The artifacts are uploaded using Visual studio 2010 and not from web interface.
For each artefact preparation, there will be a task created in TFS.
Example:
Documentation preparation
The requirement is whenever a document is uploaded or modified in the sharepoint folder, can the user be alerted?
Example:
which TFS task he/she needs to update the completed hours
FOlder structure:
similar to the one shown in the 2nd answer to the below question
Share project documents in TFS different ways, what are your best practices?
It's not there by default, but one could build it oneself using a ListItemEventHandler (http://msdn.microsoft.com/en-us/library/ms437502.aspx) in sharepoint or a custom aproval workflow that activates from within sharepoint and creates workitems in TFS using the object model (http://msdn.microsoft.com/en-us/library/bb130322.aspx).
The requirement is whenever a document is uploaded or modified in the
sharepoint folder, can the user be alerted?
A simpler way to achieve only this requirement might be to put an sharepoint alert on the document list so one would recieve an e-mail when an item is created.
I need to transfer a reusable Workflow from the stage env. to the prod.
The workflow is associate to a list, so the list id is stored in the workflow.
Is it possible to transfer the workflow and change the list id to the list name with Visual Studio? (We have no SharePoint Designer access to the prod. env.)
Short answer: No
I tried several hours to fix a reusable workflow, which same as yours was associated with a specific list - I switched systems and the GUID changed --> Workflow was broken.
You can give it a try and rename the MyWorkflow.wsp to MyWorkflow.cab and extract that somewhere. The workflow files are XML based hence you can edit the associated list GUID with your favorite editor. Now you need to package your edited file back into a cab file, rename it to wsp and you can give it a shot. I tried exactly that and resented to just "re-clicking" (as it's SPD) my workflow (two screens come in handy here).
That's what I call "reusable" workflow... Next time do not associate your reusable workflow with anything to keep it reusable.
I would recommend creating an Content Type in a Feature and then base your list and your Reusable Workflow association on that Content Type. We had a project in December where we successfully used this method. I saved a Reusable Workflow as a template. I then deployed the Content Type solution package and the Workflow solution package to another environment. Worked like a charm.
There are tow alternatives for deploying workflow regardless the assigned content types
It is very simple just do the following:
Alternative One
Save the workflow as template
Go to the following path in your site
http://your_server_Address/SiteAssets/Forms/AllItems.aspx
Download the file as WSP
Go to the following URL
http://your_Target_server_Address/_catalogs/solutions/Forms/AllItems.aspx
Upload the WSP, and activate the solution
Go to the site settings, then Site Actions, then Manage site features
Activate the feature that is related to the workflow
If you click workflows under site administration you would be able to see your custom reusable workflow
Alternative Two
Save the workflow as template
Go to the following path in your site
http://your_server_Address/SiteAssets/Forms/AllItems.aspx
Download the file as WSP
Open your visual studio
Click add new project
Under SharePoint choose 2010
Choose Import reusable work flow
Follow the wizard
Project will be created and can be deployed
Note : Make sure your workflow is reusable and that it has no errors
I have a 2007 SharePoint site called Beta. On Beta, I have a custom List called MapData. This is a custom list of data that a webpart reads from. Data has been typed into Beta to make sure the webpart works correctly.
In production, called Prod, I have that same List called MapData except it has old values. How can I copy the data from one site to another. Beta and Prod are on different servers. I would like to do this without writing C# or something. Is it possible use the command line to just backup that list and restore it on a different server or possibly use Sharepoint designer?
The following options are not without drawbacks, but they are codeless:
If the list is not too large, you can save it as a template, copy the .stp file from Beta to Prod, and create a new list based on the template.
STSADM has export/import
Gary LaPointe's custom STSADM command for this job: http://stsadm.blogspot.com/2007/11/import-export-copy-and-delete-lists.html
I'm actually looking to sync the two lists.
I need one to be the data that the public can see, while the other (parent list) has all of the public and private data.
My goal is to extend functionality of the current asset tracking system.
Basically I would like to pull list of Clients and related assets from external system into sharepoint 2010.
Then I would like to associate documents with each asset. My first intention is to create a list of folders where each folder would be named respectively.
Tell me, if I am going in the wrong direction.
You can open your document library in explorer view and easly copy your content from external sorce to document liabrary, as windows explorer.
You can reffer the below link for more details
http://msmvps.com/blogs/shane/archive/2006/01/12/80843.aspx