Hoe kan ik een email van WebPart in MOSS Stuur 2007

Hi Devs,
Het volgende is het stukje code naar e-mail verzenden vanaf webpart.

met behulp van Systeemherstel;
met behulp van System.Collections.Generic;
met behulp van System.ComponentModel;
met behulp van System.Text;
met behulp van System.Web;
met behulp van System.Web.UI;
met behulp van System.Web.UI.WebControls;
met behulp van System.Collections.ObjectModel;
met behulp van Microsoft.SharePoint.Utilities;
met behulp van Microsoft.SharePoint;
met behulp van System.Data;
met behulp van System.Collections;
namespace SendMail
{
public class SendMail : Microsoft.SharePoint.WebPartPages.WebPart
{
particuliere TextBox txtTo;
prive-knop btnSendMail;
beschermd override void CreateChildControls()
{
txtTo = new TextBox();
this.Controls.Add(txtTo);
btnSendMail = new Button();
btnSendMail.Text = “E-mail”;
btnSendMail.Click = new EventHandler(SendMail_Click);
this.Controls.Add(btnSendMail);
}
void SendMail_Click(object sender, EventArgs e)
{
SPSite _site = nieuwe SPSite(HttpContext.Current.Request.Url.ToString());
SPWeb _web = _site.OpenWeb();
_web.AllowUnsafeUpdates = true;
SPUtility.SendEmail(_web, valse, valse, txtTo.Text, “Test E-mail”, “Tekst Body Bericht”);
_web.Dispose();
_site.Dispose();
}
}
}

Maak de WebPart en registreren als SafeControl

MOSS 2007 Prijsstelling & Costing Info

Ik heb geconsolideerd paar links van Microsoft voor MOSS 2007 Product Costing.

Microsoft Office SharePoint Server 2007 en aanverwante technologieën prijzen

Microsoft Office SharePoint Server 2007 producten vergelijking te downloaden

2007 Microsoft Office-systeem prijzen en upgrade-informatie

Hoe kan ik Snel starten in MOSS Verberg 2007

Wilt u uw snelle lancering Bar verbergen in MOSS 2007
Er zijn twee manieren om de Quick Launch balk te verbergen
1. U kunt direct bewerken in CSS
2. Het toevoegen van verborgen content editor webpart

Toevoegen van nieuwe content editor webpart
Klik Source Editor in ToolPane
plak de onderstaande code in content editor webpart
[stijl]
.ms-QuickLaunch
{
tonen:geen;
}
.ms-navframe
{
tonen: geen;
}
[/stijl]
Gebruik “<" & ">” in plaats van “[” & “]”
Stel de Verborgen Property op True onder lay-sectie in ToolPane.
Nu Vernieuw de pagina……You Quick Launch Bar is Gone 🙂

Presentator in de Shaping the Future Workshop

Ik presenteerde de Demo op de architectuur van gedistribueerde applicaties met behulp van Grid Architecture in Accenture Shaping the Future workshop. Dit is mijn tweede presentatie in Accenture Shaping the Future.

Hoe MOSS Force 2007 Timer Jobs Execute

Gebruik de volgende stadm opdracht te dwingen de timer banen banen uit te voeren.
hoeft niet te wachten voor de interval om de timerjobs uit te voeren.
stsadm.exe-o execadmsvcjobs

MOSS 2007 De naam van de Web Application Naam

Ik wil om te delen hoe de webapplicatie naam in de command line beheer van MOSS hernoemen 2007 met behulp van stsadm Command.

Syntaxis:
stsadm-o renameweb-url-newname

Voorbeeld:
Stsadm-o-renameweb url http://localhost / oldname-newname newname

Het bovenstaande commando zal de naam van de webapplicatie van oudenaam aan de newname.

Commerce Server 2007 Integratie met MOSS 2007

MOSS heeft veel ingebouwde functies. De werkingssfeer van deze POC is het integreren van Commerce Server 2007 met MOSS 2007 Portal geïntegreerde e-commerce applicatie te bieden

Configureren van MOSS 2007 aan de Commerce Server Membership Provider gebruiken als basis voor User Authentication

The primary tasks are to make the Central Administration and Portal sites hand-shake with Commerce Server. This needs to be done by modifying the appropriate Web.config files for these sites. By adding the Commerce Server and httpModules sections, the SharePoint Central Administration site and the Portal site will be able to create the necessary CommerceContext object. The CommerceContext object enables the Commerce Server Membership Provider to be initialized correctly, and also enables Web parts and pages in the portal to use the CommerceContext object to access Commerce Server resources such as the Product Catalog.
The UpmMembership Provider extends the Membership framework offered by ASP.Net to accommodate the use of the ASP.Net Login Controls and authenticate against Commerce Server Profiles.

Update the Web.config for MOSS Central Administration and in Portal site with below sections to avail Commerce Server data and services in MOSS

  • Commerce Server Section Group
  • Commerce Server Group
  • Http Modules
  • Assemblies
  • Membership Provider
  • Profile Section

o Determine which Web.config file is used for the SharePoint Central Administration site and which is used for the Portal site. Use the Home Directory tab in IIS Manager to determine the appropriate path of the Web.config file for each site.

o Use the Web.config file that was previously created for the Commerce Server C SharpSite as the source for the text to copy in the following instructions:

Please follow the below steps to modify the web.config file of SharePoint administration site.

Step 1: Adding Commerce Server Section Group
Copy the Commerce [sectionGroup] in [configSections] and paste it after the [System.Workflow.ComponentModel.WorkflowCompiler] section group.
[sectionGroup name=”CommerceServer”]
[section name=”application” type=”Microsoft.CommerceServer.Runtime.Configuration.CommerceApplicationSectionHandler, Microsoft.CommerceServer.Runtime, Version=6.0.1.0, Culture = neutral, PublicKeyToken=31bf3856ad364e35″/]
[section name=”authentication” type=”Microsoft.CommerceServer.Runtime.Configuration.CommerceAuthenticationSectionHandler, Microsoft.CommerceServer.Runtime, Version=6.0.1.0, Culture = neutral, PublicKeyToken=31bf3856ad364e35″/]
[section name=”pipelines” type=”Microsoft.CommerceServer.Runtime.Configuration.CommercePipelineSectionHandler, Microsoft.CommerceServer.Runtime, Version=6.0.1.0, Culture = neutral, PublicKeyToken=31bf3856ad364e35″/]
[section name=”caches” type=”Microsoft.CommerceServer.Runtime.Configuration.CommerceCacheSectionHandler, Microsoft.CommerceServer.Runtime, Version=6.0.1.0, Culture = neutral, PublicKeyToken=31bf3856ad364e35″/]
[section name=”messageManager” type=”Microsoft.CommerceServer.Runtime.Configuration.CommerceMessageManagerSectionHandler, Microsoft.CommerceServer.Runtime, Version=6.0.1.0, Culture = neutral, PublicKeyToken=31bf3856ad364e35″/]
[section name=”catalog” type=”Microsoft.CommerceServer.Runtime.Configuration.CommerceCatalogSectionHandler, Microsoft.CommerceServer.Runtime, Version=6.0.1.0, Culture = neutral, PublicKeyToken=31bf3856ad364e35″/]
[section name=”orders” type=”Microsoft.CommerceServer.Runtime.Configuration.CommerceOrdersSectionHandler, Microsoft.CommerceServer.Runtime, Version=6.0.1.0, Culture = neutral, PublicKeyToken=31bf3856ad364e35″/]
[section name=”profiles” type=”Microsoft.CommerceServer.Runtime.Configuration.CommerceProfilesSectionHandler, Microsoft.CommerceServer.Runtime, Version=6.0.1.0, Culture = neutral, PublicKeyToken=31bf3856ad364e35″/]
[section name=”contentSelection” type=”Microsoft.CommerceServer.Runtime.Configuration.CommerceContentSelectionSectionHandler, Microsoft.CommerceServer.Runtime, Version=6.0.1.0, Culture = neutral, PublicKeyToken=31bf3856ad364e35″/]
[section name=”commerceEvent” type=”Microsoft.CommerceServer.Runtime.Configuration.EventLoggerConfigurationHandler, Microsoft.CommerceServer.Runtime, Version=6.0.1.0, Culture = neutral, PublicKeyToken=31bf3856ad364e35″/]
[section name=”expressions” type=”Microsoft.CommerceServer.Runtime.Configuration.CommerceExpressionSectionHandler, Microsoft.CommerceServer.Runtime, Version=6.0.1.0, Culture = neutral, PublicKeyToken=31bf3856ad364e35″/]
[/sectionGroup]
Step 2: Adding Commerce Server Group
§ Copy the [CommerceServer] section and paste it after the [SharePoint] rubriek, just before the [system.web] rubriek.

[CommerceServer]
[application siteName=”CDevSite” debugLevel=”Production”/]
[pipelines][/pipelines]
[expressions schema=”Auto”/]
[caches]
[cache name=”Reclame” type=”Reclame” refreshInterval=”900″ retryInterval=”30″/]
[cache name=”Discounts” type=”Discounts” refreshInterval=”0″ retryInterval=”30″/]
[cache name=”ShippingManagerCache” type=”Shipping” loaderProgId=”Commerce.ShippingMethodCache” refreshInterval=”0″ retryInterval=”30″/]
[cache name=”PaymentMethodCache” type=”Payment”/]
[cache name=”OrdersConfigurationCache” type=”OrdersConfiguration”/]
[/caches]
[messageManager]
[cultures default=”en-US” baseName=”CommerceMessageManager” assembly=”CommerceMessageManager”]
[culture id=”en-US”/]
[culture id=”fr-fr”/]
[culture id=”ja-JP”/]
[culture id=”de-DE”/]
[/cultures]
[resources]
[resource id=”pur_badsku”/]
[resource id=”pur_badplacedprice”/]
[resource id=”pur_discount_changed”/]
[resource id=”pur_discount_removed”/]
[resource id=”pur_noitems”/]
[resource id=”pur_badshipping”/]
[resource id=”pur_badhandling”/]
[resource id=”pur_badtax”/]
[resource id=”pur_badcc”/]
[resource id=”pur_badpayment”/]
[resource id=”pur_badverify”/]
[resource id=”pur_out_of_stock”/]
[resource id=”unknown_shipping_method”/]
[/resources]
[/messageManager]
[orders honorStatus=”ware” newOrderStatus=”NewOrder” sqlCommandTimeoutSeconds=”60″ sqlLongRunningCommandTimeoutSeconds=”28800″]
[addressMap]
[profileDefinition name=”Adres”/]
[property from=”GeneralInfo.address_id” to=”OrderAddressId”/]
[property from=”GeneralInfo.first_name” to=”Voornaam”/]
[property from=”GeneralInfo.last_name” to=”Achternaam”/]
[property from=”GeneralInfo.address_line1″ to=”Line1″/]
[property from=”GeneralInfo.address_line2″ to=”Line2″/]
[property from=”GeneralInfo.city” to=”City”/]
[property from=”GeneralInfo.region_code” to=”RegionCode”/]
[property from=”GeneralInfo.postal_code” to=”PostalCode”/]
[property from=”GeneralInfo.country_name” to=”CountryName”/]
[property from=”GeneralInfo.region_name” to=”Staat”/]
[property from=”GeneralInfo.tel_number” to=”DaytimePhoneNumber”/]
[/addressMap]
[Types]
[Type Key=”Basket” UserTypeName=”Basket” AssemblyType=”GAC” NameSpace=”Microsoft.CommerceServer.Runtime.Orders” Assembly=”Microsoft.CommerceServer.Runtime, Version=6.0.1.0, Culture = neutral, PublicKeyToken=31bf3856ad364e35″/]
[Type Key=”PurchaseOrder” UserTypeName=”PurchaseOrder” AssemblyType=”GAC” NameSpace=”Microsoft.CommerceServer.Runtime.Orders” Assembly=”Microsoft.CommerceServer.Runtime, Version=6.0.1.0, Culture = neutral, PublicKeyToken=31bf3856ad364e35″/]
[Type Key=”OrderTemplate” UserTypeName=”OrderTemplate” AssemblyType=”GAC” NameSpace=”Microsoft.CommerceServer.Runtime.Orders” Assembly=”Microsoft.CommerceServer.Runtime, Version=6.0.1.0, Culture = neutral, PublicKeyToken=31bf3856ad364e35″/]
[Type Key=”OrderForm” UserTypeName=”OrderForm” AssemblyType=”GAC” NameSpace=”Microsoft.CommerceServer.Runtime.Orders” Assembly=”Microsoft.CommerceServer.Runtime, Version=6.0.1.0, Culture = neutral, PublicKeyToken=31bf3856ad364e35″/]
[Type Key=”LineItem” UserTypeName=”LineItem” AssemblyType=”GAC” NameSpace=”Microsoft.CommerceServer.Runtime.Orders” Assembly=”Microsoft.CommerceServer.Runtime, Version=6.0.1.0, Culture = neutral, PublicKeyToken=31bf3856ad364e35″/]
[Type Key=”Shipment” UserTypeName=”Shipment” AssemblyType=”GAC” NameSpace=”Microsoft.CommerceServer.Runtime.Orders” Assembly=”Microsoft.CommerceServer.Runtime, Version=6.0.1.0, Culture = neutral, PublicKeyToken=31bf3856ad364e35″/]
[Type Key=”Payment” UserTypeName=”Payment” AssemblyType=”GAC” NameSpace=”Microsoft.CommerceServer.Runtime.Orders” Assembly=”Microsoft.CommerceServer.Runtime, Version=6.0.1.0, Culture = neutral, PublicKeyToken=31bf3856ad364e35″/]
[Type Key=”CreditCardPayment” UserTypeName=”CreditCardPayment” AssemblyType=”GAC” NameSpace=”Microsoft.CommerceServer.Runtime.Orders” Assembly=”Microsoft.CommerceServer.Runtime, Version=6.0.1.0, Culture = neutral, PublicKeyToken=31bf3856ad364e35″/]
[Type Key=”GiftCertificatePayment” UserTypeName=”GiftCertificatePayment” AssemblyType=”GAC” NameSpace=”Microsoft.CommerceServer.Runtime.Orders” Assembly=”Microsoft.CommerceServer.Runtime, Version=6.0.1.0, Culture = neutral, PublicKeyToken=31bf3856ad364e35″/]
[Type Key=”PurchaseOrderPayment” UserTypeName=”PurchaseOrderPayment” AssemblyType=”GAC” NameSpace=”Microsoft.CommerceServer.Runtime.Orders” Assembly=”Microsoft.CommerceServer.Runtime, Version=6.0.1.0, Culture = neutral, PublicKeyToken=31bf3856ad364e35″/]
[Type Key=”CashCardPayment” UserTypeName=”CashCardPayment” AssemblyType=”GAC” NameSpace=”Microsoft.CommerceServer.Runtime.Orders” Assembly=”Microsoft.CommerceServer.Runtime, Version=6.0.1.0, Culture = neutral, PublicKeyToken=31bf3856ad364e35″/]
[Type Key=”OrderAddress” UserTypeName=”OrderAddress” AssemblyType=”GAC” NameSpace=”Microsoft.CommerceServer.Runtime.Orders” Assembly=”Microsoft.CommerceServer.Runtime, Version=6.0.1.0, Culture = neutral, PublicKeyToken=31bf3856ad364e35″/]
[Type Key=”DiscountApplicationRecord” UserTypeName=”DiscountApplicationRecord” AssemblyType=”GAC” NameSpace=”Microsoft.CommerceServer.Runtime.Orders” Assembly=”Microsoft.CommerceServer.Runtime, Version=6.0.1.0, Culture = neutral, PublicKeyToken=31bf3856ad364e35″/]
[Type Key=”ShippingDiscountRecord” UserTypeName=”ShippingDiscountRecord” AssemblyType=”GAC” NameSpace=”Microsoft.CommerceServer.Runtime.Orders” Assembly=”Microsoft.CommerceServer.Runtime, Version=6.0.1.0, Culture = neutral, PublicKeyToken=31bf3856ad364e35″/]
[Type Key=”PromoCodeRecord” UserTypeName=”PromoCodeRecord” AssemblyType=”GAC” NameSpace=”Microsoft.CommerceServer.Runtime.Orders” Assembly=”Microsoft.CommerceServer.Runtime, Version=6.0.1.0, Culture = neutral, PublicKeyToken=31bf3856ad364e35″/]
[/Types]
[Limits OrderFormsPerOrderGroup=”5″ PromoCodeRecordsPerOrderForm=”10″ PromoCodesPerOrderForm=”10″ LineItemsPerOrderForm=”40″ OrderTemplatesPerUser=”10″ PaymentsPerOrderForm=”10″ ShipmentsPerOrderForm=”40″ BasketsPerUser=”15″ OrderAddressesPerOrderGroup=”10″/]
[MappingFiles PipelineMappingFilename=”OrderPipelineMappings.xml” StorageMappingFilename=”OrderObjectMappings.xml”/]
[SerializationBindings]
[SerializationBinding OldType=”Microsoft.CommerceServer.Runtime.Orders.LineItem , Microsoft.CommerceServer.Runtime ,Version=6.0.1.0,Culture=neutral, PublicKeyToken=31bf3856ad364e35″ NewType=”Microsoft.CommerceServer.Runtime.Orders.LineItem, Microsoft.CommerceServer.Runtime,Version=6.0.1.0,Culture=neutral, PublicKeyToken=31bf3856ad364e35″/]
[/SerializationBindings]
[/orders]
[commerceEvent]
[add className=”Microsoft.CommerceServer.Runtime.AddItemToBasketEvent” id =”AddItemToBasket”/]
[add className=”Microsoft.CommerceServer.Runtime.RemoveItemFromBasketEvent” id =”RemoveItemFromBasket”/]
[add className=”Microsoft.CommerceServer.Runtime.SubmitOrderEvent” id =”SubmitOrder” loggingEnabled=”ware”/]
[/commerceEvent]
[/CommerceServer]
Step 3: Adding “CommerceApplication” in “httpModules” Section
§ Copy the Commerce HTTP Modules to the end of the [httpModules] rubriek.
[add name=”CommerceApplication” type=”Microsoft.CommerceServer.Runtime.CommerceApplicationModule, Microsoft.CommerceServer.Runtime, Version=6.0.1.0, Culture = neutral, PublicKeyToken=31bf3856ad364e35″/]
[add name=”CommerceAuthentication” type=”Microsoft.CommerceServer.Runtime.CommerceAuthenticationModule, Microsoft.CommerceServer.Runtime, Version=6.0.1.0, Culture = neutral, PublicKeyToken=31bf3856ad364e35″/]
[add name=”CommerceOrder” type=”Microsoft.CommerceServer.Runtime.Orders.CommerceOrderModule, Microsoft.CommerceServer.Runtime, Version=6.0.1.0, Culture = neutral, PublicKeyToken=31bf3856ad364e35″/]
[add name=”CommerceCatalog” type=”Microsoft.CommerceServer.Runtime.Catalog.CommerceCatalogModule, Microsoft.CommerceServer.Runtime, Version=6.0.1.0, Culture = neutral, PublicKeyToken=31bf3856ad364e35″/]
[add name=”CommerceProfile” type=”Microsoft.CommerceServer.Runtime.Profiles.CommerceProfileModule, Microsoft.CommerceServer.Runtime, Version=6.0.1.0, Culture = neutral, PublicKeyToken=31bf3856ad364e35″/]
[add name=”CommerceExpressionEvaluator” type=”Microsoft.CommerceServer.Runtime.Targeting.CommerceExpressionModule, Microsoft.CommerceServer.Runtime, Version=6.0.1.0, Culture = neutral, PublicKeyToken=31bf3856ad364e35″/]
[add name=”CommerceCache” type=”Microsoft.CommerceServer.Runtime.Caching.CommerceCacheModule, Microsoft.CommerceServer.Runtime, Version=6.0.1.0, Culture = neutral, PublicKeyToken=31bf3856ad364e35″/]
[add name=”CommerceContentSelection” type=”Microsoft.CommerceServer.Runtime.Targeting.CommerceContentSelectionModule, Microsoft.CommerceServer.Runtime, Version=6.0.1.0, Culture = neutral, PublicKeyToken=31bf3856ad364e35″/][add name=”CommerceDataWarehouseAuthenticationModule” type=”Microsoft.CommerceServer.Runtime.CommerceDataWarehouseAuthenticationModule, Microsoft.CommerceServer.Runtime, Version=6.0.1.0, Culture = neutral, PublicKeyToken=31bf3856ad364e35″/]Remove or comment out the Commerce Server Authentication Module. This module is not required because ASP.NET Forms Authentication will be used for all authentications.
Step 4: Adding “Commerce Server” AssembliesCopy the commerce server assembly information from CSharpSite web.config and paste it in the [assemblies] tag in the Central Administration site’s web.config as below:
[assemblies]
[add assembly=”Microsoft.CommerceServer.Runtime, Version=6.0.1.0, Culture = neutral, PublicKeyToken=31bf3856ad364e35″ /]
[add assembly=”Microsoft.CommerceServer.Catalog, Version=6.0.1.0, Culture = neutral, PublicKeyToken=31BF3856AD364E35″ /][/assemblies]

Step 5: Configure Central Administration to recognize Commerce Server Membership
Copy the below code snippet to [system.web] section of the Web.config file for the Central Administration. Opmerking: Paste it before the closing [/system.web].
[membership defaultProvider=”UpmMembershipProvider”]
[providers]
[clear /]
[add applicationName=”CSharpSite ”
enablePasswordRetrieval=”valse”
enablePasswordReset=”ware”
requiresQuestionAndAnswer=”ware”
requiresUniqueEmail=”ware”
enableCreateDate=”ware”
enableEmailAddress=”ware”
enableLastLoginDate=”ware”
profileDefinition=”UserObject”
passwordFormat=”Hashed”
name=”UpmMembershipProvider”
type=”Microsoft.CommerceServer.Runtime.Profiles.UpmMembershipProvider”/]
[/providers]
[/membership]

Step 6: Configuring the Commerce Server Profiles section

This section contains settings which configure the functionality of profiles and catalog sets. Het [userProfile] node resides in the [CommerceServer][profiles] node in the web.config.
Uncomment the profiles section in [commerceserver] node.

[userProfile
profileDefinition=”UserObject”
userIdProperty=”GeneralInfo.email_address”
organizationIdProperty=”AccountInfo.org_id”
catalogSetIdProperty=”AccountInfo.user_catalog_set”
userIdSource = “ASP.NET”
userIdKey = “GeneralInfo.email_address”
userIdTarget = “GeneralInfo.user_id”
/]
[organizationProfile
profileDefintion=”Organization”
organizationIdProperty=”GeneralInfo.org_id”
catalogSetIdProperty=”GeneralInfo.org_catalog_set”
/]

Step 7: Adding Users in the Central AdministrationLocate Central Administration, Application Management, Authentication Providers, Default zone entry. Make sure that you have the PortalSite Web Application selected in the drop-down list.

o Click Forms.

o Change the Membership Provider Name to UpmMembershipProvider. This should match the name that is in the membership section of the Web.config file.Locate Central Administration, Application Management, and Policy for Web Application. Make sure that you have selected the Portal Web Application.

o Click Add Users.

o Select Default zone, and then click Next.

o Type the e-mail address of the user that you added previously by using the Commerce Server Customer and Orders Manager, and then click Check User.

o If the user name is successfully recognized, it will be underlined. Select Full control, and then select Finish.

o If the user name is not recognized, run a SQL Server trace on the Commerce Server Profiles database to make sure that the queries are running against the database. Additionally, make sure that the entry for the provider is in the Web.config file for Central Administration, and look for errors in the event log.

Step 8: Copy the following XML files from the CSharpSite (IIS Virtual Directory) to the root folder of the Central Administration site:

o OrderObjectMappings.xml
o OrderPipelineMappings.xml

Run Central Administration to make sure that these changes were made correctly. If errors occur, check the Web.config file for syntax issues.Even if the page displays correctly, check the event log. Some permissions errors may be hidden.

Configure the MOSS portal to use the Commerce Server Membership provider:
Step 1: Follow the above 6 steps to configure Portal site for Commerce Server.

