Category Archives: Octobris 2007

SharePoint amet — Consuetudo definitur actio facere user-C # functiones

UPDATE: Hoc dimissum est hic CodePlex: http://www.codeplex.com/spdwfextensions

UPDATE: Vide hic in notis tardus remissionis: http://paulgalvin.spaces.live.com/blog/cns!1CC1EDB3DAA9B8AA!381.entry

UPDATE: Hic meo cogitationes in commercializing hoc project: http://paulgalvin.spaces.live.com/blog/cns!1CC1EDB3DAA9B8AA!569.entry

This project provides a custom activity in SharePoint Designer. Use this custom activity to invoke (confodiantur) any C# function that you incorporated into the linked assembly.

Ut nuper October, 2007, this is just an initial version of the project. I plan to expand it with a number of additional functions, possidet substring, Index, restituo, invoking web services and anything that seems useful or interesting. I also plan to post this to codeplex once I have my act together on that front. This will also be deployable as a solution at some point.

Si vos have ullus ineo, vel quaestiones proponentibus, mihi comments in eis placere relinquere an email.

Disclaimer:

I make absolutely no claims as to the suitability of this for any purpose. Use at your own risk.

Gradibus instruitur (Quisque in agro sequi WFE):

1. Download. Zip et eruere,.

2. Install the .dll into the GAC. I usually open c:\fenestrae collectam usura Fenestra Rimor et non rescribatur.

3. Abilitates web.config adicere coetus ad imperium securum:

<System.Workflow.ComponentModel.WorkflowCompiler>
<authorizedTypes>

<authorizedType Assembly="SpdGenericInterface, Version = 1.0.0.0, Culturae = neutra, PublicKeyToken = abe076fd8125f3c4" Namespace="Nivlag" TypeName="*" Authorized="True" />

4. Copy "SpdGenericInterface.actions" C:\Progressio Lima Commune Lima Microsoft Communes meaning Maecenas lobortis XII Template MXXXIII workflow

Nota quod situm superius specificum anglicus Linguam installations.

