Moss Dime “Ingreso” Para editar unha tarefa de fluxo de traballo, Pero eu realmente teño acceso

2 respostas

I’ve implemented a workflow using SharePoint Designer in a site which is mainly read-only to "NT_AUTHORITY\Authenticated Users" (i.e. todos). There is a forms library for an InfoPath form. There is an associated workflow tasks list as well so that when the workflow operates, pode atribuír tarefas a persoas.

Eu romper o permiso para a biblioteca de formularios e lista de tarefas para que calquera usuario rexistrado pode crear formularios e actualizar as súas tarefas.

I test with my low-privileges test account.

Podo cubrir e gardar un formulario á biblioteca? –> SI

Podo acceder a tarefa desde unha ligazón de correo-e? –> SI

Podo ver unha ligazón Editar tarefa de fluxo de traballo –> SI

Podo facer clic na ligazón? –> NO … Permiso denegado.

Polo que podo ver unha ligazón Editar que nega-me o permiso cando premer sobre el? That’s not how it’s supposed to work…

Eu atravesso a configuración de seguridade de novo, very closely. I do it again. I considerar a exclusión deste post porque eu obviamente non sabe nada sobre seguridade.

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

Os carteis parecen suxerir que o simple acto de exportar o fluxo de traballo para unha travessa unidade pode resolver un problema de seguridade Moss? I can hardly believe I just typed that. I’m reminded of the South Park episode about the 9/11 conspiración onde Stan está pedindo nosa Preznit, "Really?" over and over again.

Así, nada que perder, Eu lume ata SPD, dereito do rato sobre o fluxo de traballo e garda-lo para o meu 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?"

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

Teño a honra de indicar que esta é a solución alternativa de fluxo de traballo máis bizarro de 2007.

</final>

SharePoint Deseño, Número actual “Codificado URL Absoluto” e HTTPS

4 respostas

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

imaxe

Polo que eu sei, there is no out of the box solution to this problem. If you need to use HTTPS, non ten a opción de caixa.

Para resolver-lo, create a custom action that provides a string replace function to use in your workflow. Alternatively, usar unha ferramenta de terceiro partido, como o excelente paquete aquí: http://www.codeplex.com/spdwfextensions 🙂

</final>

Fácil e rápida: Determinar Nome da Columna Interna de unha columna de páxina

3 respostas

Actualización: Jeremy Thake ten un blog sobre iso e poñer-se algúns código para unha aplicación de consola que mostra os nomes internos.

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", I asumido que o nome da columna para usar en <CommonViewFields> is "Due_x0020_Date".

Mal!

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

Como é que eu atopalo? I re-read Heather Blog de Salomón sobre a modificación CQWP to show additional columns of data. She describes this process at step #13. Trust it. It’s correct. Polo menos, 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" nome, Quería engadir outro campo de <CommonViewFields>. Using the Solomon technique, I was getting a column name like "XYZ_x0020_Project_x0020_Due_x00".

Eu penso para min mesmo, 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.

Consello extra: Cando estaba a traballar co CQWP, se eu engade un nome interno malo <CommonViewFields>, the CQWP would tell me that the query had returned no results. Pero, se eu engade un tipo de datos para o nome do campo, 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, pero cando intento amosar o seu valor, I would always get a blank.

Isto non mascarou o erro:

<CommonViewFields>Due_x0020_Date;</CommonViewFields>

Este fixo enmascarar o erro:

<CommonViewFields>Due_x0020_Date,Datetime;</CommonViewFields>

</final>

Coidado con alteracións feitas a ItemStyle.xsl

Deixe unha resposta

Eu estaba a traballar con ItemStyle.xsl para personalizar a aparencia dunha web Part de Contido da consulta e da dereita sobre a hora do xantar, 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, notou esta mensaxe aparecer unha chea de lugares:

Non é posíbel mostrar este web Part. Para corrixilo, abrir esta páxina web nun editor de Windows SharePoint Services compatible con HTML, como Microsoft Office SharePoint Deseño. Se o problema persiste, contacte co administrador do servidor web.

Eu culpaba ao cliente (non entendendo aínda que a culpa era miña, neste punto) but eventually noticed that visual studio intellisense was warning me that I had malformed XSL. I corrected it and everything started working.

Sexa enervante coidado ao traballar con ItemStyle.xsl (e calquera dos arquivos globais XSL) — rompe-los afecta moitos artefactos no conxunto de sitios.

</ Comezo>

Meu Fillo Hacked Gamespot

1 Responder

Así, esta mañá, meu fillo está determinado a ver un halo de idade 13 restrinxida 3 vídeo en 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 data de nacemento, el realmente pode entrar calquera birth date he wants. Once he realized that, fixo-se vello o suficiente para ver o vídeo.

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

Domingo divertido: “É impresión de lixo”

1 Responder

O primeiro traballo fóra da facultade en 1991, Tiven a sorte de traballar para unha empresa de manufactura con 13 locais, 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.

O proxecto rula ao longo e estou enviado a Baltimore cun novo compañeiro de traballo, Jeff. Our job was to power up the Unix box, comproba se o A / S estaba funcionando, instalar o sistema ERP, configurar ERP, train people on the ERP and do custom work for folks on the spot. (Este foi un traballo de soño, sobre todo vindo en liña recta fóra da facultade). Before we could really get off the ground, que necesitabamos para descomprimir todos os tubos verdes, put them on desks and wire them. And the best part was that we had to put the RJ11 connectors on ourselves.

Por algunha razón que eu nunca entendín e realmente nunca pensei en preguntar sobre o tempo, Nós tiñamos tido algúns empresa contratante vir e executar cabo en toda a planta, but we didn’t have them put on the connectors. Así, there was a "patch box" with dozens of of unlabeled cables in the "computer room" e estes serpenteava en torno do edificio para varios lugares do edificio.

Traballamos o noso camiño a través del, ao longo dun fin de semana, probar cada fío, poñer un conector (asegurarse de que era recta vs. cruzado), garantindo a configuración de bits nos tubos verdes e impresoras estaban correctos, 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.

Pero, 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, pero a impresora se converteu nun pesadelo de tres semanas.

Se non sabe, ou que suprimiu, xestionar tubos verdes e impresoras deste xeito, there are various options that you deal with by setting various pins. 8-bocado, 7-bocado, paridade (par / impar / ningún), probably others. If you get one of those settings wrong, o tubo ou a impresora aínda mostra cousas, pero será xerga total, or it will be gibberish with a lot of recognizable stuff in between. Por suposto, these pins are hard to see and have to be set by using a small flat-edge screw driver. And they are never standard.

Montar a primeira de moitas chamadas rápidas co NJ cara (un inimigo ordenador grisalho que probablemente nos maldí até hoxe). 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, nunca está seguro de se estaba facendo isto correctamente.

É hora de ir en directo, todo en Baltimore está cantarolando, pero non podemos comezar a impresora maldito en NJ para traballar! 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", coa esperanza de que quizais haxa algún indicio de que o lixo que vai nos dicir o que estamos facendo de malo.

Cando chegamos o fax, we immediately knew what was wrong. Ver, our method of testing whether we had configured a printer correctly was to issue an "lp" comando coma este:

lp / etc / passwd

Basicamente, 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:

ferreiro:*:100:100:8A-74(oficina):/home / smith:/usr / bin / sh
:*:200:0::/home / invitado:/usr/bin/sh

We had been printing out the password file over and over again for several weeks and it was printing correctly. Con todo, para o usuario final, it was "printing garbage".

</final>

Yet Another Rede emitir credenciais multi-Challenge e Resolución

Deixe unha resposta

O meu cliente instalouse recentemente un dispositivo máxico de Zimbro que aparentemente substituíu o antigo Cisco balance de carga de rede (NLB). At about the same time, instalouse un hotfix para resolver un problema de fluxo de traballo.

Un ou dous días despois, notamos un problema cando acessamos os provedores de servizos compartidos (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, Non sabemos cal dos dous (Juniper ou hotfix) sería o tema, aínda que sospeito fortemente o hotfix, descubrir que non tiña instalado seguro.

It turned out that Juniper had some kind of compression setting. Un dos figuras de túnica 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 navegadores (IE 7 exploradores traballaron sen dificultade).

Así, add "compression" á lista de perigos.

</final>

Crédito para: http://www.elfwood.com/art/s/h/sherry/death_colour.jpg.html

Pensando en cambiar de plataforma Blogging

7 respostas

Comecei a miña carreira blogging "" using Microsoft’s platform and it’s been good to me. It’s easy to post, hai boas opcións e widgets para xestionar o seu "espazo", almacenamento web decente e así por diante.

Con todo, 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.

Primeiro, 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 (ou, sobre todo, non poden atopar) when they search my blog. It’s very hard to use lives spaces for that.

Segundo, there does not seem to be any mechanism to "monetize" a windows live space blog. En realidade, a fin de se librar dos anuncios MS (desde o que eu sacar ningún beneficio), I need to actually pay Microsoft. (Polo menos, é así que eu entendo; Eu fun incapaz de obter respostas definitivas para esta e preguntas gusto).

Agora que eu teño un patrón establecido e un conxunto de blogs hábitos, I want to evaluate other options. I’ve done some research and there are a lot of choices, pero estou curioso para saber o que as outras persoas, particularmente outros na comunidade SharePoint (como bloggers ou lectores), like to use.

Si este tema lle interesa e ten unha opinión ou están dispostos a compartir a súa experiencia, por favor, deixe un comentario ou enviar un correo directamente.

Grazas!

</ Comezo>

Technorati Tags:

SharePoint Deseño Email Envía ???? en un correo-e

1 Responder

Os usuarios do foro, en ocasións, pedir: Por que poñer o SharePoint Design ???? no meu correo electrónico en lugar dun valor de campo?

Unha razón isto acontece é porque a variable á que se refire é nulo.

Isto pode ocorrer porque estás a facer referencia a un campo do elemento "actual" but the user never entered a value into that form field.

</ Comezo>

Comparar / Proba para as datas en branco ao SharePoint Workflow Design

5 respostas

Escenario: En un fluxo de traballo do SharePoint Design, you need to determine if a date field is blank.

Problema: SPD does not provide a direct method for comparing dates to anything other than a date. You cannot create a condition like this: "Se [DateField] é igual en branco ".

Solución: 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. Neste escenario, a field on an item, "Environmental Permits:First Permit Reminder Date", is submitted and the workflow fires in response.

imaxe

imaxe

Notas:

When I tried this, I was pleasantly surprised to learn that it works. I was worried that SharePoint Designer might disallow the string assignment (Variable:StringReminderDateDate) but it did allow it.

I was also concerned that allowing it, the value might be null and either blow up the WF at runtime or maybe raise the global temperature 1/2 a degree, but those concerns were unfounded.

</final>