Step 2: Comment out the existing [authentication], [identity], en [authorization] sections. This will disable the default Windows authentication and authorization.

Step 3: Copy the below configuration settings contents to the Web.config file for the Portal site. Paste this after the previous sections that you just commented out. This sets up the site for Forms Authentication and denies anonymous access.

[authentication mode=”Formulieren”]
[forms loginUrl=”/_layouts/login.aspx” name=”.ASPXFORMSAUTH” /]
[/authentication]
[authorization]
[deny users=”?” /][/authorization] View the Portal site in a Web browser. You should be redirected to the logon page. Log on and use the user credentials that you added by using the Customer and Orders Manager.

Step 4: Copy the following XML files from the CSharpSite (IIS Virtual Directory) to the root folder of the Portal site:

o OrderObjectMappings.xml
o OrderPipelineMappings.xml

Step 5: Restart the IIS

Step 6: Run the Portal site and look for errors.

[Opmerking : I am not able to Post scripts tag in here replace all “[” & “]” met “<" & ">“

Gratis Microsoft Press E-Books Aanbod voor LINQ,ASP.Net,Silverlight

De volgende E-boeken kunnen worden gedownload van Microsoft Press Site.

  • Introducing Microsoft LINQ
    by Paolo Pialorsi and Marco Russo
  • Introducing Microsoft ASP.NET AJAX
    by Dino Esposito
  • Introducing Microsoft Silverlight 1.0
    door Laurence Moroney

    http://csna01.libredigital.com

    Op de site inloggen met behulp van uw paspoort / id en hotmail downloaden e-boeken gratis.

Bill Gates laatste dag bij Microsoft

Bill Gates gaf zijn laatste CES keynote in(Consumer Electronic Show) in de laatste vegas.

you can find his full keynote in Microsoft CES

Goedkeuring van de inhoud Workflow in MOSS 2007

In MOSS 2007 Workflow voor goedkeuring is beschikbaar in out of the box zelf. We gewoon moeten vervolgens configureren slechts een paar stappen zijn we klaar met het goedkeuringsproces.

Als de workflow voor goedkeuring is geconfigureerd zal het document worden alleen zichtbaar voor de inbrenger en de fiatteur.

Stappen voor het configureren goedkeuringsworkflow

Open de documentbibliotheek
Klik op Instellingen -> Instellingen van documentbibliotheek


In Document Library Instellingen onder Machtigingen en beheer Klik Werkstroominstellingen

Document Library Settings -> [Toestemming en Management] Workflow Management

In MOSS 2007 het heeft een aantal vooraf gedefinieerde workflow templates voor de volgende workflows

  • Goedkeuring
  • Feedback verzamelen
  • Handtekeningen verzamelen
  • Goedkeuren voor bestemming
  • Drie Staat

Kies nu de workflow voor goedkeuring en geven de unieke naam voor de workflow bijvoorbeeld.
Selecteer de bestaande Task List Name of maak nieuwe takenlijst voor deze workflow voor goedkeuring.
Selecteer de bestaande geschiedenis of nieuwe workflow geschiedenis van deze workflow geschiedenis te behouden.
Onder Start opties kunt u aangeven hoe dit workflow kan worden gestart.

· Toestaan dat deze workflow handmatig worden gestart door een geverifieerde gebruiker met machtigingen Items bewerken
· Start deze workflow wanneer een item wordt gemaakt
· Start deze workflow wanneer een item wordt gewijzigd

Als u kiest voor "Start deze workflow wanneer een item wordt gemaakt" het zal automatisch begint workflow bij nieuw item is toegevoegd aan de documentbibliotheek.

Als u kiest voor "Start deze workflow wanneer een item wordt veranderd" het zal automatisch opnieuw opstarten van de workflow bij de items in de documentbibliotheek wordt gewijzigd.

Onder workflowtaak
Als u toewijzen Taak voor kiezen om "Alle deelnemers gelijktijdig" Het zal de taak voor alle deelnemers op hetzelfde moment. De workflow zal worden afgerond na de goedkeuring van alle fiatteurs.

Als u ervoor kiest toewijzen taak om "Een deelnemer op een moment" Het zal de volgorde van de activiteit eerst de workflow taak zal worden opgericht om de eerste gebruiker en een keer haar toenmalige slechts erkend zal gaan naar de volgende fiatteur.

Als het nodig is kunt u de vervaldatum voor de workflow.
De workflow-status kan ook worden aangemeld, andere dan de deelnemers van de workflow door het geven van de naam op kennis anderen kolom.

Wij zijn het creëren van de workflow voor goedkeuring van de inhoud. Dus vergeet niet de vink de optie "Update de goedkeuring status (Gebruik deze workflow om goedkeuring van inhoud controle)"

Nu kun je met succes aangemaakt goedkeuringsworkflow.

Je moet de goedkeuring van de inhoud in de documentbibliotheek dan staat het alleen zal beperken andere gebruikers om toegang te krijgen.

Wanneer u goedkeuring van de inhoud in staat het document wordt alleen zichtbaar voor de medewerker / auteur en goedkeurder, het zal niet zichtbaar zijn voor andere gebruikers in documentbibliotheek.

Open Instellingen -> Instellingen van documentbibliotheek
Onder Algemene Instellingen -> Instellingen voor versiebeheer
Goedkeuring van inhoud vereisen voor verzonden items? Kies Ja
En Klik op OK om de instellingen te bewaren.

Open nu de Document Library en het uploaden van het Document

Nu het document wordt geüpload de Document Library

Als u inloggen met behulp van een andere gebruiker diplomawaardering (niet een fiatteur / donateur). Het document zal worden weergegeven in de documentbibliotheek.

Als u denkt dit bericht helpt u bij het maken workflow voor het goedkeuren van inhoud. Laat uw waardevolle opmerkingen.