June: SharePoint

Usura “Personae aut coetus” in columna iniri

People commonly ask about using a column of data type "Person or Group" in another column of data type "Calculated".

Imo linea, hoc non operetur in WSS 3.0 (vel MUSCUS).

Cum addita ratione agmen, WSS shows the list of fields it allows you to use for the calculation. If you type in the name of a column that is not in its list, Is dico vos:

Unus vel plures columns References non liceat, quia non est modus columnae datis sustineantur definitur formulae.

Workaround: Use an event handler. The event handler fires when the user saves the item. It performs the update you would have wanted the calculated column to do for you.

Suspendisse in ratione communi in agris:

Lorem vivos: Et illa vera et accurata, sed vidi tantum passim ingeniis musco / WSS ut non mirum sit amet (Sin ATTONITUS) if someone has figured out a way to do this without resorting to code. If you’ve figured out clever work-around or know someone that did, placet me cognoscere!

MUSCUS / michi WSS: “Alius paginam iam author in modificatur …” sed ultro, non fuit.

We did some heavy duty re-organizing of our site taxonomy via "Manage Content and Structure". For reasons unknown to me, hoc processus (quamquam in summa operantes) broke some navigation links in the quick launch. The broken links are characterized by:

  • Wrong URL. Verbigratia, it should be "/sites/departments/HumanResources/…". Autem, the new link is "/sites/Corporate/HumanResources/…".
  • Repetitur frenos in titulo quaestionis filum, ut in:

/sites / Dicasteria / HumanResources / _layouts / viewlsts.aspx?BaseType = 0?BaseType = 0?BaseType = 0?BaseType = 0

That’s easy enough to fix via site settings/navigation. Except, MUSCUS sistit hic me experior me et faciam illud:

imaginem

Hoc est,, Nemo ulla mutatione (declinavimus a me, utique).

A vivos quaerere irrepserit hac forums Discussion MSDN: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1691577&SiteID=1

Willelmi Belle Heurdier posuerit eam in penultima (tamquam 10/02/07) stipes:

Hoc est,:

Corrupta ad reset headings, habes :

– omnem tabularum sub capite corrupto

– aufero caput capitis corrumpi

– A occasus album, add a removed list to the quick launch (Haec non corrumpuntur petenti regenerare)

Vos igitur ad bonum….


Peritus Sharepoint – Cap Sogeti Gemini Helvetia

Confusus sum, quia ego, volens transire amet consectetuer navigatio, make the change and then get hit with the "page was modified" message. Tandem, I realized I had to go to the list settings and remove/add it to quick launch. That did the trick. Happy times are here again!

</finem>

Scribet ad mea blog!

Problems “Donec Date pause” operatio in-creatum SPD workflows

UPDATE 12/10/07: Hotfix as described in MSDN KB929816 solved the problem for us mentioned below. Obtain the hotfix and then install on each server on the farm. Igitur, sharepoint configuration utility on each server. Here is the MS Support link for that KB: http://support.microsoft.com/kb/932816.

Background:

An environmental engineering amet habemus negotium ubi necessitas requirit ut 30 some-odd manufacturing locations located throughout the United States needs to ensure that those plants file for their various state-mandated permits in a timely fashion. One approach we’ve investigated leverages the "Pause Until Date" activity available to us via SharePoint Designer worfklow. The engineering manager (vel eius vicarii) enters all the required permits and reminder dates at the start of the year. The system then does all the heavy lifting.

Environment:

MUSCUS, 64 frenum, Rectum Apparatus environment (progressionem buxum), 2 servientibus (In SQL servo #1, omnia alia server #2).

Problemata:

The Pause Until Date action seems like the perfect solution and it may well prove itself to be. Autem, Quisque a quam non faciat (pro nobis).

  1. Job non workflow est scheduled ad currere, ever. I discovered this by reading through CHRISTOPHORVS Albus scriptor (http://chrissyblanco.blogspot.com/2007/06/issues-with-delay-activity-in-moss.html) excellent write-up by using stsadm thusly:

    C:\>stsadm -o getproperty -propertyname "job-workflow" -url http://localhost

    <Property Exist="No" />

    C:\>

    Quod mirum erat, sed facile solvitur per:

    C:\>stsadm -o setproperty -propertyname "job-worfklow" -propertyvalue "every 1 inter minutes 0 et LIX" -url http://localhost

    Operatio feliciter expletum.

    C:\>

    Quod faciendum, the first "In Progress" workflow celeriter officium fecit et concitus.

  2. Miserabile, the next one didn’t work as expected. Gratanter, Christopher refers us hic (http://support.microsoft.com/kb/932816). As of writing of this entry, IT department sumus expectantes obtinere hotfix, but it does look promising. Our copies of the affected .dll’s do not share the same byte size, ita spero satisfaciet proposito.

Workaround:

Re-running the stsadm -o setproperty command seemed to prod the workflow timer awake. It would, Violatis 7 minutes laxus, actually wake up and continue along with the workflow.

Quæstiones / Alloquitur exitibus:

Donec mora Date non operatur.

Date mora Donec non recuperabit.

Workflow status does not change from "In Progress"

Workflow status stays "In Progress"

MRO Workflow causa studio usura MUSCUS, SPD, InfoPath & meaning officia.

Overview

Collatio describit causa studio descriptis actualis MRO (Ut starent, Instaurabo et operationes) workflow approbatione processus perficiatur musco.

Hoc est technica non facto Discussion, sed eidem ministrat prospicere realis-mundi suggestum occurrit exemplum quod ostendit, quomodo musco realis-mundi indigent.

(This entry is cross posted between http://paulgalvin.spaces.live.com et http://blogs.conchango.com)

Background

The client’s MRO process had been characterized by the following

  • Manual approval process.
  • Some support using excel spreadsheets.
  • Irregular approval process. The same MRO purchase approval process would vary day to day, person by person.
  • Lots of paper and hand-written signatures — purchase requisitions required up to 3 written signatures before final approval.

The objectives of this project included:

  • Fully automate the process.
  • Enforce enterprise standards for approval.
  • Provide consolidated view of MRO purchasing to various managers.
  • Detailed audit trail.

As a side effect of the solution, written signatures were no longer required.

Approval Process

The approval process consists of four "swim lanes": Originator, Direct manager, Functional manager and division manager.

Originator:

Sees the need for the purchase and starts the process. Note that the originator may or may not actually enter the purchase requisition, but instead direct another staff member to do so. ALIQUOTIES, the originator does not have the technical expertise to fill out the PO requisition. Verbigratia, a user may want to requisition a new laptop computer, but does not know the best vendor, IT standards, etc. In hoc, the originator works with IT and IT actually fills out the requisition.

Direct manager:

This is the direct manager of the originator (which may be different from the person who actually entered the PO requisition into MOSS). Direct managers must approve the PO requisition before the system seeks approval further down the line.

Functional Manager:

The functional manager is the individual responsible for ensuring that the proposed purchase conforms to enterprise standards within the scope of a particular corporate function. Verbigratia, IT purchases are approved by an IT functional manager.

Division Manager:

Division managers approve purchase requisitions strictly by dollar amount. Division manager approve purchase requisitions in excess of a configurable dollar amount.

The Solution

We used the following tools and components to implement the solution:

MUSCUS: Serves as the platform off which everything else "hangs". MOSS provides bedrock services for security, master data, audit trails and other features.

InfoPath forms services: A MOSS component, this enables users to fill out purchase requisitions via a web browser.

SharePoint amet (SPD): We used SPD to implement the automated workflow process.

Web Service: A c# web service enhances the user experience by enabling cascading selections lists in the InfoPath form and provides better performance with respect to filtering data. Videte hic for a technical deep dive on this subject and our reasons for using it.

Custom Lists: MOSS user profiles provided a given user’s direct manager, but did not provide most of the data that controlled workflow decisions (e.g. whether the divisional manager is required to approve the PO requisition). We used custom lists in an "Enterprise Data" site to maintain data such as "Divisional Manager Approval Dollar Amount", "Functional Area Manager" and so forth. Lists integrated very nicely with InfoPath and also provide create/update/delete (CRUD) functionality with auditing and security out of the box.

Use Case

This use case illustrates how the solution fits together:

  1. Paul wants a new laptop. He describes his needs to Vivek, an IT person familiar with corporate laptop standards, preferred vendors, etc.
  2. Vivek logs into MOSS, accesses the PO Requisition form and enters the requisition on behalf of Paul. The form prompts Vivek for a purchase category which then uses the web services to populate a drop-down list of company-approved vendors. Vivek also specifies the corporate functional area of this purchase (e.g. "IT" or "Finance").
  3. SPD based workflow starts, determines Paul’s direct manager and routes the requisition to his manager, Stacy.
  4. Stacy approves the purchase requisition.
  5. SPD workflow inspects the requisition and determines it’s an IT purchase. It routes the workflow to the IT functional manager, Wonson.
  6. Wonson approves the requisition.
  7. SPD workflow again inspects the requisition and determines that the purchase amount exceeds a maxium dollar amount and routes it to the division manager for approval.
  8. The division manager approves the purchase requisition.

Notes

  • The use case demonstrates a "clean" run with no rejections or jumps.
  • Every approver has the ability to approve or reject the requisition as well as provide written comments. These are logged in the audit trail.
  • If a responsible manager rejects the purchase requisition at any point, the PO requisition is "dead" and the process must be started from the beginning.
  • Workflow notifies the originator at every step of the process.
  • No written signatures — the client determined (after some forceful recommendations) that the audit trail as provided via workflow history, served their auditing needs.
  • Effort — it took approximately three man weeks to implement this solution.

Conclusio

This solution leverages MOSS as a development and run-time platform. The client was able to leverage core MOSS features to automate a routine business process that affected nearly every employee in the company. With the exception of a simple web service (which itself leverages MOSS), almost no actual "programming" was required.

The solution also serves as a "showcase" for the client, demonstrating how different MOSS features can be combined to create a fully featured business application and generate new consulting opportunities in the future.

Glossary

MRO: Ut starent, repair and operations. These purchases typically include items such as notepads, chairs, personal computers, printers, cell phones and the like.

MUSCUS / WSS Search results (et dataviews): considerandam rudis XML notitia

Haec dicta sint, manifeste cognitum multis, sed dum studet enim meus MUSCUS ipsum programming, Facile intellexi satis est quaerere utrum per ipsam Suspendisse a user interface.

Unus modus est ut sequitur vivos:

  • Obvius Provectus Quaero.
  • Investigationem perage quod reddit aliqua notitia.
  • Duis page (occasus per site).
  • Mutare sequenti p:

<?XML version="1.0" Encoding="utf-VIII"?>
<
p:stylesheet version="1.0" xmlns:p="http://www.w3.org/1999/XSL/Transform">
<
p:output methodo="XML" version="1.0" Encoding="UTF-VIII" indent="Imo"/>
<
p:Template match="/">
<
pre>
<
p:exemplum ex- elige="*"/>
</
pre>
</
p:Template>
</
p:stylesheet>

  • Appone percute.
  • Nuper mutata in navigatro.

Et nota quod <pre> tag doesn’t do much except serve as a convenient marker when you view the results.

This trick can be very helpful when working with managed properties and customizing search. It will provide a definitive list of the XML available for you to use in your xslt which would have been very helpful the last 25 Search Results Lorem tempora creata sum quidam.

Propter hoc oportet operari tam dataviews, probatur ex eo quod adhuc non licet.

Splendidus retineo visum et Content Management API

Stefan Goßner has put together a terrific 4-part series on the SharePoint Content and Deployment API hic. It offers a great overview and very good examples in code (C #).

I first picked up this link from joris poelmans blog at http://jopx.blogspot.com/.

Etiamsi es similest mei;, in that you have not had to do much hands-on work for content management, this is well worth 20 minutes of your time to read.

Using the API, one can:

  • Export and import content very easily.
  • Re-parent content. If you want to export some content from a site "A" and send it to site "B" but in a totally new place in the hierarchy, this is possible.
  • Export content from a site A and import selected bits into site A.
  • Re-link content (meaning deal with all the hyperlinks).

WSS, doc libs & tabulatum, Ratione columnas involvat [Me]

Someone on the Internets was asking about how to create a calculated column on a list that would show a value formatted as "[User] – [Status] – [Location]" as in "Paul Galvin – Bibentes [libero] Cervisiam – The Beach".

Paul would go in and update his entry in the list and the calculated column would update appropriately. The [User] deficeret ad user introitu / updating album.

A calculated column cannot use "volatile" ut functiones [Me] aut [Hodie]. I solved it in a test environment with these steps:

  1. Create a text column named "Current User".
  2. Pone eius defaltam ad valentiam [Me]
  3. Create a calculated column called "Calc Test".
  4. Pone valor = [User current]

Profectus sum in, Accessit item operatur album.

Intermittendi IE cum accessu ad fragosus in documentis WSS / library MUSCUS document

Nam hoc fui flagellatus 9 et vidi in mensibus populum et MSDN Usenet forums eam too.l

Aliquando, Cum accessu ad verbum document (aut alia genera doc) ex scripti simpliciter in bibliotheca facit Penitus Rimor 'fragosus et recedam (si aperta sunt cum eo assumptis universis tabs).

Hotfix potest solvere hoc MS: http://support.microsoft.com/kb/938888

Quoque, illic 'nonnullus forsit description de hic:

http://jopx.blogspot.com/2007/07/solving-internet-explorer-crash-when.html

Velle verum gradum XPath?

Overview:

Procurat quod a quibusdam ratio contenti elenchum creavit consuetudo duodecim columnis.

Addita ad paginam deinde per SPD, convertatur in ipsum secundum.

Forsit:

My Xpath expression was returning blank for a column named "Current Position". I referenced it thusly:

    <table border="1">
      <p:for-each select="/dsQueryResponse/Rows/Row" >
        <tr>
          <td>
            Current Status:
            <p:value-of select="@Current_x0020_Status"></p:valor ex->
          </td>
        </tr>
      </p>
    </mensamque>

The column in the CT is named "Current Status". It shows up in the lookup as "Current Status". Everywhere you look, you see "Current Status".

While thrashing madly about, looking for a solution, I instead referred to "@Recruiter" and behold! — that actually returned back the current status. I expected it to return back the recruiter when I did that.

Solutio:

I poked about in SPD. Go to that page in SPD and it shows the data view. You can inspect the actual data provided to the view and associated Xpath. Here I found out that indeed, the Xpath pointed at "Recruiter". Strangely enough, the "actual" recruiter field pointed from "Recruiter1".

Take Away:

SPD provides authoritative Xpath expressions for rows & columns in a data view.

Secundo, it shows the actual data. So for example, a column of type shows this:

<nobr><span><A HREF="/sites/Corporate/HumanResources/TalentAcquisition/_layouts/userdisp.aspx?ID=17">Galvin, Paulus</A><img terminus ="0" height="1" width="3" src="/_layouts/images/blank.gif"/><a href=’javascript:’ onclick=’IMNImageOnClick();return false;’ class=’ms-imnlink’><img name=’imnmark’ title=” border =’0′ height=’12’ width=’12’ src=’/_layouts/images/blank.gif’ alt=’No presence information’ sip=’PGalvin@xxx.com’ id=’imn_77,type=smtp’/></a></span></nobr>