My jongste artikel is op www.sharepointbriefing.com. Hier is 'n teaser:

Lees die hele ding hier: http://sharepointbriefing.com/features/article.php/3874226/Content-Query-Web-Part-SharePoints-Swiss-Army-Knife.htm

Sien dit in 'n ware publieke webwerf hier deur die volgende stappe:

1. Gaan na die webblad: http://cdi-its.com/Pages/Customer_Support.aspx (Dit is die kliënt ondersteuning bladsy vir CDI).
2. Klik op "Case Studies" in die linkerhand navigasie.

Dit sal spring na die "Customer Support"-afdeling van die gevallestudies lys.

</einde>

Skryf in op my blog.

Volg my op Twitter http://www.twitter.com/pagalvin

One of my clients worked with a previous contractor to build out a small but useful HR application for the enterprise. That contractor used SharePoint Designer to implement the workflow portion of the solution. It’s a bit of a mess. Byvoorbeeld, there are nine SPD workflows in support of a single logical workflow process and up to five of them may fire simultaneously at any given time given the right conditions. It’s not easy to debug 🙂

My kliënt het 'n aantal steeds uitstaande vereistes, one of which is to generally provide more context when the system sends out email alerts – both in the email itself as well as associated task forms. As SPD workflow implementers know, the “collect data from user” SPD action actually creates a task with a custom content type. When we use that action, we don’t get to specify much. We can prompt for some values (bijv. "Goedgekeur" of "ontken") and we can specify a hard coded value in the title and description. That’s about it.

My kliënt se behoefte is tweeledig:

1. Wanneer SharePoint stuur 'n e-pos oor 'n taak te voltooi, 'n baie inligting oor die taak in die e-liggaam.
2. Meer belangrik, by verre – Wanneer die gebruiker op die taak skakel in die e-pos, the task form should have all the information the approver needs in order to make his/her approve or deny decision. Right now, the manager needs to click on the item link itself to drill down into the underlying details and no one likes that. You have to click in the email. Then you need to click a sort of obscure link on the task item. Then you can look at the underlying data (n Path vorm in hierdie geval). Then you click back/back, ens.. Everyone hates it.

Ek het hierdie ietwat slordig tegniese oplossing geërf, en ek wil die veranderinge in die minste indringende manier moontlik te maak.

The approach I’m taking right now is to create a custom alert template. Jy kan lees oor wat hier. The flow works like this:

• SPD workflow lopies.
• Op 'n sekere punt, dit ken 'n taak om 'n bestuurder.
• SharePoint system automatically sends out an alert to that manager. This is not part of the SPD workflow but rather “what SharePoint does.” (Die SharePoint timer, Ek glo).
• 'N persoonlike waarskuwing hanteerder wat opgeroep word ten gunste van die standaard wakker proses (volgende magie reëls soos beskryf in die hierbo vermelde artikel).
• Wanneer my persoonlike wakker hanteerder loop, it generates a beautiful email. Meer belangrik, aangesien dit die taak in die hand, versier dit ook die taak met al die konteks inligting wat nodig is om die vereistes te voldoen.
• Die gebruiker kry die e-pos en dit is vol nuttige inligting oor konteks..
• Gebruiker op die taak skakel en die taak self is vol nuttige inligting oor konteks.
• Almal gaan huis waatlemoen en roomys te hê.

I did a quick POC and it works well in a lab environment. I get my custom email alert as expected. I also get to update the task description and title itself.

Die enigste moeilike bietjie, so ver, is 'n situasie te vermy waar die waarskuwing updates die item, triggering another alert. This doesn’t worry me.

Lyk belowend so ver ...

The great thing about this is that I don’t need to muck about with any of the existing SPD workflows. They are blissfully unaware that an alert handler is “IIZ hardloop in da BAKGROUND, DECORATIN TEH Takenlijst WIF MOAR konteks".

</einde>

Skryf in op my blog.

Volg my op Twitter http://www.twitter.com/pagalvin

[Let daarop: Ek wil dadelik sê dat ek 'n finansiële belang in die verlangde uitkoms van hierdie demonstrasie, wat ek noem in die belang van 'n volledige openbaarmaking, ens.. This is actually the first time I’ve ever blogged about an event where I stand to benefit personally in this way.]

Hierdie web demonstrasie plaasvind Donderdag, 06/04 op 12:30 EDT, eindig by 1:30PM EDT.

In samewerking met my uitstekende sakevennoot, Geïntegreerde stelsels en Services Group (ISSG), I have been working to develop a vertical business application using SharePoint as the platform. In hierdie geval, we’re building an application that serves the needs of manufacturers that make customized product for their customers. In these cases, a great deal of collaboration needs to take place between the customer and the manufacturer. There’s also a great deal of collaboration required between different groups within the manufacturer, insluitend verkope, ingenieurswese, navorsing en ontwikkeling, regs-en ander groepe.

Die demo gaan 'n aansoek wat fasiliteer dat die soort van samewerking te wys, saam met 'n bespreking oor hoe om al die stukkies samewerking nodig het om te integreer met 'n backend ERP-stelsel.

Laastens, this isn’t going to be a SharePoint demo. This is a demonstration of a solution for a specific niche problem that happens to use SharePoint as the platform.

So, hoekom sou jy die moeite om aan te meld en kyk na hierdie demo? I don’t expect too many readers of my blog to be all that interested in a solution for make-to-order manufacturers 🙂 Your take-away would be the concept itself – using SharePoint purely to deliver a business solution without regard to SharePoint itself.

As jy belangstel, teken asseblief hier(https://www323.livemeeting.com/lrs/8000043750/Registration.aspx?pageName=skmqfwbr5smmlx20).

</einde>

Skryf in op my blog.

Volg my op Twitter http://www.twitter.com/pagalvin

My nuutste artikel is by www.EndUserSharePoint.com. I wrote about SharePoint Designer, Eindgebruikers en die uiteensetting van 'n strategie dat Eindgebruikers kan probeer volg om bevoegdheid te demonstreer en die bou van vertroue om hierdie hulpmiddel.

Die kommentaar is meer interessant as die artikel self.

Check dit uit.

</einde>

Skryf in op my blog.

Volg my op Twitter http://www.twitter.com/pagalvin

Op my huidige projek, sommige van die gebruikers sal reis regoor die wêreld, en wanneer hulle kom op verskillende bestemmings, use whatever machine is handy at the time. Those guest machines will be running Windows and installed and configured for the local locale. (Ek het net besef dat die gaste masjiene nie kan het die reg om taal pakkette… sal waarskynlik nie, in werklikheid… Ek parkeer dat 'n mens vir nou).

SharePoint needs to provide a mechanism whereby the user can pick their preferred language and then have MOSS honor that language regardless of how the user accesses MOSS. In other words, disregard whatever the browser tells IIS/MOSS and instead look up that preferred language and use it.

Ons gaan twee benaderings te ondersoek:

1. HTTP Handler: 'N persoonlike HTTP hanteerder geïnstalleer op IIS sal kyk op die gebruiker se mos profiel, die taal van voorkeur en dan skakel die HTTP-kop rond soos nodig voordat beheer te MOSS.
2. Global.asax: Modify global.asax to do the same thing. We may modify something else, but the idea is that we find some place where we can insert our locale-switching logic.

Die ander kompliserende faktor is dat ons moet 60k gebruikers te ondersteun, oor 1,000 wat gelyktydig toegang tot spitslas word mos.

Die HTTP-hanteerder lyk redelik drastiese, but possibly the best place to put the code since it’s at the IIS level and all-knowing. It’s a good single point of work.

Ons leun na 'n Global.asax tipe benadering, hoofsaaklik omdat ons glo dat ons meer opsies vir die kas van data sal op daardie stadium.

Ek sal blog meer oor hierdie onderwerp as ek meer inligting.

As jy weet niks oor hierdie, please post a comment 🙂

</einde>

Skryf in op my blog.

Volg my op Twitter http://www.twitter.com/pagalvin