Цатегори Арцхивес: СхареПоинт

Коришћење “Лице или група” у израчунатој колони

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

Боттом лине, ово не ради у ВСС 3.0 (или МОСС).

Када додајете израчунату колону, 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, То вам говори:

Један или више колона референце нису дозвољени, јер су колоне су дефинисане као тип података који није подржан у формулама.

Решење: 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.

Корисни линкови о обрачунатим поља у целини:

Брзо Дисцлаимер: Верујем горе да би било истинито и тачно, али сам видео довољно паметне трикове ту и тамо у Мосс / ВСС да не би било изузетно изненађен (Нестрпљиво ако хоћете) 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, молим вас јавите ми!

Мосс / ВСС ми каже: “Страница је измењена од стране другог аутора на …” али заправо, то није било.

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

  • Wrong URL. На пример, it should be "/sites/departments/HumanResources/…". Међутим, the new link is "/sites/Corporate/HumanResources/…".
  • Repeated bits on the query string of the heading, као у:

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

That’s easy enough to fix via site settings/navigation. Except, MOSS presents me with this when I try and do it:

слика

The fact is, no one is making any change there (aside from me, наравно).

A quick search turns up this MSDN forums discussion: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1691577&SiteID=1

William Heurdier lays it out nicely in the the penultimate (као и од 10/02/07) после:

Fact is:

To reset corrupted headings, you have to :

– remove all the lists under corrupted heading

– remove corrupted heading

– From the list settings, add a removed list to the quick launch (This regenerate a non corrupted heading)

You are then good to go….


Sharepoint Expert – Sogeti Cap Gemini Switzerland

I was a bit confused because I kept wanting to go to the navigation page, make the change and then get hit with the "page was modified" message. Коначно, 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!

</крај>

Претплатите се на мој блог!

Проблеми са “Пауза до датума” активност у СПД-створене токове посла

УПДАТЕ 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. Онда, sharepoint configuration utility on each server. Here is the MS Support link for that KB: http://support.microsoft.com/kb/932816.

Позадина:

Имамо пословну услов где еколошки инжењеринг менаџер треба да осигура да 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 (или њен помоћник) enters all the required permits and reminder dates at the start of the year. The system then does all the heavy lifting.

Околина:

МОСС, 64 бит, виртуелна машина окружење (Развој кутија), 2 сервери (На СКЛ серверу #1, све остало на серверу #2).

Проблеми:

The Pause Until Date action seems like the perfect solution and it may well prove itself to be. Међутим, не ради добро из кутије (за нас).

  1. Ток посао није требало да покрене, ever. I discovered this by reading through Кристофер Вајт (http://chrissyblanco.blogspot.com/2007/06/issues-with-delay-activity-in-moss.html) excellent write-up by using stsadm thusly:

    Ц:\>stsadm -o getproperty -propertyname "job-workflow" -УРЛ хттп://лоцалхост

    <Property Exist="No" />

    Ц:\>

    То је изненађујући резултат, али лако решити:

    Ц:\>stsadm -o setproperty -propertyname "job-worfklow" -propertyvalue "every 1 минута између 0 и 59" -УРЛ хттп://лоцалхост

    Операција је успешно завршена.

    Ц:\>

    Када то раде, the first "In Progress" Ток брзо запали и урадио свој посао.

  2. Нажалост, the next one didn’t work as expected. Срећом, Christopher refers us овде (http://support.microsoft.com/kb/932816). As of writing of this entry, чекамо ИТ одељењу да добије хитну исправку, but it does look promising. Our copies of the affected .dll’s do not share the same byte size, па се надам да ће решити проблем.

Решење:

Re-running the stsadm -o setproperty command seemed to prod the workflow timer awake. It would, грубо 7 минута касније, actually wake up and continue along with the workflow.

Питања / Питања којима се бави:

Пауза до датума не ради.

Пауза до датума не настави.

Workflow status does not change from "In Progress"

Workflow status stays "In Progress"

ОСП тока студија случаја коришћења Мосс, СПД, ИнфоПатх & веб сервиси.

Преглед

This entry describes a case study describing an actual MRO (Maintenance, Repair and Operations) workflow approval process implemented in MOSS.

This is not an overtly technical discussion, but instead serves to provide a real-world example that demonstrates how the MOSS platform met a real-world need.

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

Позадина

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. Неки пута, the originator does not have the technical expertise to fill out the PO requisition. На пример, a user may want to requisition a new laptop computer, but does not know the best vendor, IT standards, итд. У овом случају, 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. На пример, 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:

МОСС: 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.

СхареПоинт Десигнер (СПД): 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. Видети овде 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 (Цруд) 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, итд.
  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.

Белешке

  • 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.

Conclusion

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: Maintenance, repair and operations. These purchases typically include items such as notepads, chairs, personal computers, printers, cell phones and the like.

Мосс / ВСС Пронађено (и датавиевс): видите сирове КСМЛ податке

То може бити очигледно да многима, али док је студирао за мој испит МОСС програмирања, Сазнао сам да је прилично лако да се стварни КСМЛ из упит претраге путем корисничког интерфејса.

Један брзи метод је следећи:

  • Приступ напредну претрагу.
  • Обавите претрагу која враћа неке податке.
  • Уређивање странице (преко сајта подешавања).
  • Промените КССЛ на следеће:

<?КСМЛ верзија="1.0" кодирање="УТФ-8"?>
<
клс:стиловима верзија="1.0" КСМЛнс:клс="хттп://ввв.в3.орг/1999/КССЛ/Трансформ">
<
клс:излаз метод="КСМЛ" верзија="1.0" кодирање="УТФ-8" увући="да"/>
<
клс:шаблон меч="/">
<
унапред>
<
клс:копија-у изабрати="*"/>
</
унапред>
</
клс:шаблон>
</
клс:стиловима>

  • Хит примењују.
  • Виев Соурце у бровсеру.

Имајте на уму да <унапред> 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 пута сам створио неке прилагођене резултате претраге.

То би требало да раде, као и за датавиевс, мада нисам тестиране да је од још.

Нема ЦКВП за ВСС? Покушајте ово…

Видим да Ериц Краус was faced with a requirement normally met with a content query web part. Проблем? He was in a pure WSS environment with no access to the CQWP. Rather than curling up in the fetal position (нагон морам да се борим сваки дан, изгледа), he came up with solution that at least gives WSS shops a fighting chance to succeed. It’s described овде.

Бриљантно и детаљан приказ управљања садржајем АПИ

Stefan Goßner has put together a terrific 4-part series on the SharePoint Content and Deployment API овде. 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/.

Even if you’re like me, 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).

ВСС, доц либс & Листе, Израчунате колоне укључују [Ме]

Someone on the Internets was asking about how to create a calculated column on a list that would show a value formatted as "[Корисник] – [Статус] – [Локација]" as in "Paul Galvin – Алкохол [бесплатно] Пиво – The Beach".

Paul would go in and update his entry in the list and the calculated column would update appropriately. The [Корисник] треба бити додељена кориснику улази / ажурирање листе.

A calculated column cannot use "volatile" функције, као што су [Ме] или [Данас]. I solved it in a test environment with these steps:

  1. Create a text column named "Current User".
  2. Поставите своју вредност подразумевану [Ме]
  3. Create a calculated column called "Calc Test".
  4. Поставите своју вредност = [Тренутно корисника]

Отишао сам у, додао ставку на листи и то је радио.

Прекидајући ТЈ пада када приступа документима у ВСС / МОСС библиотеку докумената

I’ve been plagued by this for 9 months and I see that people on the MSDN and Usenet forums have it too.l

Понекад, when accessing a word document (or other doc types) from a document library causes Internet Explorer to simply crash and go away (taking all the tabs with it if any are open).

This MS hotfix may solve it: http://support.microsoft.com/kb/938888

Такође, there’s some description about the problem here:

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

Да ли ће стварно КСПатх корак напред?

Преглед:

Created a custom list that manages a content type with some dozen columns.

Added it to a page and then via SPD, converted into a data view.

Проблем:

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

    <table border="1">
      <клс:for-each select="/dsQueryResponse/Rows/Row" >
        <тр>
          <тд>
            Current Status:
            <клс:value-of select="@Current_x0020_Status"></клс:вредности од>
          </тд>
        </тр>
      </клс>
    </табела>

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.

Решење:

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.

Други, it shows the actual data. So for example, a column of type shows this:

<фонт><распон><A HREF="/sites/Corporate/HumanResources/TalentAcquisition/_layouts/userdisp.aspx?ID=17">Galvin, Павле</A><имг бордер ="0" height="1" width="3" src="/_layouts/images/blank.gif"/><a href=’javascript:’ onclick=’IMNImageOnClick();return false;’ class=’ms-imnlink’><img name=’imnmark’ title=” бордер =’0′ height=’12’ width=’12’ src=’/_layouts/images/blank.gif’ alt=’No presence information’ sip=’PGalvin@xxx.com’ id=’imn_77,type=smtp’/></a></распон></фонт>