Hi Santhosh,

you can use SharePoint web services to check for attachments on your list item. Place a "Call web service" action and configure it to use the Lists web service (https://msdn.microsoft.com/de-de/library/office/websvclists.aspx ). In the response you will get a list of all attachments. You can then check this list and see if there are actually any attachments present and lead your workflow in the respective direction.

See the MSDN article for method reference: Lists.GetAttachmentCollection-Methode (WebSvcLists)

Best Regards

Philipp

Well, that sounds not easily achievable, since in the worklfow you don't know what has changed in the underlying item.

What would come to my mind would be to enable versioning on the list and then make whe workflow lookup the changes in the version-history. When the change involved adding an attachment you send out your mail, otherwise the workflow will just exit.

Ahh okay, so he only wants every NEW added attachment sent by mail? Didn't get that, but reading the question for the sixth time, i think you could be right

Well then you would need to store the response from the web service somewhere (for example in a new column in the same list) and then check your received web service response against the stored value in the colum, that shows the last attachments every time the edit workflow runs. This way you can find out, which attachments were added during the last editing of the item.

But the versioning idea sounds intressting as well as long as the attachments won't be too big in size. But since 2 Versions would be sufficient for this use case, even that shouldn't be a big issue.

Yeah, I also thought about that - you could have one workflow run automatically whenever a new item is created. This will setup a baseline-value in a column.

Then you create a second workflow which runs whenever the item is updated. This workflow will extract some unique data from the attachments and compare this to the baseline to check whether an attachment was added (or removed). you would then need to update the baseline.

Hi Philipp ,

Thank you for your great time for me.

Your thinking is correct, i want every New added attachment send by email, actually i am new user to nintex , i don't know how to configure the "Call web Services" , Could you please explain briefly .

Thanks in advance.

Thanks,

Santhosh

Hi Eiben,

Thank you for your great time for me.

My exact requirement is , when user added  attachment to list , every new attachment will get a mail.how develop the workflow in nintex .i am new to nintex worklfow.

Thanks,

Santhosh

Well - a basic description of the action can be found at http://nintexdownload.com/helpfiles/nw2013/nintexworkflow2013usermanual.html#Nintex.Workflow.CallWebService .

As the URL you would need to insert http://<site>/_vti_bin/Lists.asmx and provide a username and password of a user who can access this list. Then can query the webservice at the previous URL for all available methods.

Among others there should be a method called GetAttachmentCollection. if you select this, you'll see two input-fields being renderd. There you can provide the name of the list as well as the list-item id. If you execute the action you'll reveive a collection of the attachments of this list item. A detailed description can be found at: https://msdn.microsoft.com/de-de/library/office/websvclists.lists.getattachmentcollection.aspx

see above answer ... from the https://msdn.microsoft.com/de-de/library/office/websvclists.lists.getattachmentcollection.aspx  method you'll get a list of attachments, you could query the XML using the XML query action and turn the attachments into a collection. Then you could iterate over the list of attachments and send out some kind of notification.

you could create a hidden field on the content type. in the workflow store the attachment/s name in the field. On modify run a different workflow that runs a condition, that if the workflow name/s is different to what is stored then send an email. from memory when you get the attachment collection, the names are comma delimited, so as long as your hidden field was a plain text multiline field, you should be golden