I know there are two types of starting rules, Scheduled and Conditional. With a conditional you can set starting rule conditions so an entry must have a specific path. What if you want to use a Scheduled rule? In the scheduled rule you are not able to specify a specific path the document has to be in. Do you just need to do that in the workflow itself?
Question
Question
Scheduled Starting Rule Question
Replies
Hi Blake,
Yes, you would need to establish that within the workflow itself. Because the schedule rule is not triggered by any particular document, you can't check the path because there isn't anything to check. Because you don't have a starting entry, you're usually using scheduled rules for things like processing a day's reports that are all always stored in the same folder to use as your starting entry, or emailing a bunch of people at a certain time, a situation where you might not need a starting entry at all.
It would be very beneficial for situations such as this to be able to specify conditions with a scheduled starting rule.
I'm not sure I know what you mean.
For your example above would that be running the workflow once a day, but only if the \_Employee Not Found folder is not empty?
No, it would be nice to have a condition in the scheduled starting rule to say run only if these conditions are satisfied, just like a conditional starting rule. It would be a hybrid of the two.
The hybrid starting rule like that wouldn't actually give you any additional utility, because the conditional starting rule conditions wouldn't apply, and if you're just checking a normal condition you might as well just enter the workflow on the schedule and check using a conditional decision whether to actually proceed with or end the workflow.
If you really wanted to use a hybrid situation, you could use a condition starting rule and have the first event be a delay activity to delay until a certain time. That way the workflow would be triggered like a conditional, but you could control when you'd want it to actually run.
I am having the same issue. Bringing in folders (video dvd's) from different agencies and they all go into a different folder in LF. It does a lookup to a SQL db and if it finds an existing case will process the DVD. If not... it needs to recheck it the next morning, but I am dealing with more than one folder in which a DVD can sit until a db entry is found. Have not found a solution. Will keep looking.
Ingeborg,
It sounds like you have a workflow that runs when the documents are created and does the lookup? You could add a scheduled workflow that looks for documents created before today and then calls the original workflow on each one of them. (You'd want to refine the search a bit so it only gets the documents that don't have the field set)
Problem is it is folders and not files I need to look for and they are subfolders in possibly 17 other folders. But... the date stamp might be something I can use in my search for a solution. Thanks for the hint and I will go and see if I can make that work somehow.
So we have two folders that we use for an HR workflow. It is supposed to take the metadata from the documents and file the documents in the employee's folder. We perform a lookup in the HR software for the employee's SSN to fill in the additional metadata and create the employee's folder structure.
We currently have a Conditional starting rule so that if a file is put into the \_Process Employee Files folder it will kick off the workflow. If the employee is not found in the HR software yet, we put the documents in the \_Employee Not Found folder. We would like to keep this workflow, but would like to run the same workflow on the \_Employee Not Found folder on a schedule. What would the best way to do that be?
You could create a workflow that runs on a schedule, and have it do a search in that folder. Take the results and For...Each over them, feeding each one as a starting entry into your other workflow via the Invoke Workflow activity.
Late post, but you can check to see if there's a starting entry using the Token>Global>Has Starting Entry. If it has a starting entry, go down one path, otherwise go down a second path that gets the entries in the specified folder and processes those entries.
That's the only way I've ever been able to do it. It's normally a scheduled workflow with the first activity being a Search targeted at the directory I'm interested in.
Hi All,
I have a similar problem, but Repositories. I have two repositories and two similar Workflows with two schedule rules (one on each workflow). Each Workflow is supposed to run only on each repository. However, both Workflows are running on both repositories (returning an error on the other repository). There is no schedule condition to specify where we want that rule to run.
Is there any way to specify which Repository to run that schedule rule on?
Thanks,
Hi Minura,
Thanks for your message.
I think the error messages are related to the fact that the Workflow is supposed to run on a specific repository, and it does not have rights to access the other one. This error/warning does not occur on the repository where it is supposed to run
The workflow was started from repository 'LFSYDHI'. There are no workflow connection profiles that use this repository. [0471-WF10] |
Is there any way to specify a Workflow to run just on a specific repository?
Regards,