MOSS esaten dit “Sarbidea ukatu” Workflow zeregin bat editatzeko, Baina ez dut dute sarbidea

2 Erantzunak

I’ve implemented a workflow using SharePoint Designer in a site which is mainly read-only to "NT_AUTHORITY\Authenticated Users" (I.E. guztiontzat). There is a forms library for an InfoPath form. There is an associated workflow tasks list as well so that when the workflow operates, zereginak esleitu ahal izango da pertsona.

Baimena apurtu dut forma liburutegia eta zereginen zerrendaren beraz autentifikatutako erabiltzailea edozein forma sor daitezke, eta euren esleitutako zereginak eguneratu.

I test with my low-privileges test account.

Ezin bete dut eta liburutegian inprimaki bat gorde? –> BAI

Ezin zeregin sartzeko I elektroniko bat lotura-tik? –> BAI

Ezin bat editatzeko workflow zeregin lotura ikusten dut –> BAI

Ezin klik lotura duten I? –> NO … Baimena ukatu.

Zergatik ezin bat editatu lotura duten me baimena ukatzen ikusten dut egin klik I? That’s not how it’s supposed to work…

Joan segurtasun konfigurazioa bidez dut berriro, very closely. I do it again. Mezu hau ez da ezabatzen uste dut jakina dut, zeren ez dakit segurtasun buruz ezer.

Azkenik, I search the Internets. I find this highly unlikely MSDN forum thread: http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=1838253&SiteID=17

Kartelak dela iradokitzen to eu esportatzen disko platter bat ekintza sinple bat MOSS segurtasun zulo konpondu egingo? I can hardly believe I just typed that. I’m reminded of the South Park episode about the 9/11 konspirazio non Stan gure Preznit da eskatuz, "Really?" over and over again.

Beraz,, ezer galtzeko, Sutea sortu dut SPD, eu eskuin-klik egin eta gorde nire c:\ drive. That would be the c:\ drive on my laptop. I’m looking over my shoulder the whole time so that no one will ask me, "why are you saving that workflow to your laptop?"

Izugarri, that solves my problem. I can edit the task.

Izendatuko dut hau gehien Bizarra Workflow Workaround izateko 2007.

</amaiera>

Technorati Tags:

SharePoint Designer, Uneko elementua en “Kodetuta absolutua URL” eta HTTPS

4 Erantzunak

We often want to send an email that includes a hyperlink to the item or document that triggered the workflow. We can use current item’s "Encoded Absolute URL" for this purpose. Hala eta guztiz ere, it always seems to use "http" for the URL protocol. If your site runs on HTTPS then it will not work for you.

image

Den neurrian ezagutzen dut, there is no out of the box solution to this problem. If you need to use HTTPS, Aukera kutxa kanpo ez duzu.

Konpondu nahi, create a custom action that provides a string replace function to use in your workflow. Alternatively, erabili 3 party tresna, hala nola, pakete bikaina hemen: http://www.codeplex.com/spdwfextensions 🙂

</amaiera>

Technorati Tags: ,

Azkarra eta erraza: Zehazteko Barne Zutabe Web Zutabe baten izena

3 Erantzunak

UPDATE: Jeremy Thake du honi buruz Blogetakoak eta jarri batzuk kontsola aplikazio baten kodea erakusten duen barne-izenak.

I was trying to get a content query web part to display a due date from a task and because the screen label is "Due Date", Zutabe-izen hori erabili bere gain hartu nuen <CommonViewFields> is "Due_x0020_Date".

Oker!

The real column name in this case was "DueDate".

Nola aurkituko dut? I re-read Heather Solomon en CQWP aldatzea sarrera blog to show additional columns of data. She describes this process at step #13. Trust it. It’s correct. Gutxienez, it was correct for me. I did not trust it at first for another column with a much longer name.