5. Excogitatoris SharePoint Close (si suus 'iam patefacio).

6. iisreset

7. SPD et aperire novum workflow.

Si omnes bene, Retribuetur enim tibi novo genere actionis:

Notes:

Videte hic (http://blogs.msdn.com/sharepointdesigner/archive/2007/03/15/adding-activities-to-spd.aspx) pro ingenti overview of processus partum, Vestibulum et installing solutio huiusmodi.

In. Zip ordinatur directe ad vos can extraho:\ drive. If you do this, et omne consilium tui vias suas aperire futurum.

Uti hoc in Visual Bulla, you probably need to install "Extensions for Windows WF".

The initial upload contains just one "dispatcher function", "ToLower()". To add more functionality, adde Facite ostenditur ratione,:

 protegetur dominari ActivityExecutionStatus
          Fáciant(ActivityExecutionContext executionContext)
        {

            filum functionToDispatch;
            functionToDispatch = hoc.DispatchFunction.ToLower();

            switch (functionToDispatch)
            {
                casum "tolower()":
                    {
                        hoc.OutResult1 = hoc.InParam1.ToLower();
                        diruam;
                    }

                defaltam:
                    {
                        hoc.OutResult1 = "Unknown function: [" + hoc.DispatchFunction + "].";
                        diruam;
                    }
            }

            revertetur ActivityExecutionStatus.Concluserat;
        } // ActivityExecutionStatus

    }

Igitur, re-build the project and copy the assembly to the GAC. I expect an iisreset would be required.

SPD workflow consuetudinem actione – impetro <WorkflowInfo> tag ius ad vitare uanitate

Aliquam responsum

Part of the process for creating a custom action for SharePoint Designer involves create a ".actions" file.

Ive et inhiberet specimen Template quam ut satus off:

<?XML version="1.0" Encoding="utf-VIII" ?>
<WorkflowInfo xmlns="http://schemas.microsoft.com / sharepoint /">
<Actiones Sequential="igitur" PARALLELOS="et">

Autem, that xmlns attribute prevents my environment from working. My actions don’t show up in SPD.

Solutio est ut spoliaretis ex attributo xmlns, do an iisreset and close/re-open SPD.

Vivos et Simplex: Configurare musco quaerere specialis libraria document

4 Restituo

See UPDATE (Ego) below (11/24/07) on How to Configure Microsoft Office SharePoint Server 2007 to Index and Crawl Network Folders for Search

Objective: I want to execute a search restricted to a specific document library. In hoc, the document library contains training documents.

Steps:

1. Record the URL of the document library.

2. Create a scope:

Go to central administration.

Access the SSP.

Go to "Search Settings".

Scroll down to the scope section and select "View Scopes".

Create a new scope. Give it a name and useful description.

3. Define scope crawl rules:

Add a rule that defines the document library for this scope.

Select "web address" for "Scope Rule Type".

Enter the name of your folder (videre #1 above).

Accept the default value of "Include".

Wait for the scope to update (or start it manually).

4. Enable the scope in a site collection.

Go to site collection where you want to use this scope.

Add your new scope to the appropriate display group or groups.

5. Quaerere!

Ad hoc, you’re done. Assuming the scope is properly defined, it will be available in the scopes drop downs for simple and advanced searches and when you search using that scope, you’ll just get results you expect.

Notes:

I wrote this blog entry because my searches for simple scope setup turned up dry using phrases like:

configure scopes in MOSS
configure search scope moss
scopes in sharepoint 2007
scopes in sharepoint
search a document library moss
scopes primer moss

You can create a search scope on a folder, not just the entire document library.

A scope can be shared across multiple site collections (Hinc, a "shared service").

You can create the scope at the site collection level itself. Autem, I prefer to go to central admin because I can start the crawl from there. You cannot start the crawl from the site collection.

UPDATE (Ego) tamquam 11/24/07:

Kai Shang put together a great post entitled How to Configure Microsoft Office SharePoint Server 2007 to Index and Crawl Network Folders for Search @ http://kaishenghoo.spaces.live.com/blog/cns!8A7458DB12CA5AC9!206.entry

Technorati Tags: SharePoint, Sharepoint Search, Quaerere

Nec pulmenti vobis! Scelerisque vitae est elit Nazi products of NLB?

2 Restituo

Hodie, I tried to access a document library via windows explorer. This doc lib is living inside a system that consists of two WFE’s load balanced by some kind of Cisco NLB solution. (Si / cum retiacula pythones indica mihi quid sit, Ego hoc update stipes).

Windows explorer couldn’t connect. I did some research and eventually, retiacula magos dixisse WebDAV est infirma / non sustinetur / beneath the dignity of the NLB.

Ita, assuming the network wizards aren’t just telling me the network wizard equivalent of "take a long walk off a short bridge", Ego autem mirari — facit NLB, natura, disable WebDAV? Do we lose our windows file explorer interface to SharePoint? Is Cisco the IUS Nazi?

Curo MUSCUS / WSS environments — custodiens cum Microsoft scriptor notitia basis

Aliquam responsum

Microsoft creates knowledge base articles day in and day out and some of those are darned important to know about if you live in the SharePoint world.

Ego ad velocitatem aequare cum eis via per obsequium praebeant ad bonum folks www.kbalertz.com. KBAlertz enables you to sign up for your favorite MS technology and they send you digest versions of Microsoft KB articles via email.

Policy Web Application, Situs securitatem et tuitionem qr — Scire configuration

4 Restituo

(Updated 11/29 Qualiter ad obvius occasus per telam application consilium UI)

I had one of those "why is MOSS doing this to me????" moments today. In finem, BENE mea culpa.

We have an enterprise MOSS project going on and we want to secure "place holder" sites so that no user may access it or see it. That’s easy:

Vade ad site.
Confrínget securitatem hereditátem.
Aufero sulum user / coetus a site permissiones.

Supremus administrator collection site licentia relinquere iustum ad ad situm videre.

Si quis alius ligna in, ut non sit satis videre, et eatenus ab omni loco solitis locis.

Sed … non fuit. Simul, I suddenly realize that my "Joe User" standard user test account with no priv’s other than restricted read access has a "Site Actions" choice everywhere he goes. I double check one thing and double check something else. I pick up the phone to call a colleague, but put it down and check something else. I go for a walk and try everything all over again. I call a colleague and leave a message. And then, tandem, Invenio apud Ethan scriptor blog, his opening graph makes it quite simple:

MUSCUS 2007 Web Application vocatur novus pluma habet Politiae. Hi sunt permissiones quod securitatem Web Application purum alligatur. Hi omni securitate occasus, ut securitatem occasus dominari in situ positus est congeries sive Site (Meaning) quod pro gradu user.

A quick visit to web application policies shows that "NT Authority\authenticated users" had been granted Full Read. I removed them from the list and everything finally started working as expected. I believe they were added in the first place by someone with the mistaken impression that that is best method to grant read access to everyone in the enterprise. It does, sed, eliquare a quote, "It does not mean what you think it means."

Access web application policies this way:

Perge ad Centralis Administration
Lego Application Management
Select "Policy for Web Application"
Quod in screen, make sure you pick the correct web application. Enim me, Fusce a ipsum id elit consectetuer arcu ille qui non vult.

Cum hanc quaestionem, Lorem Ipsum verbis, vel in posterum minime mirum quantum in hac iuvatur:

Visibilium omnium actiones users Site

Actiones users ad omnes aspectabili Site

site securitatem actiones non sunt ornaverunt

impetrarunt MUSCUS site

introductio securitatem musco

Technorati Tags: SharePoint

Vivos et Simplex: Uti certa Keyword Quaero Praecessi Core in Quaerere

1 Respondere

Quick and Simple Instructions:

Edit a page and add a Search Core Results web part.

Edit that web part and expand "Fixed Keyword Query".

Add the fixed keyword query (e.g. ContentType:"Training invoice" TrainingInvoiceNumber:1111)

Expand Results Query Options and change "Cross-Web Part query ID" to a value other than "User Query" (e.g. "Query 2").

Notes:

Using core search results in this manner allowed me to create a page that shows information from another site collection. The client has two major site collections: Departments and Products.

The product site collection contains, naturally enough, product information. Each product in the site collection aggregates data from multiple sources.

One of the departments, codes and testing, is on such source. When users access product XYZ, they should see codes and testing data directly on the XYZ main page. Since codes and testing is hosted in another site collection, it’s a little awkward. We decided to use the core search results web part since search spans site collections. Codes and Testing manages product data via a custom list that is constrained by a specific content type. Aa keyword query that uses first the content type and then the product number narrow down the search to a single row in the custom list.

The keyword query above is an AND. It returns documents of content type "Training Invoice" and where the invoice number equals "1111".

A nice benefit from this approach: We can edit the XSL from the core search results web part and generate any format that we want.

En (http://devcow.com/blogs/jdattis/archive/2007/04/17/SharePoint_2007_How_to_Rollup_Content_from_multiple_Site_Collections.aspx) for another blogger’s discussion on this topic.

</finem>Scribet ad mea blog.

Dico me de tua blog!

27 Restituo

If you maintain a blog that is at least minimally connected to SharePoint, please let me know in comments. I would love to add you to my blog list.

If you maintain a blog that is not connected to SharePoint but want me to add it anyway, let me know. I’ll may create a separate blog list.

Please give:

Your blog URL (Manifestum)
A short description of your blog.

I want to keep the link to "active" blogs, which I’m roughly defining as one post per week and minimum three months old. If you don’t meet that "requirement" add your name to comments anyway. It’s *my* list so I can break my own rule if I want to.

Gratias!

Operarius Lorem ipsum et materia Template — Cimice decrementum in in Template

5 Restituo

The client noticed a bug today with the above mentioned template.

Course managers create courses. When creating a course, in maximum numerus of procurator quod specificat sedes praesto.

The template provides for self-service enrollment. I enroll and a workflow attached to the registration list decrements the "available seats" sociatur Utique.

Individuals may also unregister from a course. The bug lies here. Unregistering from a course does not increment the available seats counter. Ut ex, available seats is not accurate. This bug is compounded by the fact that when available seats decrements to zero, non plus sui ministerium adnotatione admittitur.

Fortunate, Microsoft provides the workflow for this process. Even better, suus sea workflow creatus per SharePoint Designer.

Haec altum gradu sequantur vestigia figere eam:

Ignis sursum SDP.
Obvius fundatur off site disciplina template.
Access "Attendee unregistration" workflow.
Insert his gradibus (Duo gradus, quorum primus ego):
1. Adice Cursus:Repleti sedes minus 1 (Output INCERTUS:calc)
2. (igitur) Item in update Cursus

Click Perago et es fieri.

Collaborative offa:

SharePoint amet:

Complevit workflow:

Descende-conputat EXERCITATIO:

Item cursuum in update:

Da bono nuntio crebro; da malum fama mane

Aliquam responsum

I’ve been a consultant for a lot of years now and as any experienced consultant knows, good communication is one of the key pillars to the successful delivery of a project. It’s so obvious, it’s really almost boring to talk about. This isn’t a post about generic communication. Pro, I’m writing about the darker side of communication — communicating bad news.

It goes without saying that giving good news to the client is done all the time, as often as possible. Who doesn’t want to give good news? Who doesn’t like to hear good news?

On the flip side, bad news is no fun at all. I have always struggled with this. In the earlier days of my career, I would know something was awry with a project and instead of telling the client, I would work longer hours to try and solve the problem. I would enjoin my team to work harder. It’s a natural enough impulse to think that a super-human effort can save the day. Some times this works, some times it does not. Even when it "works" it’s often a mixed bag. Is the quality of the deliverable really up to spec when key parts have been developed over several 60 ad 80 hour weeks?

What is the best way to handle bad news? The answer is: tell it early. Don’t wait until one week before the project budget will be consumed. If you know six weeks out that there simply isn’t enough time to deliver some bit of promised functionality, tell the client right then and there. The client may get upset (probably will), there may be incriminations and accusations and hurt feelings. Sed, when emotions cool off, there’s still six weeks left on the project. Six weeks is a good chunk of time. There’s time to adjust plans, change schedules, get the ball rolling on budget extensions (good luck!) and just generally come to grips with the "facts on the ground" and devise a new plan that still results in a successful project.

Case in point: I’m working on a project characterized by:

T&E budget with a capped "Not to exceed" dollar amount.
A "best efforts will be made" promise to deliver X, Y and Z by project’s end.
Lack of promised key resources on the client side. These resources were not withheld on purpose, nor for any "bad" reason, but they were withheld.
A dawning realization as the project passed the half-way point that we were not going to be able to deliver "Z" (mainly because the promised resources were not actually available).
Regular status reports and "CYA" documentation that backed us (the consulting team) up.
Tightly knit implementation team with members drawn from the consulting organization (my company) and the client.
Distant management team, in both a metaphorical and physical sense. The management team was focused on another large enterprise project and due to space constraints, the implementation team was housed in a separate building on campus, down a hill and relatively far way from "civilization".

With roughly six weeks left on the project budget, nos (the implementation team) knew that we were trouble. The contract said that we needed to deliver "Z". Even though the project is time & materials and even though we only promised "best efforts" to deliver Z and even though we had great justification for missing the delivery … the bottom line is that it wasn’t looking good — we were not going to deliver Z in a shape a quality that would make anyone proud.

Recognizing this, we went to management and told them that the project budget would be consumed by a certain date and that we were in trouble with Z.

A mini firestorm erupted over the next few days.

Day 1: Management team calls in its staff for a special meeting (nos, the consultants are not invited). Contracts are printed and handed out to everyone and a line-by-line review ensues. Management puts the staff members on the defensive. I don’t think the phrase "Stockholm Syndrome" is *actually* used, sed vos adepto picture. We’re a tight-knit group, post omnes, and the staff has been working with us consultants day in and out for several months now.

Day 2: Management calls another staff meeting. They feel a little better. They want options and ideas for moving forward. They realize there’s still six weeks remaining in the current project budget, which is still a decent bit of time. One of the action items: schedule a meeting with full implementation team (including consultants).

Day 5: Full team meets, constructive meeting ensues and a new achievable plan put into place. Even better, we’ve already begun discussing phase two and the client invites us to prepare proposals for that phase immediately.

If we had waited until just three weeks remained, or even worse, one or two weeks, it would have been much different. Instead of a constructive meeting to re-align the project, we would have been pulling out status reports, parsing the contract and reviewing old emails to justify this or that decision. We would have "won" but is it really "winning" hoc in casu?

Ita, if you have to give bad news, give it early. Bad news given late isn’t just bad, suus horrendum.