Publishing major version document with Workflow

Hi
I have a SharePoint Designer Workflow 2013 and need publishing the major version of document. But, I think that there aren't actions to do publish the document in SPD Workflow.
How can I to do the publishing of document? Are there any web services to make this?
Thanks
Everton

you can need to create a VS approval workflow or create a custom SharePoint Designer activity. Or if you want to use this feature, programming
is also needed to create a custom activity to start the workflow automatically. check the below post explain the stuff in details:
http://social.technet.microsoft.com/Forums/sharepoint/en-US/93431f51-464e-4801-9341-a3dd80c871d3/sharepoint-designer-2010-custom-workflow-publishing-a-major-version
Please remember to mark your question as answered &Vote helpful,if this solves/helps your problem. ****************************************************************************************** Thanks -WS MCITP(SharePoint 2010, 2013) Blog: http://wscheema.com/blog

Similar Messages

Update Column value after current item is Approved and then publish major version using Sharepoint 2013 designer workflow

Hi,
We have a requirement to update a column value once the item has been approved.
Following settings have been made in the publishing articles list:
Require content approval for submitted items : yes
Create major and minor (draft) versions
Who should see draft items in this document library? :Only users who can edit items
Require documents to be checked out before they can be edited? : yes
I have createdatu a Sharepoint 2013 workflow to check if Approval sts of current item = 0 i.e. Approved , then check out and update the item and finally checkin the item. Everything works fine till this point except that the minor version of the item is
checked in. Due to this the updated columns are not published to others.
Also, I created a Sharepoint 2010 workflow to SET CONTENT APPROVAL = APPROVED and started this workflow from my list workflow above, but the item does not get checked-in and always shows "In Progress" status with comment "The item is currently
locked for editing. Waiting for item to be checked in or for the lock to be released.".
Please let me know where I am missing out so that once the item is approved, column value gets updated and current item is still in Approved status.
Thanks

Hi,
According to your post, my understanding is that you want to update Column value after current item is Approved and then publish major version using Sharepoint 2013 designer workflow.
You will get into this kind of Catch-22 situation trying to set the Content Approval Status in SharePoint Designer workflow:
- You must check out the document before you can change the Content Approval Status
- You can't change the Content Approval Status once the document in checked out
Since you set the Require documents to be checked out before they can be edited=Yes, you will need to check out the document when run the workflow on the item. But you cannot approve a document when it is checked
out. So the logic in workflow conflicts.
As a workaround, you can use the Start Another Workflow action to start the normal Approval workflow on the document. The built-in Approval workflow can work with a document that’s not checked out.
The designer approval workflow also can work with a document that’s not checked out.
You can create two workflow using SharePoint Designer 2013.
First, create a SharePoint 2010 platform workflow.
Then, create a SharePoint 2013 platform workflow.
Then when the SharePoint 2013 platform workflow start, it will start the SharePoint 2010 platform workflow to set content approval status, then the SharePoint 2013 platform workflow will update current item value.
More information:
SharePoint Designer Workflow Content Approval Issue
SharePoint 2010 Approval Workflow with Content Approval
Best Regards,
Linda Li
Linda Li
TechNet Community Support

Proper way to get the latest published Major version of Document

Hi,
I have a Document Library which has "Create major and minor (draft) versions" enabled.
Now, from my C# application I need to fetch the latest major version of a document from that library.
What is the proper way to do this?
As of right now, I do the following:
return sourceFolder.Files["documentName.docx"]; // sourceFolder is a SPFolder object
Now, I don't trust that this will always give me the latest published major version of the document. Or am I wrong? If I'm wrong, how should I do this?
Thanks!

Problem
When you store critical documents in the SharePoint libraries, sometimes it becomes necessary to track all the changes and to maintain version history for them.
Solution
There might be a time when you would need to restore files back to an older version if any inadvertent change happens. You can also track changes for auditing purposes.
So how does SharePoint allow creating different versions of documents? How does version history work? What are the different types of versions we can maintain for our library or list and how can we revert back to an older version?
SharePoint allows you to enable (by default it's disabled) versioning on lists and libraries. Once enabled, SharePoint will maintain multiple versions of the document or list which gets incremented on each change iteration. There are three different versioning
settings:
No versioning - This is the default setting in which the current version overwrites the older version. There are no previous versions stored. This setting is not recommended especially if your document library contains critical or important
documents.
Create major versions - Also called simple versioning, in this setting the document versions will be numbered with whole numbers, called major versions, i.e. 1, 2, 3, 4 etc.
Create major and minor (or draft) versions - In this setting document versions will be numbered with whole numbers (1, 2, 3, 4 etc.) as well as numbers with decimals (.1, .2, .3, .4 etc.). The whole number is called the major version
(indicates final copy) and the numbers with a decimal are called minor versions (indicates work is still in progress). You use this setting if your document goes through several iterations/drafts/reviews (minor versions) and you want only the final copy (major
version) to be published to a broader audience.
Please note for a list or list items, the only option available for versioning is creating major versions, no minor versions are created.
Once versioning is enabled SharePoint automatically and transparently creates the next version of the document whenever a user updates a document in the library. These are some of the different scenarios when SharePoint will create a new version for your
document or list item:
When a new document or list item is created or uploaded into SharePoint, version 1 is created if the option
Create major versions option is enabled or version 0.1 is created when
Create major and minor (or draft) versions is enabled (not applicable for list items) and when you publish it then next higher major version is created.
When you upload a document with the same name as an already existing document in the library and check the
Add as a new version to existing files check box, the existing file becomes an older version and the new uploaded document will have next higher version number.
When any properties (metadata fields) of the document or list item is changed.
When you Check-in a document that was previously Checked-out.
When you open a document in the associated application, edit and save it for the first time. On subsequent changes no new versions will be created as long as you don't close the application and re-open it.
When you restore the old version of the document.
Please note, although the demonstration in this tip has been shown in SharePoint 2010, the versioning feature has been part of previous SharePoint versions as well.
Reference URL with Example :
http://www.mssharepointtips.com/tip.asp?id=1047
Thanks
Jaison A

After the in place upgrade from SharePoint server 2007 to 2010, the out of the box approval workflow does not prompt for additional information after check in of a major version.

I think it has to do with the interaction between Word, InfoPath, IIS, and /or SharePoint, but I cannot put my finger on it. Maybe client integration or authentication settings? I have looked at it in wireshark
and have not seen anything glaring.
Steps to reproduce the (working) behavior:
Set up a document library in SharePoint 2010.
Under versioning settings, make the following changes:
Set Require Content Approval for submitted Items to Yes
Select Create Major and Minor (draft) versions
Set require checkout to Yes
Create an out of the box “approval” workflow with the following settings:
Start this workflow to approve publishing a major version of an item.
I then create a new document. Save it. check it in. it is now version 0.1.
I then open it again. check it out. Make a change. Close and save it.
Check it in.
Publish major version:
At this point a screen is presented to me to enter workflow parameters. This screen comes up in Enterprise 2013 and MOSS 2007, but not the migrated version of 2010:
This is what I need help with. It should come up in 2010. To fix it in 2013, I had to change the IIS bindings to only have 1 entry for a port. I did this for 2010 and it did not work.
Any help or ideas is very appreciated. Thanks very much in advance.

Hi Chris,
According to your description, my understanding is that the approval workflow cannot work when the workflow was set to start to approve publishing a major version of an item after upgrading to SharePoint 2010.
I recommend to check the approval workflow in Workflow settings of the corresponding library to see if the Start this workflow to approve publishing a major version of an item is checked.
For test, I recommend to create a new OOB approval workflow and set it to start to approve publishing a major version of an item in the same library to see if the workflow can work.
Thanks
Victoria
Forum Support
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected]
Victoria Xia
TechNet Community Support

Document with various reviews / approvals

Dear Friends,
In our document cycle it will be routed through many reviews and approvals. May be in each review and approval stage users will put their comments / edit the document.
We have following statuses:
Create --In prgoress- review 1 --- review 2 --- review 3 -
approval 1 -- approval 2 --- approval 3 --completed
I am having following options:
1. Each reviewr / approval can down load the document (if it editable like word / excel etc) , after editing attach it as another attachment. In this case we will have two documents original and edited one in same version of the document.
He change the version and attached the edited document & delete the original document. In this case old version document with original document need to be completed / rejected / locked. This will be extra work for them. More over in this case there may be more versions & to identify who did what changes is difficult. We need to open each document & find out.
2. If the document is like PDF he can enter his comments on separate layer. Each reviewer / approver can enter his own layers & enter their comments etc.
Then some one need to be comiled all these editings / layers and make new version of the document and also complete / reject / locked the old version document.
3. Try to do outside the SAP the editing & upload the final version of the document.
4. Can we consider Content version ? In this case can we get statuses also. Can we name each version ?
I want to understand in my scenario which is better approach consideringthe following points:
a. I want to see the older / new version of changes. Want to know who proposed what changes / comments .
b. what is original document & sub srquent documents.
Regards,
Sai Krishna

Dear Pradeep,
Thanks for ur reply.
In this case creator / originator need to compile all layers and submit new document. Shall he need to create new version for this ? or shall add new original attachment in same DIR. At what stage this needs to be done ?
New status can be :
Create - R1- R2- R3- Change updated- A1-A2- A3-Completed
I think after R1, R2, R3 he will submit new document for approval. Then after A1, A2, A3 he will upload another document which is final. Shall we need to create new cersion, other wise there is no record. If we make new version old version DIR status need to be changed to completed / rejected / locked to complete the cycle. Same time for new version DIR status to be Change updated (new status) so that it can go to A1. For each document he needs to this exercise means long process.
Am I right ?
Regards,
Sai Krishna

Problem with custom sharepoint designer approval workflow - check box: 'Start this workflow to approve publishing a major version of an item' is greyed out

I wanted to create a simple approval workflow. Hence I opted to start from scratch rather than copy the OOTB approval WF. Using SharePoint Designer (not Visual studio) I created a reusable workflow and have added the built in 'Start approval process' action.
It's saved and published globally.
Everything works fine except that when associating the WF with a list the 'Start this workflow to approve publishing a major version of an item' check box is disabled.
Major and minor versioning is enabled for the library.
What am I missing here? Or do I have to start from the OOTB approval WF to get this to work?
Regards
Henning

Again - new ideas pop up right after defining the issue as a problem. :-) Problem solved!
I solved this by creating a new workflow from the original publishing approval workflow (copy and replace), but instead of tweaking the already defined approval process (WF action) I deleted it, then deleted all initiation form and local variables,
and then added the 'Start approval process' action again. This re-installs all the necessary local variables without any initiation form involvement, which is just what I want.
From here I can tweak the workflow to make it more user friendly, much like
described by Bobby Chiang in his great blog.
Remember to add action Set Workflow Variable 'EnableContentApproval' to Yes right before the Start Approval Process action, else the document's status won't be set to 'Approved' or 'Rejected' as an output of the workflow.
Learning every day!
Henning

OOTB workflow gives error when user rejects in the document in publishing a major version.

Hi All,
I am using OOTB workflow with little customization with following configuration
1. Allow content approval enabled
2. Configure a workflow with following general settings true
3. Start workflow on publish of Major version only is enabled
4. workflow has following configuration enabled.
Now, when user start publishing of major version and Starts the workflow. workflow starts without any problem.
But as and when the user rejects the document it is rejected with Reject status with "Approval Status" as well as workflow status which is expected.(This is correct )
But when i look at the workflow history i can see at last line there is an Error with
An error has occurred in In [Workflow Name].
Now when user check out and check in item again and try to publish with Major version again. it gives errors that the previous version is still running.
I have trace a lot and also test with original OOTB workflow itself. it is behaving the same.
As per my findings there is problem in "Completion condition of this task process" the end task process is not being executed correctly.
I tried to end the task process with End the task process action but it is still not working.
I need some help in this issue as users are facing problems in case of rejection. I hope some one has the solution for the same.
Two things i have noticed are
1. My MS office 2010 professional plus is expired as i was using trial version
2. I have made stop inheriting tasks permission and remove all default groups as i have settings in workflow "Only allow task reception and process owner to read and edit workflow task"
3. Earlier i had also installed "Sharepoint 2010 April 2012 updates". i had also observed that (installing Sharepoint 2010 April 2012 updates) before that if user has selected "Automatically rejects the document if any participant rejected". it ends
with "rejected" status. At present it remains in inprogress and not stops with rejected status.
Can any one give me a hint what should be the problem ? Is it a problem with latest Sharepoint 2010 April 2012 updates ?
Thanks,
S. M. MANIYAR

I have done following testing.
1. The server in which i have not installed sharepoint 2010 April 2012 updates the above scenario is working fine without any problem
2. I have also observed following logs of error in server where April 2012 updates is installed.
8/28/2012 03:51:41.33 w3wp.exe (0x0F08)                       0x0A00 SharePoint Foundation
Workflow Infrastructure       88xr Unexpected WinWF Internal Error, terminating workflow Id# 8bf7fef1-c92e-4b22-a16f-480425d3adc6
08/28/2012 03:51:41.33 w3wp.exe (0x0F08)                       0x0A00 SharePoint Foundation
Workflow Infrastructure       98d4 Unexpected System.InvalidOperationException:
CompositeActivity cannot transition to 'Closed' status when there are active child context still exist for child activity.     at System.Workflow.ComponentModel.Activity.MarkClosed()     at System.Workflow.ComponentModel.ActivityExecutionContext.CloseActivity()
at Microsoft.Office.Workflow.Actions.OfficeTask.FinalClose(Object sender, EventArgs eventArgs)     at System.Workflow.ComponentModel.ActivityExecutorDelegateInfo`1.ActivityExecutorDelegateOperation.Run(IWorkflowCoreRuntime workflowCoreRuntime)
at System.Workflow.Runtime.Scheduler.Run()
Following are last two lines of workflow history.
S. M. MANIYAR

"Start this workflow to approve publishing a major version of an item" in Project Site templates

Hi
I created a document library with the "Start this workflow to approve publishing a major version of an item" on, and saved the site as a template. However when I create instances using that project site template, the document library doesn't
have the "Start this workflow to approve publishing a major version of an item" option on, like the site that was used for the template have.
Is this option not possible to save on a project site template?
Here are the steps I did:
On a document library I set the versioning for major and minor version
I create an “Publishing approval” workflow and set it to “Start this workflow to approve publishing on a major version”.
But when I create a project instance of this type, the document library on the project site has the “Start this workflow to approve publishing on a major version” turned off.
Thanks!
Best regards

Hi,
I recommend to create a WebProvisioned event receiver.
We need to create an event handler and register it with the Web Provisioned event. In the event, we need to find the specific Library and set SPList.DefaultContentApprovalWorkflowId property.
When the site is provisioned, the event handler is activated. Then the "Start this workflow to approve publishing a major version of an item" option will be checked.
More information:
SPWebEventReceiver.WebProvisioned method (Microsoft.SharePoint)
SPList.DefaultContentApprovalWorkflowId property (Microsoft.SharePoint)
Attaching Web Event to perform operations after creating the web (Event Receiver Concept)
Best Regards,
Linda Li
Linda Li
TechNet Community Support

Start this workflow to approve publishing a major version of an item is disabled in SharePoint Online

Hi there,
Despite turning on the require content approval for submitted items in the version setting. Start this workflow to approve publishing a major version of an item is still disabled in the workflow settings.
Anyone one know how to enable this option.
Thanks
Regards,
Ravi

Hi Wendy,
I tried to copy and modify the Globally Reusable Workflow->Approval-SharePoint 2010 but the problem
that I am facing is, I cant seems to find the Assign a task in the Actions list and also when I am setting the approver variable to a value, I am missing a column name( how can I get a column which is used in a list?).
But “Start this workflow to approve publishing a major version” is enabled now using this workflow
but saying that I am unable to complete the workflow due to the action and column missing.
Previously the work flow that I created was for a specific list.
Is there any work around to this issue?
Thanks
Regards,
Ravi

Error when checkin a major version from office document

Hi,
We havea document library set up to automatically start a workflow when a major version is published. From sharepoint this is working fine. However if we checkin from any MS Office application we are getting the error below and the workflow is not started.
Any help appreciated.
Chris
<v:shape alt="" id="Picture_x0020_1" o:spid="_x0000_i1025" style="width:373.5pt;height:105pt;" type="#_x0000_t75"> <v:imagedata
o:href="cid:[email protected]" src="file:///C:\Users\McCartc\AppData\Local\Temp\msohtmlclip1\01\clip_image001.png">
</v:imagedata></v:shape>

Hi,
I tried to reproduce the issue like this:
1. Create a new Document Library and add an Approval workflow for it using the OOTB workflow template “Approval – SharePoint 2010" as the documentation below suggests:
http://office.microsoft.com/en-001/sharepoint-server-help/use-a-workflow-to-manage-content-approval-for-a-library-HA010172010.aspx
2. Then upload a Word document to this library, check out, edit in the client Office 2010 application;
3. After editing, check in as a major version and close the document;
4. Back to the Document Library, refresh the page, the workflow status column shows “In Progress”;
I suggest you do a test with the steps above in another machine to see whether the issue still exists.
Feel free to reply if there are any progress.
Thanks
Patrick Liang
Forum Support
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected]
Patrick Liang
TechNet Community Support

How to tell what version of a document the workflow ran against?

I am using the OOB Approval workflow and in the workflow information I see a Document field, but that links latest version of the document. How can I tell what version of the document the workflow actually ran against?

Hi,
Set a variable in the workflow to be equal to the version of the document.
Now you can use this variable to update a column in the document library with the version and date the workflow was ran. Next time the workflow runs, update this column with next run details.
OR write this variable to workflow history. Hope it helps.
Regards, Kapil ***Please mark answer as Helpful or Answered after consideration***

PDF Printing with BI Publisher makes empty document

Hi all,
We have installed the BI Publisher. And configured apex to use it as printer server.
In Apex we created a report query. The query I exported to an xml file. And I also exported the xml schema.
These two files I imported in Word with the BI Publisher plugin. Next I created a simple document with the word plugin and exported it as XSL-FO.
In Apex I created a report_layout with named columns based on the xsl-fo document I created.
Now when I go to the created report query and point to that document it will render an empty file. I get an error message telling me the file is damaged.
The query returns data however.
We are using Apex 4.
Does anybody have a clue?
Is there a way I can add some debugging in the process?
Thanks,
Maurice
Edited by: maurice.niezen on Oct 6, 2010 5:12 AM

If you are using that route, I'd try editing the xsl file before you upload it into APEX.
I found that APEX didn't like some of the tags, so if you look at your XSL file in wordpad or similar and delete the following lines if they are there:
<xsl:param name="_XDOCALENDAR">GREGORIAN</xsl:param>
<xsl:param name="_XDOLOCALE">en-US</xsl:param>
<xsl:param name="_XDOTIMEZONE">GMT</xsl:param>
<xsl:param name="_XDODFOVERRIDE">;</xsl:param>
<xsl:param name="_XDOCURMASKS">;</xsl:param>
<xsl:param name="_XDONFSEPARATORS" />
<xsl:param name="_XDOCHARTTYPE">image/svg+xml</xsl:param>
<xsl:param name="_XDOOUTPUTFORMAT">application/pdf</xsl:param>
<xsl:param name="_XDOSVGFONTEMBED">true</xsl:param>
<xsl:param name="_XDOCTX">#</xsl:param>
<xsl:variable name="_XDOXSLTCTX" select="xdoxslt:set_xslt_locale($_XDOCTX, $_XDOLOCALE, $_XDOTIMEZONE, $_XDOCALENDAR, concat($_XDODFOVERRIDE,'',$_XDOCURMASKS,'',$_XDONFSEPARATORS))" />
You should be left something like:
<?xml version = '1.0' encoding = 'utf-8'?>
<xsl:stylesheet version="2.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:fo="http://www.w3.org/1999/XSL/Format" xmlns:ora="http://www.oracle.com/XSL/Transform/java/" xmlns:xdofo="http://xmlns.oracle.com/oxp/fo/extensions" xmlns:xdoxslt="http://www.oracle.com/XSL/Transform/java/oracle.apps.xdo.template.rtf.XSLTFunctions" xmlns:xdoxliff="urn:oasis:names:tc:xliff:document:1.1" xmlns:xlink="http://www.w3.org/1999/xlink">
<xsl:variable name="_XDOFOPOS" select="''"/>
<xsl:variable name="_XDOFOPOS2" select="number(1)"/>
<xsl:variable name="_XDOFOTOTAL" select="number(1)"/>
<xsl:variable name="_XDOFOOSTOTAL" select="number(0)"/>
<xsl:template match="/">
before the root tag.
That worked for me, so worth a try.
Jon.
PS - Just to add that was when we were set up with standard printing rather than advanced.
Edited by: J F Miller on Oct 6, 2010 1:33 PM

Took delivery of imac yesterday with pre-installed Pages, Numbers and Keynote. App store says they need updating but won't let me because I've never owned the major version of the software. I have paid like anyone else, so why can't I update?

Took delivery of imac yesterday with pre-installed Pages, Numbers and Keynote. App store says they need updating but won't let me because I've never owned the major version of the software. I have paid like anyone else, so why can't I update?

You must be signed into the Apple Store with your Apple ID or it won't work.
and
How to deal with a 100 Store Error:
Try here > Mac App Store: "An unknown error occurred (100)" when purchasing
If that doesn't help, open the Finder. From the Finder menu bar click Go > Go to Folder
Type this exactly as you see it here;
~/Library/Caches/com.apple.appstore/Cache.db
Click Go
Move the Cache.db file to the Trash.
Now here:
~/Library/Preferences/
Click Go
Move these files from the Preferences folder to the Trash.
com.apple.appstore.plist
com.apple.storeagent.pllist
Now here:
~/Library/Cookies
Click Go
Move the com.apple.appstore.plist file from the Cookies folder to the Trash.
Empty the Trash, try the App Store.

App-V PowerShell: Script to Query XenApp Servers for App-V Publishing Errors and Output an Excel Document with the Results

Please Vote if you find this to be helpful!
App-V PowerShell: Script to Query XenApp Servers for App-V Publishing Errors and Output an Excel Document with the Results
Just posted this to the wiki:
http://social.technet.microsoft.com/wiki/contents/articles/25323.app-v-powershell-script-to-query-xenapp-servers-for-app-v-publishing-errors-and-output-an-excel-document-with-the-results.aspx

Hi petro_jemes,
Just a little claritification, you need to add the value to the variable "[string]$ou", and also change the language in the variable "$emailbody" in the function "Get-ADUserPasswordExpirationDate".
I hope this helps.

Document Management integration with Workflow

Hi anybody,
I have to setup a workflow using Oracle Databse Server 8.1.7, Oracle 9i Application Server 1.0.2.2.1 and Workflow 2.6 on Windows 2000 Advanced Server.
Trying to run the sample workflow
"Workflow Demonstrations/Document Management"
(http://<host>:<port>/pls/<wf_dad>/wf_initiate.Process?ItemType=WFDM), I get the following problem:
When I push the button "Send Document" to attach a document, the new browser window shows :
"The page cannot be found". The url is like this: http://orc9:7778/jbc/aol/Oasjbc?template=dm_create.htm ...
Does anyone know what is missing or wrong configured here?
Which Document Management software can be used together with Workflow in order to be able to attach documents to items?
Can Internet File System be used here?
Thank you for your help in advance!
Dorian

Hi Dorian
The existing document management feature in Workflow is reserved for future use. If you want to use iFS and Oracle Workflow together, there is a technical whitepaper available on OTN. Navigate OTN:Products:Oracle Internet File System->Technical Information.
CHeers
Mark
Hi anybody,
I have to setup a workflow using Oracle Databse Server 8.1.7, Oracle 9i Application Server 1.0.2.2.1 and Workflow 2.6 on Windows 2000 Advanced Server.
Trying to run the sample workflow
"Workflow Demonstrations/Document Management"
(http://<host>:<port>/pls/<wf_dad>/wf_initiate.Process?ItemType=WFDM), I get the following problem:
When I push the button "Send Document" to attach a document, the new browser window shows :
"The page cannot be found". The url is like this: http://orc9:7778/jbc/aol/Oasjbc?template=dm_create.htm ...
Does anyone know what is missing or wrong configured here?
Which Document Management software can be used together with Workflow in order to be able to attach documents to items?
Can Internet File System be used here?
Thank you for your help in advance!
Dorian

Publishing major version document with Workflow

Similar Messages

Maybe you are looking for