This past week I finished off a proof of concept project for a client in Manhattan. While implementing the solution, Corrín a outra lagoa do Moss KPIs (Vexa aquí unha cuestión KPI anterior ea miña solución).
Fondo: We used SharePoint Designer workflow to model a fairly complex multi-month long business process. As it chugged along, it would update some state information in a list. KPIs use this data to do their mojo.
We decided to create a new site each time a new one of these business processes kicks off. Aside from the workflow itself, nestes sitios acollida varias bibliotecas de documentos, use audience targeting and so forth. Just a bunch of stuff to help with collaboration among the internal employees, viaxando funcionarios e socios de empresas que participan do cliente.
Tamén queriamos amosar algúns KPIs que monitorizar a saúde xeral do que o proceso de negocio específico, como a promovida polos datos do estado de fluxo de traballo e visto usando os KPIs.
Finalmente, usan os elementos da lista de KPIs que fan unha conta nunha visión nunha lista na web (en oposición a tirar dende outra fonte de datos, como o Excel ou SQL).
O Problema: Como podes imaxinar, supoñendo que fose para levar a idea básica para adiante nun mundo de produción, we would want a site template. Provision a new site based off a "business process" modelo.
The problem is that you can’t seem to get a functioning KPI that way. When I create a new site based on a template with a KPI List and KPI web part, the new site’s KPI data are broken. The new site’s KPI list points at whatever source you defined when you first saved it as a template.
By way of example:
- Create a new site and build it to perfection. This site includes the KPI data.
- Save that as a template.
- Create a new site and base if off the template.
- This new site’s KPI list items’ sources point to the site template, not the current site.
The instantiation process does not correct the URL.
I tried to solve this by specifying a relative URL when defining the KPI list item. Con todo, I couldn’t get any variation of that to work.
I always want to pair up these "problem" blog posts with some kind of solution, but in this case I don’t have a good one. The best I can figure is that you need to go in to the newly provisioned site and fix everything manually. The UI makes this even harder because changing the URL of the source list causes a refresh, entón realmente ten que redefinir a cousa toda de cero.
Se alguén sabe un xeito mellor de tratar con isto, por favor publicar un comentario.
</final>