Предвремено Работното Активирање — А не-медицински решение

8 одговори

Ажурирање: Погледнете го овој MSDN дискусија, особено последниот запис: http://forums.microsoft.com/MSDN/showpost.aspx?postid=2631057&siteid=1. It describes a condition that may short circuit this whole thing. На кратко, тоа може да биде едноставно како правење на најмалку една од областите задолжителни.

Јас имам еден документ библиотека која поддржува осум типови содржини.

I have a SharePoint Designer workflow that wants to calculate and assign a "reminder date" со едноставно одземање 30 дена од друга колумна, "due date". This should only happen for one of the content types, "Insurance". The business objective is to produce a KPI that shows two categories of insurance documents: "about to expire" and "expired." (Можете да прочитате повеќе за овој вид на KPI и посуштински вежба-долу тука).

I have configured the workflow to fire when a new item is created and when an item is modified. The idea is that when an insurance document is uploaded, we calculate a "warning date" based on the expiration date. A pair of views work in connection with a KPI List to highlight these conditions when users hit their home page.

Оваа стратегија не работи кога јас испратите документот.

I upload the document and I am presented with the meta data entry screen. Во овој момент, I’m already in trouble. SharePoint has already, предвреме од моја перспектива, fired the workflow. I haven’t had a chance to pick the correct content type nor assign a due date. Во исто време, the workflow does not fire when I hit the submit button at this time. There’s some built-in logic that "believes" that first submit is part of the "create" event. Така … мојата работа е отпуштен и кога станува погубен, it was passed default meta data values.

The best work-around I know of is to insert a "pause until" activity in the workflow. I have the workflow pause for 1 minute. While it’s pausing, Јас го изберете точниот тип на содржина, enter the meta data and submit. The pause completes and the workflow proceeds as needed. (Имајте на ум дека во мојата средина, timer workflow activities from SPD do not work out of the box. You may have the same trouble. Види тука за повеќе детали).

I don’t like "magic delay" work-around. What happens if the user uploads a document and the phone rings and the ensuing conversation outlasts the pause? I can make the pause longer, но јас сè уште не ми се допаѓа.

Напишав за тоа на MSDN форуми тука: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=2430725&SiteID=1

8 размислувања за "Предвремено Работното Активирање — А не-медицински решение”

  2. Saurabh Синг
    Hi,
    I am creating a reminder wrokflow using SharePoint Designer, and when i using "Pause Until Date" активност. It doesn’t resume and Workflow status does not change from "In Progress".
    (i.e it displays "Pausing for 0 минути" under Workflow History but it doesn’t take specified action).
    I have created it many times but found same problem.
    I have done some googling for that in last some days, and from there I had got a hot fix  КБ 932394 and installed it but still I am in same trouble with Пауза До Датум Activity.
    I have also changed job-workflow time duration using stsadm command from 5 минути за да се 1 минута како подолу:
    stsadm -o setproperty -propertyname "job-workflow" -propertyvalue "every 1 минути помеѓу 0 и 59" -рачно http://localhost
    но не најде истиот проблем.
    Што треба да направам за оваа?
    Please suggest me why "Pause Until Date" doesn’t resume and Workflow status does not change from "In Progress" во мојот работното.
    If anyone have any solution regarding this then please reply me at saurabhsinghmca@gmail.com
    Ви благодариме,
    Saurabh Кумар Синг
    Одговори ↓
  4. rich wrote:
    I saw a post to a similar issue that said you need to make the fields required and that it will then stop the workflow from firing until the required fields are filled in. I have not tested it just documenting here what I read elsewhere.
    Одговори ↓
  5. Corey
    We had this same issue and what we wound up doing was to create an "Unclassified" content type which was the default. As long as your workflows ignore the "Unclassified" типот на содржина (and you’re not firing on create) you’re good to go.
    Одговори ↓
  7. Пол Галвин
    Joe,
    I’m glad to know I’m not the only one. This is another case where SharePoint brings you soooo close to a solution but leaves you short and no really good option to finish the crossing line.
    I went down the same path you describe but didn’t finish it entirely. I expect I will end up doing exactly that in the end.
    Ви благодариме за споделување,
    –Пол G
    Одговори ↓
  8. Joe wrote:
    I found this problem also – not just with a date oriented workflow, but any workflow on a doc library where users will upload documents.
    If the workflow depends on any metadata, you can’t have it fire automatically because the upload fires the workflow before the metatdata is filled in. This is a flaw in SharePoint in my opinion.
    As for "reminder" dates, instead of using workflow, I ended up writing a timer job that scans the list every day and sends out e-mail reminders based on a date field.
    I tried having users manually start the workflow after the metadata was entered, but I still had a problem using workflow for the reminders because it would pause the workflow until the reminder date, but if the user later edited the document data and changed the date, the old reminder workflow was still out there.
    Одговори ↓

Остави Одговори

Вашата е-маил адреса нема да бидат објавени. Задолжителни полиња се означени *