ნაადრევი სამუშაოს გააქტიურება — არასამთავრობო სამედიცინო გადაჭრა

8 პასუხი

განახლების: აგრეთვე ამ MSDN დისკუსია, განსაკუთრებით ბოლო ჩანაწერში: http://forums.microsoft.com/MSDN/showpost.aspx?postid=2631057&siteid=1. It describes a condition that may short circuit this whole thing. In short, ეს შეიძლება იყოს ძალიან მარტივი მიღების მინიმუმ ერთი სფეროებში სავალდებულო.

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

I have a SharePoint Designer workflow that wants to calculate and assign a "reminder date" უბრალოდ subtracting 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 და უფრო არსებითი საბურღი-down აქ).

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. ასე რომ, … ჩემი workflow უკვე გაათავისუფლეს და როდესაც ის შესრულებული, 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 thoughts on "ნაადრევი სამუშაოს გააქტიურება — არასამთავრობო სამედიცინო გადაჭრა”

  2. Saurabh Singh
    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  KB 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" -url http://localhost
    მაგრამ აღმოაჩინა იგივე პრობლემა.
    რა უნდა გავაკეთოთ, ამ?
    Please suggest me why "Pause Until Date" doesn’t resume and Workflow status does not change from "In Progress" ჩემს workflow.
    If anyone have any solution regarding this then please reply me at saurabhsinghmca@gmail.com
    დიდი მადლობა,
    Saurabh Kumar Singh
    პასუხი ↓
  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. კორი
    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. პოლ Galvin
    ჯო,
    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.
    Thanks for sharing,
    –პოლ 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.
    პასუხი ↓

დატოვე პასუხი

თქვენი ელ-ფოსტა არ გამოქვეყნდება. აუცილებელი ველები მონიშნულია *