I say "Trust it" because I did not trust it and probably wasted near two hours butting my head up against a wall. After I resolved the "DueDate" izena, Eremu beste gehitzeko nahi nuen <CommonViewFields>. Using the Solomon technique, I was getting a column name like "XYZ_x0020_Project_x0020_Due_x00".

, Pentsatu nuen, that’s clearly a truncated name. I went ahead and un-truncated it with no success. I finally used the seemingly truncated name and it worked.

Bonus tip: Noiz CQWP batera nintzen lanean, gehitu dut txarra barne izena badago <CommonViewFields>, the CQWP would tell me that the query had returned no results. Baina, gehitu dut datu-mota bat bada, eremu-izena, it would return a result. Adding the data type actually masked a problem since I was referencing a non-existent field. I could add it, baina bere balioa erakutsi nahi izan dut,, I would always get a blank.

Honek ez zuen maskara errorea:

<CommonViewFields>Due_x0020_Date;</CommonViewfields>

Akats maskara zuen:

<CommonViewFields>Due_x0020_Date,DateTime;</CommonViewfields>

</amaiera>

Kontuz Breaking to ItemStyle.xsl aldaketak

Utzi erantzun bat

ItemStyle.xsl zen I Eduki Query Web Taldea eta eskuineko itxura pertsonalizatzeko lunch time buruzko lan, I made a breaking change to the xsl. I didn’t realize it, but this had far reaching effects throughout the site collection. I went off to lunch and upon my return, nabaritu mezu hau toki mordo bat agertzen:

Ezin da Web zati honetan erakutsi. Arazoa konpontzeko, Open Web orrialde honetan, Windows SharePoint Services bateragarria, hala nola, Microsoft Office SharePoint Designer gisa HTML editorea. Arazoak jarraitzen badu, harremanetan zure web zerbitzariaren administratzaileak.

Bezeroa erruduntzat dut (oraindik ez konturatu zela nire errua puntu honetan) but eventually noticed that visual studio intellisense was warning me that I had malformed XSL. I corrected it and everything started working.

Izan darned kontuz ItemStyle.xsl lan egiten (eta XSL global edozein artxibo) — Horietako asko hautsi eragiten artifacts gune bildumako.

<amaieran />

My Son Hacked Gamespot

1 Erantzun

Beraz,, goizean, nire semea zehaztuko da adin-hamahiru mugatuan Halo ikusteko 3 bideoa Gamespot. I’m outside shoveling snow, so I’m not there to help or hinder. Necessity is the mother of invention and all that … he has a eureka! moment. He realizes that even though Gamespot wants him to enter his real jaiotze-data, benetan sartu ahal izan edozein birth date he wants. Once he realized that, nahikoa zaharrak berak bideoa ikusteko egin zuen.

I’m not quite sure how I feel about this 🙂

Igandea Funny: “Garbage da inprimatzea”

1 Erantzun

Nire unibertsitateko out lehenengo lana at 1991, Zortea behar fabrikazio-enpresa batean lan egin izan dut 13 kokapenak, not including its corporate HQ in New Jersey. I joined just when the company was rolling out a new ERP system. We were a small IT department of about ten people altogether, two of whom Did Not Travel. Part of the project involved replacing IBM System 36 boxes with HP hardware and HPUX. Everyone used green tubes to access the system.

Proiektuan zehar pasatzean, eta nago bidalitako behera Baltimore berri bat co-langilea batera, Jeff. Our job was to power up the Unix box, ziurtatu O / S exekutatzen, instalatu ERP sistema, konfiguratzeko ERP du, train people on the ERP and do custom work for folks on the spot. (Hau ametsetako lana izan zen, batez ere, zuzen izarrekin unibertsitateko datozen). Before we could really get off the ground, berde hodi guztiak despaketatzeko behar dugu, put them on desks and wire them. And the best part was that we had to put the RJ11 connectors on ourselves.

Arrazoi inoiz ez dut ulertzen, eta inoiz pentsatu buruz galdetu momentuan egiteko, izan genuen kontratazio enpresa batzuk ere etortzen dira eta kable exekutatu landare osoan zehar, but we didn’t have them put on the connectors. Beraz,, there was a "patch box" with dozens of of unlabeled cables in the "computer room" eta horiek eraikinaren inguruan snaked eraikinaren hainbat tokitan.

Gure bidea egin dugu, horren bidez, asteburuan zehar, alanbre bakoitzean probatzen, Konektore bat jarri (Ziurtatu zuzen vs egiten zen. zeharkatu), hodi berdea eta inprimagailuak ezarpen bit ziren egokiak bermatuz, labeling wires, making sure that "getty" was running correctly for each port and probably a thousand other things that I’ve suppressed since then. It all came together quite nicely.

Baina, there was one important cable that we couldn’t figure out. The plant in Baltimore had a relationship with a warehousing location in New Jersey. Some orders placed in Baltimore shipped out of that location. There were two wires that we had to connect to the HPUX box: a green tube and a printer. The green tube was easy, baina inprimagailua hiru aste amesgaizto bihurtu.

Ez baduzu ezagutzen, edo kendu da, hodi berdea eta inprimagailu era honetan aurre, there are various options that you deal with by setting various pins. 8-bit, 7-bit, parekotasuna (are / bakoitiak / bat ere ez), probably others. If you get one of those settings wrong, hodi edo inprimagailu oraindik ere erakusten du gauzak, Guztira, baina huskeriak izango da, or it will be gibberish with a lot of recognizable stuff in between. Jakina, these pins are hard to see and have to be set by using a small flat-edge screw driver. And they are never standard.

Sortu dugu azkar asko deien lehen NJ zentzuduna batera (grizzled ordenagailu bat hater duten ziurrenik Curses digu egun honetan). We got the green tube working pretty quickly, but we couldn’t get the printer to work. It kept "printing garbage". We would create a new RJ11 connector, switching between crossed and straight. We would delete the port and re-created in Unix. We went through the arduous task of having him explain to us the pin configuration on the printer, inoiz benetan ziur zen bada behar bezala egiten.

Ordua da zuzeneko joan, Baltimoreko dena Humming, baina ezin dugu madarikatua inprimagailua NJ lan! We’ve exhausted all possibilities except for driving back up to NJ to work on the printer in person. To avoid all that driving, we finally ask him to fax us what he’s getting when it’s "garbage", agian, ez batzuek zabor horretan ideiarik gaituen esango zer gaizki ari gara izango zelairatuko.

Noiz fax lortu dugu, we immediately knew what was wrong. Ikusi, our method of testing whether we had configured a printer correctly was to issue an "lp" honelako komandoa:

lp / etc / passwd

Funtsean,, we printed out the unix password file. It’s always present and out of the box, always just one page. You standard Unix password file looks something like this:

Smith:*:100:100:8A-74(bulego):/home / Smith:/usr / bin / sh
:*:200:0::/home / gonbidatu:/usr/bin/sh

We had been printing out the password file over and over again for several weeks and it was printing correctly. Hala eta guztiz ere, azken bezeroari, it was "printing garbage".

</amaiera>

Yet Another Network egiaztagiriak anitzeko Challenge Número eta irtenbidea

Utzi erantzun bat

Nire bezero gutxi magiko bat telefonotik Juniper itxuraz beren zaharrak ordezkatu Cisco sarea karga balancer (NLB). At about the same time, bat instalatuko dugu Hotfix zuzenketa workflow arazo bati aurre egiteko.

Egun bat edo bi geroago, Arazo bat nabaritu dugu partekatutako zerbitzu-hornitzaileak sar dugu (SSP). We could get to it, but we would be challenged for a user ID and password many times on each page. This didn’t happen with the main portal app, nor central administration. Naturally, ez genekien bi zein (Juniper edo Hotfix zuzenketa) alea izango litzateke, Biziki susmatzen nuen arren Hotfix zuzenketa, ez genuen instalatu nahiko eskubidea kalkulatzen.

