In the Word Automation Solutions: What It Does post, I supplied an incredibly high-level outline with the server-side API offered through the services, exhibiting you the essential outline for doing work along with the services: a ConversionJob Produce it the settings for that conversion(s) to perform Person credentials to fetch/store files Target file format for output Etc. Inform it while file(s) to practice Initiate (optionally) Check progress
In this post, I desired to evaluate a particular example solution and what's involved in establishing it, to stroll due to a authentic example from the company end-to-end.
In this illustration, I have a library by which I save contracts as they're becoming created. When they're approved, I set the Standing property for that document within just the library to "Final" and an XPS edition of it is instantly created to archive the agreed-upon version from the material. Remedy
I've published up the method in tutorial sort, so people w/ Visual Studio 2010 and SharePoint 2010 can really assemble the resulting workflow; if which is not your objective, browsing the sample code really should be sufficient to present you an concept of how the solution operates. the Document Articles Variety
Before we begin, we add the Position column towards the Document articles sort, so that we can use it within this walkthrough. the SharePoint internet page, pick Site Actions (inside upper-left hand corner), then click Page Settings. Under the ################## heading, decide upon Page Content Styles. Click on on Document to edit its content type. Decide on Add from current website columns. Inside Out there Columns list, come across Position and click Add to add it towards the list of columns to add. Note: If Position cannot be uncovered, it could already happen to be added towards the written content variety. Click on Ok. Developing the Venture
First, we make a SharePoint challenge in Visual Studio which will contain our workflow code. Visual Studio 2010 as an administrator. Be aware: It's essential to start out Visual Studio as an administrator as a way to efficiently publish the undertaking towards the SharePoint farm. Below the File menu, choose New, and after that Project… With the New Undertaking dialog box, pick out the Visual C# SharePoint 2010 project form. Decide upon Sequential Workflow in the template listing. Give the project a name (e.g. ArchiveDocument). Click on Okay to build the project. When asked, choose to Deploy like a farm method. Be aware: This is required since the Phrase Automation Services object model can't be accessed from partially trusted code. Around the up coming action, give the workflow a friendly title, e.g. "Archive Document" and find Record Workflow as the workflow variety. Depart the default association settings, and click on Future. Notice: If you need to attach the workflow to a specific list, adjust the Checklist drop-down to that listing. With this tutorial, we will make use of the default Shared Documents list around the SharePoint online site. Uncheck "On merchandise creation" while in the default settings for workflow initiation (leaving "Manually" as the only picked worth), and click Finish.
At this stage, we now have a new empty workflow undertaking. on the Phrase Automation Providers Object Model
To accomplish conversions, we need to feature a reference to your Word Automation Solutions object model. the Solution Explorer window, right-click on References and go for Add Reference… Browse to search out the reference making use of the Browse tab. The Microsoft.Office.Word.Server.dll assembly is situated inside SharePoint Server 2010 ISAPI folder, frequently located at C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\ISAPI.
Ok to add the reference.
Note: When you acquire a warning that the DLL necessitates a newer model on the .NET Framework,
Microsoft Office Ultimate 2007 Product Key, go for Indeed to add the reference anyway. Then, add a reference to Procedure.World wide web.DataVisualization, usually positioned at C:\windows\Assembly\GAC_MSIL\System.Web.DataVisual ization\3.5.0.0__31bf3856ad364e35\. Workflow
Now that we have now a workflow task, we are going to add a two-step workflow: the very first action checks irrespective of whether the Position home may be set to "Final"; after it's got, the next action converts the document. Look at the Status Residence Through the Toolbox, under Windows Workflow v3.0, add a Although activity right after the existing onWorkflowActivated exercise. In the Toolbox, underneath SharePoint Workflow, add an OnWorkflowItemChanged exercise inside of the While activity. Click on around the OnWorkflowItemChanged activity. From your Attributes window, set the worth of the CorrelationToken property to workflowToken (the sole merchandise inside drop-down record).
tells the activity the information necessary to associate the ItemChanged occasion along with the accurate workflow. Attributes window, click about the lightning bolt to change to Occasions see, and press ENTER during the Invoked procedure to build a blank event handler. This celebration handler shall be triggered whenever the merchandise alterations. From the code window, add a world wide Boolean value to track whether or not the Standing property has long been set on the ideal value:
bool documentReady = bogus; the celebration handler, add code to examine the value of your column, and set the documentReady variable appropriately:
//check in the event the Standing is set to ultimate; in that case, the document is ready to archive
if (workflowProperties.Item["Status"] != null)
_documentReady = ((string)workflowProperties.Item["Status"] == "Final");
for the workflow designer window. Notice: It will possess a title like Workflow.cs [Design]. Click about the Whilst exercise. From the attributes window, click on Condition and decide on Declarative Rule Condition. Expand the Condition field, exposing ConditionName and Expression:
the ConditionName field, give the condition a identify, e.g. Able to Archive. Click on in the Expression field, and press the button to set the condition. Inside the dialog box, style the following condition:
documentReady == ######## to save the condition.
The resulting workflow now looks like:
2: Convert the Document
Now that we've created the portion with the workflow that waits for the column worth to be set to Final,
Windows 7 Code, we add the workflow exercise to in fact convert the document. the Toolbox, beneath Windows Workflow v3.0, add a Code activity following the current Even though exercise. In the Properties window, click on around the lightning bolt to change to Occasions see, and press ENTER in the ExecuteCode system to create a blank event handler. This event handler will undoubtedly be triggered when the item variations. Inside the celebration handler, add code to perform the conversion:
//create a conversion job
ConversionJob job = new ConversionJob("Word Automation Services"); settings
job.UserToken = workflowProperties.OriginatorUser.UserToken;
if (workflowProperties.Page.SiteSubscription != null)
job.SubscriptionId = workflowProperties.Page.SiteSubscription.Id;
job.Settings.OutputFormat = SaveFormat.XPS;
job.Title = "Archive Document Workflow"; file
string fileUrl = workflowProperties.WebUrl + "/" + workflowProperties.ItemUrl;
job.AddFile(fileUrl, Path.ChangeExtension(fileUrl, "xps")); conversion
job.Get started(); code creates a brand new ConversionJob, which defines a set of conversions, supplying the name for the service application. Notice: This illustration assumes the identify of your service application is "Word Automation Services", which is the default name when it's created via the Farm Configuration Wizard. If you ever have used a different name for your services application, transform the identify as appropriate. set the mandatory settings for that conversion: UserToken house, which specifies the consumer credentials used to read the input file and write the output file. The SubscriptionId home, which specifies the website subscription ID of your website. Notice: This parameter is only requested if your SharePoint farm happens to be configured in partitioned mode. The OutputFormat home, which specifies the output file format for your conversion.
As well, we specify one optional setting: Title home, which specifies a pleasant identify for that conversion.
Next, we add the file towards the conversion job via the AddFile procedure, and launch the processing from the conversion implementing the Initiate technique. workflow now looks like: Step 3: Monitor the Conversion
Once we've scheduled the conversion, it really is processed asynchronously. Finally, we will add a stage to keep an eye on the result in the conversion ahead of terminating the workflow, so that the workflow completes once the conversion. the Toolbox, beneath Windows Workflow v3.0, add a Whilst exercise after the current codeActivity exercise. From the Toolbox, beneath Windows Workflow v3.0, add a Sequence activity inside of the Despite the fact that activity. From your Toolbox, underneath Windows Workflow v3.0, add a Delay activity inside of the Sequence activity. Click on on the new codeActivity activity. In the Properties window, click around the TimeoutDuration house and set it to 00:00:30 (30 seconds). This means that the workflow shall be re-checked at most every 30 seconds. Notice: Considering delays in SharePoint workflows are processed working with a timer job with a default frequency of five minutes, it could take up to 4:59 for the delay to be processed. From your Toolbox, beneath Windows Workflow v3.0, add a Code exercise immediately after the Delay activity. Click on the new codeActivity activity. Through the Attributes window, click on on the lightning bolt to change to Events see, and press ENTER while in the ExecuteCode strategy to create a blank function handler. This event handler will be triggered when the merchandise changes. Inside code window, add two world wide variables: a Guid value to shop the ID in the conversion, in order that we can look at it on regular intervals,
Office 2007 Pro Plus Key, and a Boolean to track whether or not the conversion completed successfully:
Guid jobId;
bool conversionComplete = bogus; the 1st code method, retailer the ID with the conversion job into this world-wide variable, by adding the following code immediately after the Begin procedure:
//save the job's ID
jobId = job.JobId; the new celebration handler (created in Action 6), add code to check out the standing with the conversion:
//monitor the conversion
//get the page subscription ID
Guid? siteSubscription = null;
if (workflowProperties.Website.SiteSubscription != null)
siteSubscription = workflowProperties.Web site.SiteSubscription.Id; the conversion is complete; if it will be, refresh
ConversionJobStatus position = new ConversionJobStatus("Word Automation Services",
Microsoft Office 2007 Professional Plus Serial Key, jobId, siteSubscription);
if (standing.Count == position.Succeeded)
//success!
conversionComplete = true;
else if (position.Count == standing.Failed)
//conversion failed
ReadOnlyCollection<ConversionItemInfo> failedItems = status.GetItems(ItemTypes.Failed);
throw new Exception(failedItems[0].ErrorMessage);
else if (status.Count == status.Canceled)
//conversion was canceled
throw new Exception("Conversion was canceled.");
didn't complete, keep waiting checks the status from the conversion working with the ConversionJobStatus object. Notice: This illustration assumes the identify with the company application is "Word Automation Services", which is the default identify when it is actually created via the Farm Configuration Wizard. For those who have used a different name for the services application, improve the identify as appropriate. have the standing for your job, we are able to check out regardless of whether the item has succeeded or failed, and react accordingly. Otherwise, we do nothing, since the conversion is still in progress. towards the workflow designer window. Be aware: It will possess a title like Workflow.cs [Design]. Click on on the Even when exercise. Through the attributes window, click on Condition and decide on Declarative Rule Condition. Expand the Condition field, exposing ConditionName and Expression:
the ConditionName field, give the condition a identify, e.g. Conversion Complete. Click with the Expression field, and press the button to set the condition. From the dialog box, variety the following condition:
conversionComplete == bogus to save the condition.
The ultimate workflow should certainly appear like this: Deploy the Remedy
Now, deploy the option to your SharePoint farm. the Build menu,
Office 2007 Pro Keygen, pick Deploy Treatment to assemble the code and deploy it to SharePoint. From the Shared Paperwork library (or whichever library you chose in Step 9 of Developing the Undertaking), upload a whole new Phrase document to get started the workflow. Right-click about the new document and go for Workflows. Click on Archive Document to commence the workflow. Right-click around the new document and select Edit Attributes. Set the Standing home to Ultimate. Press Okay.
When the timer job runs and the conversion is processed, you must see the XPS file appear subsequent for the original document (refresh the page to see the result). Note: Again, since the conversions are processed using a timer job, it might take up to your frequency for the timer job for that file to appear.
Microsoft Office 2007 Professional Plus Serial Key
who saw quaternion
Linear Mode
