Windows 7 Activation Key Word Automation Services

[sangma07]

In the Phrase Automation Services: What It Does publish, I supplied an incredibly high-level outline in the server-side API supplied by the company, showing you the basic outline for functioning together with the service: a ConversionJob Give it the settings for the conversion(s) to execute Person credentials to fetch/store files Target file format for output And so forth. Inform it though file(s) to method Begin (optionally) Monitor progress
In this publish, I wanted to take a look at a particular instance remedy and what is associated with designing it, to walk due to a true illustration with the service end-to-end.
In this instance, I have a library through which I retailer contracts as they're becoming created. Once they are approved,Windows 7 Enterprise Serial Key, I set the Standing house for that document inside of the library to "Final" and an XPS edition of it will be instantly produced to archive the agreed-upon model for the articles. Resolution
I've published up the choice in tutorial form, so people w/ Visual Studio 2010 and SharePoint 2010 can actually establish the resulting workflow; if which is not your purpose, browsing the sample code ought to be adequate to provide you an concept of how the answer will work. the Document Content Type
Before we start off, we add the Position column to your Document subject matter form, so that we will utilize it during this walkthrough. the SharePoint web-site, determine Internet site Actions (within the upper-left hand corner), then click Online site Settings. Beneath the ################## heading, find Site Subject material Types. Click on on Document to edit its material kind. Choose Add from present webpage columns. During the On hand Columns list, identify Position and click on Add to add it for the record of columns to add. Be aware: If Position can't be discovered, it could currently are actually extra to your content type. Click on Ok. Creating the Venture
First,Windows 7 Professional Serial, we design a SharePoint undertaking in Visual Studio that will include our workflow code. Visual Studio 2010 as an administrator. Note: You need to begin Visual Studio as an administrator so that you can effectively publish the undertaking to the SharePoint farm. Under the File menu, go for New, after which Project… Within the New Task dialog box, pick out the Visual C# SharePoint 2010 challenge form. Decide upon Sequential Workflow through the template record. Give the venture a identify (e.g. ArchiveDocument). Click Ok to create the challenge. When asked, choose to Deploy as being a farm treatment. Be aware: This is certainly necessary since the Word Automation Services object model cannot be accessed from partially trusted code. About the up coming phase, give the workflow a friendly title, e.g. "Archive Document" and go for Checklist Workflow because the workflow sort. Depart the default association settings, and click Next. Notice: If you would like to attach the workflow to a particular listing, change the Record drop-down to that listing. During this tutorial, we will use the default Shared Documents record on the SharePoint website. Uncheck "On merchandise creation" inside the default settings for workflow initiation (leaving "Manually" since the only picked worth), and click on End.
At this stage, we now possess a new empty workflow undertaking. on the Word Automation Providers Object Model
To carry out conversions, we have to include a reference on the Word Automation Companies object model. the Answer Explorer window, right-click on References and decide on Add Reference… Browse to discover the reference implementing the Browse tab. The Microsoft.Office.Word.Server.dll assembly is found while in the SharePoint Server 2010 ISAPI folder, generally positioned at C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\ISAPI.
Ok to add the reference.
Note: If you happen to get a warning the DLL involves a newer model with the .NET Framework, find Indeed to add the reference anyway. Then, add a reference to Procedure.Web site.DataVisualization, traditionally positioned at C:\windows\Assembly\GAC_MSIL\System.Website.DataVi sualization\3.five.0.0__31bf3856ad364e35\. Workflow
Now that we've got a workflow challenge, we are going to add a two-step workflow: the initial stage checks no matter whether the Status property has long been set to "Final"; the moment it's got, the second phase converts the document. Look at the Standing Residence Through the Toolbox, below Windows Workflow v3.0, add a Even when exercise soon after the existing onWorkflowActivated exercise. In the Toolbox, under SharePoint Workflow, add an OnWorkflowItemChanged activity inside of the Even when exercise. Click on around the OnWorkflowItemChanged exercise. Through the Attributes window, set the worth of the CorrelationToken house to workflowToken (the sole item within the drop-down list).
tells the activity the knowledge needed to associate the ItemChanged function together with the appropriate workflow. Attributes window, click on about the lightning bolt to change to Events see, and press ENTER inside the Invoked procedure to make a blank occasion handler. This event handler will undoubtedly be triggered when the item changes. During the code window, add a global Boolean worth to track no matter whether the Status home continues to be set on the wanted worth:
bool documentReady = bogus; the function handler, add code to examine the value of the column, and set the documentReady variable appropriately:
//check when the Status is set to final; in that case, the document is ready to archive
if (workflowProperties.Item["Status"] != null)
_documentReady = ((string)workflowProperties.Item["Status"] == "Final");
to your workflow designer window. Notice: It will have a very title like Workflow.cs [Design]. Click on about the Whilst activity. From the attributes window, click on on Condition and pick Declarative Rule Condition. Expand the Condition field, exposing ConditionName and Expression:
the ConditionName field, give the condition a title, e.g. Able to Archive. Click on from the Expression field, and press the button to set the condition. During 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 for the workflow that waits for the column worth to be set to Final, we add the workflow activity to truly convert the document. the Toolbox, below Windows Workflow v3.0, add a Code exercise soon after the current Though activity. In the Properties window, click on the lightning bolt to change to Activities view, and press ENTER within the ExecuteCode process to produce a blank celebration handler. This occasion handler could be triggered every time the merchandise improvements. Inside event handler, add code to complete the conversion:
//create a conversion job
ConversionJob job = new ConversionJob("Word Automation Services"); settings
job.UserToken = workflowProperties.OriginatorUser.UserToken;
if (workflowProperties.Web site.SiteSubscription != null)
job.SubscriptionId = workflowProperties.Web-site.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.Commence(); code creates a brand new ConversionJob, which defines a set of conversions, supplying the name for the company application. Notice: This illustration assumes the identify from the service application is "Word Automation Services", which is the default name when it is created via the Farm Configuration Wizard. If you happen to have used a different name for that services application, transform the title as appropriate. set the needed settings for that conversion: UserToken residence, 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 on the online site. Notice: This parameter is only expected when the SharePoint farm has been configured in partitioned mode. The OutputFormat house, which specifies the output file format for the conversion.
As well, we specify one optional setting: Name home, which specifies a friendly identify for that conversion.
Next, we add the file on the conversion job via the AddFile approach, and commence the processing with the conversion implementing the Start off methodology. workflow now looks like: Phase 3: Keep track of the Conversion
Once we've scheduled the conversion, it happens to be processed asynchronously. Finally, we will add a action to check the result of the conversion previous to terminating the workflow, so that the workflow completes just after the conversion. the Toolbox,Windows 7 Enterprise 64bit, below Windows Workflow v3.0, add a Whilst activity soon after the present codeActivity exercise. From the Toolbox, under Windows Workflow v3.0, add a Sequence activity inside the Whereas exercise. Through the Toolbox, below Windows Workflow v3.0, add a Delay activity within the Sequence activity. Click on the new codeActivity exercise. From the Attributes window, click on around the TimeoutDuration property and set it to 00:00:30 (30 seconds). This means the workflow will be re-checked at most every 30 seconds. Note: As a result of delays in SharePoint workflows are processed utilising a timer job with a default frequency of 5 minutes, it may take up to 4:59 for that delay to be processed. From your Toolbox, below Windows Workflow v3.0, add a Code activity right after the Delay exercise. Click on about the new codeActivity activity. In the Properties window, click on about the lightning bolt to change to Activities watch, and press ENTER while in the ExecuteCode system to produce a blank function handler. This occasion handler are going to be triggered when the item alterations. Inside code window, add two world wide variables: a Guid value to shop the ID with the conversion, to ensure that we are able to verify it on regular intervals, and a Boolean to track regardless of whether the conversion completed effectively:
Guid jobId;
bool conversionComplete = ########; the very first code process, save the ID in the conversion job into this world wide variable, by adding the following code soon after the Start methodology:
//save the job's ID
jobId = job.JobId; the new occasion handler (created in Stage 6), add code to verify the status of the conversion:
//monitor the conversion
//get the page subscription ID
Guid? siteSubscription = null;
if (workflowProperties.Web page.SiteSubscription != null)
siteSubscription = workflowProperties.Web-site.SiteSubscription.Id; the conversion is complete; if it truly is, refresh
ConversionJobStatus standing = new ConversionJobStatus("Word Automation Services", jobId, siteSubscription);
if (position.Count == status.Succeeded)
//success!
conversionComplete = true;

else if (standing.Count == status.Failed)
//conversion failed
ReadOnlyCollection<ConversionItemInfo> failedItems = status.GetItems(ItemTypes.Failed);
throw new Exception(failedItems[0].ErrorMessage);

else if (status.Count == position.Canceled)

//conversion was canceled
throw new Exception("Conversion was canceled.");
didn't complete, keep waiting checks the status of the conversion using the ConversionJobStatus object. Note: This example assumes the title for the services application is "Word Automation Services", which is the default title when it really is created via the Farm Configuration Wizard. Should you have used a different identify for that service application, switch the title as appropriate. have the position for your job, we are able to examine regardless if the merchandise has succeeded or failed, and react accordingly. Otherwise,Office 2007 Pro Plus Activation Key, we do nothing, since the conversion is still in progress. on the workflow designer window. Note: It will possess a name like Workflow.cs [Design]. Click around the Even though exercise. Through the attributes window, click on on Condition and find Declarative Rule Condition. Expand the Condition field, exposing ConditionName and Expression:
the ConditionName field, give the condition a identify, e.g. Conversion Complete. Click inside Expression field, and press the button to set the condition. During the dialog box, style the following condition:
conversionComplete == false to save the condition.
The last workflow will need to look and feel like this: Deploy the Remedy
Now, deploy the answer to your SharePoint farm. the Assemble menu, choose Deploy Solution to create the code and deploy it to SharePoint. From the Shared Documents library (or whichever library you chose in Phase 9 of Establishing the Task), upload a fresh Word document to start the workflow. Right-click on the new document and select Workflows. Click on on Archive Document to get started the workflow. Right-click on the new document and find Edit Properties. Set the Position residence to Ultimate. Press Ok.
When the timer job runs and the conversion is processed, you ought to see the XPS file appear up coming for the original document (refresh the page to see the result). Notice: Again,Windows 7 Activation Key, since the conversions are processed applying a timer job, it might take up to the frequency on the timer job for the file to appear.