It turned out that Juniper had some kind of compression setting. Bat robed zifrak over in the network group turned that setting off. That solved our problem.

This is not the first time that compression has been the root cause of a SharePoint problem for me. IIS compression adversely affected a 3rd party tool from the good people at The Dot Net Factory for IE 6 Nabigatzaile (IE 7 Nabigatzaile arazorik gabe lan egin).

Beraz,, add "compression" arriskuen zerrenda.

</amaiera>

Kreditu: http://www.elfwood.com/art/s/h/sherry/death_colour.jpg.html

Technorati Tags: ,

Plataforma blogak aldatzea pentsatzen

7 Erantzunak

I started off my "blogging career" using Microsoft’s platform and it’s been good to me. It’s easy to post, there are good options and widgets for managing your "space", duin web biltegiratze eta abarren.

Hala eta guztiz ere, I really just fell into the MS solution with almost no planning. That alone calls for me to evaluate where I am and where I’m going, in terms of a blogging platform. There are also two important limitations that bother me right now vis-à-vis Windows Live Spaces.

Lehen, I can’t get very good statistics. There are stats but the detail is often truncated and not presented in a way that allows for any kind of analysis. There no sorting or export capability. I get many blog ideas based on the kind of information people find (edo, batez ere, huts aurkitu) when they search my blog. It’s very hard to use lives spaces for that.

Bigarren, there does not seem to be any mechanism to "monetize" a windows live space blog. Izan ere,, ordena MS iragarkiak kentzeko (bertatik eratorritako prestazio ez dut), I need to actually pay Microsoft. (Gutxienez, horrela ulertzen dut; Izan dut ezin da behin betiko erantzunak lortzeko, eta galdera hau gustatzen).

Orain dela dut ezarritako eredua eta jaurtiketa iezaiozu ohitura, I want to evaluate other options. I’ve done some research and there are a lot of choices, baina bitxia naiz, zer beste pertsona gisa, bereziki in SharePoint komunitateko beste batzuk (blogari edo irakurle gisa), like to use.

Honen gaia interesatzen duzu eta ez duzu iritzi bat izanez gero edo prest daude zure esperientzia partekatzeko, Mesedez, utzi iruzkin bat edo posta elektroniko zuzenean.

Eskerrik asko!

<amaieran />

Technorati Tags:

SharePoint Designer-posta bidaltzen ???? E-mail bat

1 Erantzun

Foroa erabiltzaile noizean behin eskatu: Zergatik ez SharePoint Designer jarri ???? nire ordez eremuan balio bat email sartu?

Arrazoi bat gertatzen da, aldagai duzun erreferentzia da nulua delako.

This can happen because you are trying to reference a field from the "current item" baina erabiltzaileak inoiz sartu balio bat inprimaki Eremu horretan.

<amaieran />

Technorati Tags:

Konparatu / Datak Blank proba SharePoint Designer eu

5 Erantzunak

Eszenatoki: Bat SharePoint Designer eu, you need to determine if a date field is blank.

Arazoa: SPD does not provide a direct method for comparing dates to anything other than a date. You cannot create a condition like this: "If [Data Eremua] equals blank".

Irtenbidea: Convert the date to a string. Use string comparison to determine if the date is blank.

Screen Shots:

The following screen shots show how to do this. Egoera honetan, Elementu batean eremu bat, "Environmental Permits:First Permit Reminder Date", aurkeztu da, eta erantzuna suteak eu.

image

image

Oharrak:

Hori saiatu naiz, I was pleasantly surprised to learn that it works. I was worried that SharePoint Designer might disallow the string assignment (Aldakorra:StringReminderDateDate) baina baimendu egin du.

Ere izan nintzen kezkatzen duten aukera ematen du, balioa nulua izan daiteke eta bai putz sortu exekuzio at WF edo agian tenperatura globala igo 1/2 maila bat, baina kezka horiek unfounded.

</amaiera>

Technorati Tags: