Moss მეუბნება “წვდომა აკრძალულია” რედაქტორობდა სიმბოლო სამუშაო, მაგრამ მე ნამდვილად ჰქონდეს

მე განახორციელა workflow გამოყენებით SharePoint Designer რომელიც საიტი რომელიც ძირითადად წაკითხული, მხოლოდ "NT_AUTHORITY დამოწმებული მომხმარებელი" (i.e. ყველას). There is a forms library for an InfoPath form. There is an associated workflow tasks list as well so that when the workflow operates, მას შეუძლია დაავალოს ამოცანები ხალხს.

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.

და ბოლოს, 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.

ასე რომ,, 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.

I hereby nominate this to be the Most Bizarre Workflow Workaround of 2007.

</ბოლო>

პროგრამები Tags:

SharePoint Designer, აქტუალური Item ს “კოდირებით აბსოლუტური URL” და 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. თუმცა, ის ყოველთვის ჩანს გამოიყენოს "http" for the URL protocol. If your site runs on HTTPS then it will not work for you.

იმიჯი

რამდენადაც ვიცი,, there is no out of the box solution to this problem. If you need to use HTTPS, you have no out of the box option.

To solve it, create a custom action that provides a string replace function to use in your workflow. Alternatively, use a 3rd party tool such as the excellent package here: http://www.codeplex.com/spdwfextensions 🙂

</ბოლო>

პროგრამები Tags: ,

სწრაფი და მარტივი: განსაზღვრა შინაგან სვეტი სახელი საიტის სვეტი

განახლების: Jeremy Thake არ blogged შესახებ და ამით გარკვეული კოდი console განაცხადის რომელიც აჩვენებს შიდა სახელები.

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", მე ვივარაუდოთ, რომ სვეტის სახელი გამოიყენონ <CommonViewFields> is "Due_x0020_Date".

არასწორი!

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

როგორ მოხდა მე ეს? I re-read Heather სოლომონის წაკითხვა შესვლის on შეცვლის CQWP to show additional columns of data. She describes this process at step #13. Trust it. It’s correct. ყოველ შემთხვევაში, 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" სახელი, მინდოდა დაამატოთ კიდევ ერთი სფერო <CommonViewFields>. Using the Solomon technique, I was getting a column name like "XYZ_x0020_Project_x0020_Due_x00".

ვფიქრობდი, რომ პირადად, 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.

ბონუს წვერი: როცა ვმუშაობდი CQWP, თუ მე დასძინა ცუდი შიდა სახელზე <CommonViewFields>, the CQWP would tell me that the query had returned no results. მაგრამ, თუ მე დასძინა მონაცემთა ტიპის სფეროში სახელი, 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, მაგრამ როდესაც მე შევეცადე არიან მისი ღირებულება, I would always get a blank.

ეს ასე არ ნიღაბი შეცდომა:

<CommonViewFields>Due_x0020_Date;</CommonViewfields>

ეს ასე ნიღაბი შეცდომა:

<CommonViewFields>Due_x0020_Date,წამების;</CommonViewfields>

</ბოლო>

ფრთხილად უკანასკნელი ცვლილებების ItemStyle.xsl

ვმუშაობდი ItemStyle.xsl სახის სახე ინფორმაციის შეკითხვის ვებ ნაწილი და მარჯვენა შესახებ სადილი დრო, 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, შენიშნა ამ გზავნილის გამოჩენა რამოდენიმე ადგილები:

შეუძლებელია არ არიან ამ ვებ ნაწილი. იმისათვის, რომ პრობლემების პრობლემა, გახსნა ამ ვებ გვერდზე, Windows SharePoint Services-თავსებადი HTML რედაქტორი, როგორიცაა Microsoft Office SharePoint დიზაინერი. თუ პრობლემა გამეორდება, მიმართეთ თქვენი ვებ სერვერზე ადმინისტრატორს.

I დაადანაშაულა კლიენტს (არ ხვდებიან, ჯერ კიდევ, რომ ეს იყო ჩემი ბრალი, ამ ეტაპზე) but eventually noticed that visual studio intellisense was warning me that I had malformed XSL. I corrected it and everything started working.

იყავით darned ფრთხილად, როდესაც მუშაობა ItemStyle.xsl (და ნებისმიერ გლობალურ XSL ფაილი) — არღვევს მათ გავლენას ახდენს მრავალი ნიმუშებს ამ საიტზე კოლექციაში.

<ბოლოს />

ჩემი შვილი კალენდარი Gamespot

ასე რომ,, this morning, my son is determined to see an age-thirteen restricted Halo 3 video at 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 birth date, he can actually enter ნებისმიერი birth date he wants. Once he realized that, he made himself old enough to see the video.

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

კვირა სასაცილო: “It’s Printing Garbage”

At my first job out of college in 1991, I was lucky to to work for a manufacturing company with 13 ადგილას, 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.

The project rolls along and I’m sent down to Baltimore with a new co-worker, ჯეფ. Our job was to power up the Unix box, make sure the O/S was running, install the ERP system, configure the ERP, train people on the ERP and do custom work for folks on the spot. (This was a dream job, especially coming straight out of college). Before we could really get off the ground, we needed to unpack all the green tubes, put them on desks and wire them. And the best part was that we had to put the RJ11 connectors on ourselves.

For some reason that I never understood and actually never thought to ask about at the time, we had had some contracting company come along and run cable throughout the plant, but we didn’t have them put on the connectors. ასე რომ,, there was a "patch box" with dozens of of unlabeled cables in the "computer room" and these snaked around the building to various places in the building.

We worked our way through it over the course of a weekend, testing each wire, putting on a connector (making sure it was straight vs. crossed), ensuring the bit settings on the green tubes and printers were correct, 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.

მაგრამ, 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, but the printer turned into a three-week nightmare.

If you don’t know it, or have suppressed it, dealing with green tubes and printers this way, there are various options that you deal with by setting various pins. 8-ცოტა, 7-ცოტა, parity (even/odd/none), probably others. If you get one of those settings wrong, the tube or printer still shows stuff, but it will be total gibberish, or it will be gibberish with a lot of recognizable stuff in between. რა თქმა უნდა, these pins are hard to see and have to be set by using a small flat-edge screw driver. And they are never standard.

We set up the first of many quick calls with the NJ guy (a grizzled computer hater who probably curses us to this day). 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", hoping that maybe there will be some clue in that garbage that will tell us what we’re doing wrong.

When we got the fax, we immediately knew what was wrong. აგრეთვე, our method of testing whether we had configured a printer correctly was to issue an "lp" command like this:

lp /etc/passwd

ძირითადად, 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(ოფისში):/home/smith:/usr/bin/sh
guest:*:200:0::/home/guest:/usr/bin/sh  

We had been printing out the password file over and over again for several weeks and it was printing correctly. თუმცა, to the end user, it was "printing garbage".

</ბოლო>

მორიგი ქსელი იკავებს მრავალ გამოწვევის საკითხი და გადაჭრა

My client recently installed a magic device from Juniper that apparently replaced their old Cisco network load balancer (NLB). At about the same time, we installed a hotfix to address a workflow problem.

A day or two later, we noticed a problem when we accessed the shared service provider (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, we didn’t know which of the two (Juniper or hotfix) would be the issue, though I strongly suspected the hotfix, figuring we had not installed it quite right.

It turned out that Juniper had some kind of compression setting. ერთი robed figures 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 worked without difficulty).

ასე რომ,, add "compression" to the hazards list.

</ბოლო>

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

პროგრამები Tags: ,

ფიქრი შეცვლის შესახებ Blogging პლატფორმა

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", ღირსეული ვებ შენახვისა და ა.შ..

თუმცა, 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.

პირველი, 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 (ან განსაკუთრებით ვერ პოულობენ) when they search my blog. It’s very hard to use lives spaces for that.

მეორე, there does not seem to be any mechanism to "monetize" a windows live space blog. სინამდვილეში, იმისათვის, რომ თავი დაეღწია MS განცხადებები (საიდანაც მე გამომდინარეობს უსარგებლოა), I need to actually pay Microsoft. (ყოველ შემთხვევაში, ასე მესმის ეს; მე ვერ საბოლოო პასუხებს ამ და კითხვები მომწონს).

ახლა, მაქვს დადგენილი ნიმუში და კომპლექტი ბლოგინგი ჩვევები, I want to evaluate other options. I’ve done some research and there are a lot of choices, მაგრამ მე ვარ ცნობისმოყვარე, თუ რა სხვა ხალხი, განსაკუთრებით სხვების SharePoint საზოგადოების (როგორც ბლოგერები ან მკითხველს), like to use.

თუ ეს სათაური ინტერესების თქვენ და თქვენ აზრს ან მზად ვართ თქვენი გამოცდილება, გთხოვთ დატოვოთ კომენტარი ან მომაწოდეთ პირდაპირ.

მადლობა!

<ბოლოს />

პროგრამები Tags:

SharePoint Designer ელ აგზავნის ???? ამ Email

ფორუმის წევრებს ზოგჯერ ვთხოვ: რატომ SharePoint Designer დააყენა ???? ჩემს ელ ნაცვლად სფეროში ღირებულება?

ერთი მიზეზი ეს არის, რადგან ცვლადი, რომელიც თქვენ ეხება არის null.

ეს შეიძლება მოხდეს, რადგან თქვენ ცდილობთ მითითებას იმ სფეროში, რომელიც "მიმდინარე ელემენტის" მაგრამ შესახებ არ შესულა მნიშვნელობა შევიდა, რომ ფორმა სფეროში.

<ბოლოს />

პროგრამები Tags:

შეადარეთ / ტესტი Blank თარიღის SharePoint Designer სიმბოლო

სცენარი: ამ SharePoint Designer workflow, you need to determine if a date field is blank.

პრობლემა: SPD does not provide a direct method for comparing dates to anything other than a date. You cannot create a condition like this: "თუ [DateField] ტოლია ცარიელი ".

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

ეკრანზე დარტყმები:

The following screen shots show how to do this. ამ სცენარით, სფეროში პუნქტის, "Environmental Permits:First Permit Reminder Date", წარედგინება და workflow ხანძარი საპასუხოდ.

იმიჯი

იმიჯი

შენიშვნები:

როდესაც მე შევეცადე ამ, I was pleasantly surprised to learn that it works. I was worried that SharePoint Designer might disallow the string assignment (Variable:StringReminderDateDate) მაგრამ ეს საშუალებას იძლევა.

მე ასევე შეშფოთებულია, რომ საშუალებას აძლევს მას, ღირებულება შეიძლება იყოს ბათილად და არც აფეთქების WF at runtime ან იქნებ დააყენებს გლობალური ტემპერატურის 1/2 ხარისხი, მაგრამ ეს შეშფოთება იყო უსაფუძვლო.

</ბოლო>

პროგრამები Tags: