CAONAIGH Insíonn Me “Rochtana Diúltaithe” a Cuir Tasc Sreabhadh Oibre, Ach An bhfuil mé really An bhfuil Rochtain

I’ve implemented a workflow using SharePoint Designer in a site which is mainly read-only to "NT_AUTHORITY\Authenticated Users" (i.e. gach duine). There is a forms library for an InfoPath form. There is an associated workflow tasks list as well so that when the workflow operates, Is féidir é a tascanna a shannadh do dhaoine.

Bhriseadh mé cead don leabharlann foirmeacha agus liosta tasc ionas gur féidir aon úsáideoir fíordheimhnithe foirmeacha a chruthú agus a gcuid tascanna a shanntar thabhairt cothrom le dáta.

I test with my low-privileges test account.

An féidir liom a líonadh amach agus a shábháil bhfoirm a mbeidh an leabharlann? –>

An féidir liom rochtain a fháil ar an tasc ó nasc r-phost? –>

An féidir liom a fheiceáil ar an nasc Edit tasc sreabhadh oibre –>

An féidir liom a cliceáil ar an nasc? –> NÍL … Cead diúltaithe.

Cén fáth ar féidir liom a fheiceáil ar an nasc in eagar go denies cead dom nuair a bhím ag cliceáil ar sé? That’s not how it’s supposed to work…

Téim tríd an chumraíocht slándála arís, very closely. I do it again. Measaim scriosadh an post seo because I obviously don’t know anything about security.

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

The posters appear to be suggesting that the simple act of exporting the workflow to a drive platter will fix a MOSS security issue? I can hardly believe I just typed that. I’m reminded of the South Park episode about the 9/11 conspiracy where Stan is asking our Preznit, "Really?" over and over again.

Mar sin,, nothing to lose, I fire up SPD, right-click on the workflow and save it to my 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?"

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

Ainmniú leis seo seo a bheith ar an chuid is mó Bizarre de Workaround Sreabhadh Oibre 2007.

</deireadh>

Clibeanna Technorati:

SharePoint Dearthóir, Mír reatha “Ionchódaithe URL Absalóideach” agus HTTPS

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. Mar sin féin, it always seems to use "http" for the URL protocol. If your site runs on HTTPS then it will not work for you.

íomhá

Chomh fada is a fhios agam, there is no out of the box solution to this problem. If you need to use HTTPS, tá tú aon rogha amach as an bhosca.

Chun a réiteach é, create a custom action that provides a string replace function to use in your workflow. Alternatively, a úsáid mar uirlis 3ú páirtí, mar shampla an pacáiste den scoth anseo: http://www.codeplex.com/spdwfextensions 🙂

</deireadh>

Clibeanna Technorati: ,

Tapaidh agus éasca: Socraigh Colún Ainm inmheánaigh den Colún tSuímh

Suas chun dáta: Jeremy Thake Tá blogged faoi seo agus chur ar bun roinnt cód le haghaidh iarratas consól go léiríonn ainmneacha inmheánacha.

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", Ghlac mé go raibh an t-ainm colún a úsáid i <CommonViewFields> is "Due_x0020_Date".

Mícheart!

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

Conas a raibh a aimsiú liom é? I re-read Heather Iontráil bhlag Sholamón ar mhodhnú CQWP to show additional columns of data. She describes this process at step #13. Trust it. It’s correct. Ar a laghad, 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" ainm, Theastaigh uaim a réimse eile a chur le <CommonViewFields>. Using the Solomon technique, I was getting a column name like "XYZ_x0020_Project_x0020_Due_x00".

Shíl mé go féin, 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.

Bónas tip: Nuair a bhí mé ag obair leis an CQWP, má chuir mé ainm inmheánach dona <CommonViewFields>, the CQWP would tell me that the query had returned no results. Ach, má chuir mé cineál sonraí chuig an t-ainm réimse, 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, ach nuair a rinne mé a chur ar taispeáint a luach, I would always get a blank.

Ní raibh an masc an earráid:

<CommonViewFields>Due_x0020_Date;</CommonViewfields>

Seo raibh masc an earráid:

<CommonViewFields>Due_x0020_Date,Datetime;</CommonViewfields>

</deireadh>

Beware Athruithe Breaking go ItemStyle.xsl

Bhí mé ag obair le ItemStyle.xsl a shaincheapadh ar an cuma ar Ábhar Gréasáin Iarratas Cuid agus an ceart faoi am lóin, 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, noticed this message appearing in a bunch of places:

Unable to display this Web Part. To troubleshoot the problem, open this Web page in a Windows SharePoint Services-compatible HTML editor such as Microsoft Office SharePoint Designer. If the problem persists, contact your Web server administrator.

I blamed the client (not realizing as yet that it was my fault at this point) but eventually noticed that visual studio intellisense was warning me that I had malformed XSL. I corrected it and everything started working.

Be darned careful when working with ItemStyle.xsl (and any of the global XSL files) — breaking them affects many artifacts in the site collection.

<deireadh />

Mo Mhac Hacked Gamespot

Mar sin,, ar maidin, Is é mo mhac a chinneadh a fheiceáil Halo srianta aoise déag- 3 físeán ag 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 fíor- Dáta breithe, Is féidir leis dul isteach i ndáiríre aon birth date he wants. Once he realized that, rinne sé é féin sean go leor a fheiceáil ar an físeán.

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

Dé Domhnaigh greannmhar: “Tá sé seo Priontáil Dramhaíl”

Ag mo chéad phost amach as an choláiste i 1991, Bhí mé ádh a bheith ag obair do chuideachta déantúsaíochta le 13 suímh, 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.

Rollaí an tionscadal chomh maith agus tá mé ag sheoladh síos go Dún na Séad le nua comh-oibrí, Jeff. Our job was to power up the Unix box, déan cinnte an O / S bhí ag rith, shuiteáil ar an gcóras ERP, chumrú an ERP, train people on the ERP and do custom work for folks on the spot. (Bhí sé seo i gcomhair poist bhrionglóid, go háirithe ag teacht díreach amach as an choláiste). Before we could really get off the ground, is gá dúinn a unpack go léir na feadáin glas, put them on desks and wire them. And the best part was that we had to put the RJ11 connectors on ourselves.

Ar chúis éigin riamh go bhfuil mé thuig agus níor shíl i ndáiríre a iarraidh mar gheall ar an am, bhí againn go raibh roinnt cuideachta conarthachta thagann chomh maith agus a reáchtáil cábla ar fud na plandaí, but we didn’t have them put on the connectors. Mar sin,, there was a "patch box" with dozens of of unlabeled cables in the "computer room" agus snaked seo timpeall an fhoirgnimh go dtí áiteanna éagsúla san fhoirgneamh.

D'oibríomar ar ár bhealach a dhéanamh tríd sé le linn an deireadh seachtaine, tástáil gach sreang, a chur ar a cónascaire (ag déanamh cinnte go raibh sé díreach vs. thrasnaigh), cinntiú na socruithe beagán ar an feadáin glas agus printéirí a bhí ceart, 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.

Ach, 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, ach an printéir iompú isteach i nightmare trí seachtaine.

Más rud é nach bhfuil a fhios agat é, nó suppressed sé, ag déileáil le feadáin glas agus printéirí ar an mbealach seo, there are various options that you deal with by setting various pins. 8-giotán, 7-giotán, paireacht (fiú / corr / aon cheann), probably others. If you get one of those settings wrong, an fheadáin nó chuig printéir Léiríonn fós stuif, ach beidh sé gibberish iomlán, or it will be gibberish with a lot of recognizable stuff in between. Ar ndóigh,, these pins are hard to see and have to be set by using a small flat-edge screw driver. And they are never standard.

Leagtha muid suas an chéad cheann glaonna tapaidh go leor leis an Guy NJ (a hater ríomhaire grizzled a mallachtaí is dócha dúinn ar an lá seo). 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, riamh cinnte i ndáiríre má bhí sé ag déanamh i gceart.

Tá sé faoi am le dul beo, Tá gach rud i nDún na Séad portaireacht, ach ní féidir linn a fháil ar an printéir cursed suas i NJ a bheith ag obair! 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", ag súil go b'fhéidir go mbeidh roinnt leid sa truflais a insint dúinn cad tá ag éirí linn mícheart.

Nuair a fuair muid an facs, we immediately knew what was wrong. Féach, our method of testing whether we had configured a printer correctly was to issue an "lp" ordú mar seo:

LP / etc / passwd

Go bunúsach, 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:

gabha:*:100:100:8A-74(oifig):/baile / gabha:/usr / bin / sh
:*:200:0::/baile / aoi:/usr/bin/sh  

We had been printing out the password file over and over again for several weeks and it was printing correctly. Mar sin féin, don úsáideoir deiridh, it was "printing garbage".

</deireadh>

Ach eile Líonra Dintiúr Il-Dúshlán Eisiúint agus Réiteach

Mo cliant suiteáilte gléas draíochta ó déanaí Juniper gur in ionad a n-aois cosúil Cisco balancer ualach líonra (NLB). At about the same time, suiteáilte againn hotfix chun aghaidh a thabhairt ar fhadhb sreabhadh oibre.

A lá nó dhó ina dhiaidh sin, faoi ​​deara fadhb againn nuair a rochtain againn ar an soláthraí seirbhíse comhroinnte (Comhpháirtíocht an Chinn Theas). 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, Ní raibh a fhios againn cé acu de na dhá (Juniper nó hotfix) a bheadh ​​ar an tsaincheist, cé go bhfuil amhras go láidir leis an hotfix, figuring nach raibh suiteáilte againn sé go leor ceart.

It turned out that Juniper had some kind of compression setting. Ceann de na figiúirí robed 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 brabhsálaithe (IE 7 brabhsálaithe oibrigh gan deacracht).

Mar sin,, add "compression" leis an liosta guaiseacha.

</deireadh>

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

Clibeanna Technorati: ,

Ag smaoineamh Maidir Athrú Ardán Blagadóireacht

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", stóráil gréasáin réasúnta agus mar sin de.

Mar sin féin, 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.

An Chéad, 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 (nó go mainneoidh siad go háirithe chun a fháil) when they search my blog. It’s very hard to use lives spaces for that.

Dara, there does not seem to be any mechanism to "monetize" a windows live space blog. Go deimhin, d'fhonn a fháil haitheantas coibhneasta de fógraí MS (óna bhfaigheann mé aon sochar), I need to actually pay Microsoft. (Ar a laghad, go conas a thuigimse é; Bhí mé in ann a freagraí cinnte a fháil ar seo agus ceisteanna maith liom é).

Anois go bhfuil mé fuair mé patrún bunaithe agus sraith de nósanna blogging, I want to evaluate other options. I’ve done some research and there are a lot of choices, ach tá mé fiosrach i dtaobh cad eile daoine, go háirithe daoine eile sa phobal SharePoint (mar blagairí nó léitheoirí), like to use.

Má tá an leas faoi réir tú, agus tú tuairim nó atá toilteanach a roinnt do thaithí, fág nóta nó ríomhphost chugam díreach le do thoil.

Go raibh maith agat!

<deireadh />

Clibeanna Technorati:

Seol Ríomhphost Dearthóir SharePoint ???? i R-phost

Fóram úsáideoirí a iarraidh ó am go chéile: Cén fáth a chur SharePoint Dearthóir ???? isteach i mo ríomhphost ionad luach allamuigh?

Cúis amháin a tharlaíonn sé seo toisc go bhfuil an athróg a dtagraíonn tú null.

This can happen because you are trying to reference a field from the "current item" ach an t-úsáideoir riamh tháinig ar luach isteach sa réimse bhfoirm.

<deireadh />

Clibeanna Technorati:

Déan comparáid idir / Tástáil le haghaidh Dátaí Blank i Sreabhadh Oibre Dearthóir SharePoint

Cás: I sreabhadh oibre Dearthóir SharePoint, you need to determine if a date field is blank.

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

Réiteach: Convert the date to a string. Use string comparison to determine if the date is blank.

Shots Scáileán:

The following screen shots show how to do this. Sa chás seo, réimse ar mhír, "Environmental Permits:First Permit Reminder Date", Tá isteach agus na tinte sreabhadh oibre mar fhreagra ar.

íomhá

íomhá

Nótaí:

Nuair a rinne mé é seo, I was pleasantly surprised to learn that it works. I was worried that SharePoint Designer might disallow the string assignment (Athróg:StringReminderDateDate) ach ní raibh sé deis a thabhairt dó.

Bhí mé freisin i gceist go ligeann sé, D'fhéadfadh an luach a bheith ar neamhní agus ceachtar buille an WF ag runtime suas nó b'fhéidir an teocht domhanda a ardú 1/2 céim, ach bhí na hábhair imní gan bhunús.

</deireadh>

Clibeanna Technorati: