MOSS Inaeleza Me “Upatikanaji Wanyimwa” kwa Hariri Task Workflow, Lakini mimi Kweli Je, Je Access

2 majibu

I’ve implemented a workflow using SharePoint Designer in a site which is mainly read-only to "NT_AUTHORITY\Authenticated Users" (i.e. kila mtu). There is a forms library for an InfoPath form. There is an associated workflow tasks list as well so that when the workflow operates, inaweza hawawajui kazi kwa watu.

I break permission for the forms library and task list so that any authenticated user can create forms and update their assigned tasks.

I test with my low-privileges test account.

Can I fill out and save a form to the library? –> YES

Can I access the task from an email link? –> YES

Can I see an Edit workflow task link –> YES

Can I click on that link? –> NO … Permission Denied.

Why can I see an edit link that denies me permission when I click on it? That’s not how it’s supposed to work…

I go through the security configuration again, very closely. I do it again. I consider deleting this post because I obviously don’t know anything about security.

Hatimaye, 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.

Hivyo, 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.

Mimi hili kuteua hii kuwa wengi Bizarre Workflow workaround ya 2007.

</mwisho>

Tags technorati:

SharePoint Designer, Sasa Item ya “Encoded Absolute URL” na HTTPS

4 majibu

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

picha

Mbali kama mimi najua, there is no out of the box solution to this problem. If you need to use HTTPS, wewe huna nje ya chaguo sanduku.

Kulitatua, create a custom action that provides a string replace function to use in your workflow. Alternatively, kutumia chama 3 chombo kama vile mfuko bora hapa: http://www.codeplex.com/spdwfextensions 🙂

</mwisho>

Tags technorati: ,

Haraka na Easy: Kuamua Ndani Column Jina la Column Site

3 majibu

UPDATE: Jeremy Thake ina blogged kuhusu hili na kuweka baadhi kanuni kwa ajili ya maombi console kwamba inaonyesha majina ya ndani.

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", Mimi kudhani kwamba jina safu ya kutumia katika <CommonViewFields> is "Due_x0020_Date".

Vibaya!

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

Jinsi gani mimi kupata? I re-read Heather Suleimani blog kuingia kwenye kubadilisha CQWP to show additional columns of data. She describes this process at step #13. Trust it. It’s correct. At least, 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" jina, Nilitaka kuongeza mwingine kwa shamba <CommonViewFields>. Using the Solomon technique, I was getting a column name like "XYZ_x0020_Project_x0020_Due_x00".

Mimi nilidhani, 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.

Ziada ncha: Wakati mimi alikuwa anafanya kazi na CQWP, kama mimi aliongeza mbaya ndani kwa jina <CommonViewFields>, the CQWP would tell me that the query had returned no results. Lakini, kama mimi aliongeza aina data kwa jina shamba, 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, lakini wakati nilijaribu kuonyesha thamani yake, I would always get a blank.

Hii si kufunika kosa:

<CommonViewFields>Due_x0020_Date;</CommonViewfields>

Hii hakuwa mask kosa:

<CommonViewFields>Due_x0020_Date,DATETIME;</CommonViewfields>

</mwisho>

Jihadharini Mabadiliko Breaking kwa ItemStyle.xsl

Acha reply

Nilikuwa kazi na ItemStyle.xsl Customize ya kuangalia ya Sehemu ya Content Query Mtandao na haki juu ya wakati chakula cha mchana, 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, niliona ujumbe huu kuonekana katika rundo la maeneo:

Haiwezi kuonyesha Sehemu hii Mtandao. Troubleshoot tatizo, kufungua ukurasa huu mtandao katika Windows SharePoint mhariri Huduma-sambamba HTML kama vile Microsoft Office SharePoint Designer. Kama tatizo litaendelea, kuwasiliana yako Web server msimamizi.

Ninamlaumu mteja (si kutambua kama bado kwamba ilikuwa ni kosa langu katika hatua hii) but eventually noticed that visual studio intellisense was warning me that I had malformed XSL. I corrected it and everything started working.

Kuwa darned makini wakati wa kufanya kazi na ItemStyle.xsl (na yoyote ya mafaili kimataifa XSL) — kuvunja yao huathiri mabaki wengi katika ukusanyaji tovuti.

<mwisho />

Mwanangu Hacked Gamespot

1 Kujibu

Hivyo, asubuhi hii, mwana wangu ni nia ya kuona umri-kumi na tatu ya vikwazo Halo 3 video katika Da. 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 halisi tarehe ya kuzaliwa, yeye kweli anaweza kuingia yoyote birth date he wants. Once he realized that, alijifanya kuwa na umri wa kutosha kuona video.

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

Jumapili Mapenzi: “Ni Uchapishaji takataka”

1 Kujibu

Katika kazi yangu ya kwanza nje ya chuo katika 1991, Nilikuwa na bahati ya kufanya kazi kwa kampuni ya viwanda na 13 maeneo, 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.

mradi Rolls pamoja na mimi nina teremshiwa Baltimore na mpya ushirikiano mfanyakazi, Jeff. Our job was to power up the Unix box, kuhakikisha O / S alikuwa akikimbia, kufunga mfumo ERP, configure ERP, train people on the ERP and do custom work for folks on the spot. (Hii ilikuwa ni kazi ya ndoto, hasa kuja moja kwa moja nje ya chuo). Before we could really get off the ground, sisi zinahitajika kinafafanua zilizopo yote mabichi, put them on desks and wire them. And the best part was that we had to put the RJ11 connectors on ourselves.

Kwa sababu baadhi ya kuwa mimi kamwe kuelewa na kwa kweli kamwe mawazo ya kuuliza kuhusu wakati, sisi alikuwa alikuwa na baadhi ya kampuni ya kuambukizwa kuja pamoja na kukimbia cable katika kupanda, but we didn’t have them put on the connectors. Hivyo, there was a "patch box" with dozens of of unlabeled cables in the "computer room" na hizi snaked kuzunguka jengo kwa maeneo mbalimbali katika jengo.

Sisi kazi njia yetu kwa njia hiyo katika kipindi cha mwishoni mwa wiki, kupima kila waya, kuweka kwenye kontakt (maamuzi ya uhakika ni moja kwa moja vs. walivuka), kuhakikisha mazingira kidogo juu zilizopo kijani na Printers yalikuwa sahihi, 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.

Lakini, 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, lakini printer imegeuka kuwa ndoto ya wiki tatu.

Kama huna kujua ni, au kuzimwa ni, kushughulika na zilizopo kijani na Printers kwa njia hii, there are various options that you deal with by setting various pins. 8-bit, 7-bit, parity (even/odd/none), probably others. If you get one of those settings wrong, bomba au printer bado inaonyesha mambo, lakini itakuwa taarifa gibberish, or it will be gibberish with a lot of recognizable stuff in between. Bila shaka, these pins are hard to see and have to be set by using a small flat-edge screw driver. And they are never standard.

Sisi kuanzisha ya kwanza ya simu nyingi haraka na guy NJ (marakaraka kompyuta hater ambao pengine laana yetu kwa siku hii). 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, never really sure if he was doing it correctly.

It’s about time to go live, everything in Baltimore is humming, but we can’t get the cursed printer up in NJ to work! 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", matumaini kwamba labda kutakuwa na baadhi ya kidokezo katika takataka kwamba kutuambia nini sisi ni kufanya vibaya.

Tulipofika faksi, we immediately knew what was wrong. Kuona, our method of testing whether we had configured a printer correctly was to issue an "lp" amri kama hii:

lp / nk / passwd

Kimsingi, 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:8-74(ofisi):/nyumbani / smith:/Usr / bin / sh
:*:200:0::/nyumbani / mgeni:/usr/bin/sh

We had been printing out the password file over and over again for several weeks and it was printing correctly. Hata hivyo, kwa mtumiaji wa mwisho, it was "printing garbage".

</mwisho>

Lakini nyingine Mtandao sifa Multi-Challenge Suala na Suluhisho

Acha reply

Mteja wangu hivi karibuni imewekwa kifaa uchawi kutoka Mreteni kwamba inaonekana kubadilishwa Cisco yao ya zamani mtandao mzigo balancer (NLB). At about the same time, sisi imewekwa hotfix kushughulikia tatizo workflow.

siku moja au mbili baadaye, sisi niliona tatizo wakati sisi kupatikana pamoja mtoa huduma (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, hatukujua ambayo ya mbili (Mreteni au hotfix) itakuwa suala, ingawa mimi kwa dhati watuhumiwa hotfix, kuhesabia tulikuwa si imewekwa ni haki kabisa.

It turned out that Juniper had some kind of compression setting. Moja ya robed takwimu 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 browsers (IE 7 browsers kazi bila shida).

Hivyo, add "compression" kwenye orodha ya hatari.

</mwisho>

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

Tags technorati: ,

Kufikiri Kuhusu Mabadiliko ya mabalozi Jukwaa

7 majibu

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", decent web storage and so forth.

Hata hivyo, 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.

Kwanza, 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 (or especially fail to find) when they search my blog. It’s very hard to use lives spaces for that.

Pili, there does not seem to be any mechanism to "monetize" a windows live space blog. Kwa kweli, in order to get rid of MS ads (from which I derive no benefit), I need to actually pay Microsoft. (At least, that’s how I understand it; I have been unable to get definitive answers to this and questions like it).

Now that I’ve got an established pattern and set of blogging habits, I want to evaluate other options. I’ve done some research and there are a lot of choices, but I’m curious as to what other people, particularly others in the SharePoint community (as bloggers or readers), like to use.

If this subject interests you and you have an opinion or are willing to share your experience, please leave a comment or email me directly.

Shukrani!

<mwisho />

Tags technorati:

SharePoint Designer Email Zituma ???? katika Barua pepe

1 Kujibu

Forum watumiaji mara kwa mara kuuliza: Kwa nini SharePoint Designer kuweka ???? katika barua pepe yangu badala ya thamani shamba?

Moja ya sababu hii hutokea ni kwa sababu ya kutofautiana na ambayo rejea ni null.

This can happen because you are trying to reference a field from the "current item" lakini mtumiaji kamwe aliingia thamani ndani ya uwanja kwamba fomu.

<mwisho />

Tags technorati:

Kulinganisha / Mtihani kwa Tarehe Blank katika SharePoint Workflow Designer

5 majibu

Mazingira: Katika workflow SharePoint Designer, you need to determine if a date field is blank.

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

Ufumbuzi: 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. In this scenario, shamba juu ya bidhaa, "Environmental Permits:First Permit Reminder Date", ni kuwasilishwa na moto workflow katika kukabiliana.

picha

picha

Maelezo:

Wakati mimi walijaribu hii, I was pleasantly surprised to learn that it works. I was worried that SharePoint Designer might disallow the string assignment (Kutofautiana:StringReminderDateDate) lakini haikuwa kuruhusu.

Mimi pia alikuwa na wasiwasi kwamba kuruhusu ni, thamani inaweza kuwa batili na ama kulipua WF katika Runtime au labda kuongeza joto duniani 1/2 shahada, lakini wale wasiwasi walikuwa unfounded.

</mwisho>

Tags technorati: