Is it possible to create a workflow that terminates if an index value of the document changes after the worflow has started? For example, I have a Resume Review workflow that send a resume to the hiring manger for review and approval. Is there a way to automatically terminate that workflow instance if the hiring manager changes, i.e. GV_HIRING_MANAGER <> DW_HIRING_MANAGER?
Thanks for any guidance.
Is it better practice to have one workflow with many steps and users, or is it better to have multiple workflows that encapsulate each of the steps of the larger workflow and essentially pass the document from one workflow to the next? Here's my particular situation: I've got an HR Hiring Process that passes resumes from the HR Department to a Hiring Manager and then to one or more Supervisors until a decision is made, and then back to the HR Department. This is all in one big workflow, and consequently each invidual workflow instance lasts for weeks as hiring decisions are not made quickly here.The problem is that I made a mistake in part of the workflow and, in certain circumstances, I have to manually intervene and reassign tasks. I've fixed the issue so new workflow instances don't have the problem, but I've got 270+ resumes running on the old version of the workflow that I'm going to have to monitor now for weeks.
I'm thinking that the next time I do something like this, I should break each step into it's own workflow. So if I have to fix or change something, Other documents at other stages in other workflows won't be affected, and they will just flow into the new version.
Anyone have any thoughts on this?
Thanks for the advice.
I've created two Document Relationships - one for use by HR and one for everyone else. I've linked these to specfic result and list dialogues. My problem is that I can't seem to restrict task lists in the same way. Consequently from a task list, both document relationships are selectable. Is there any way to fix this?
Thanks for any suggestions.
Thank you all for your help!
I tested it out, and it works. I've attached the diagram of my workflow. The one odd thing I had to do was to assign the timeout task to someone and then redirect the workflow back to the decision maker if the auto-exit condition wasn't met. Perhaps, there's a better way, but this does the trick.
I'd like to vote for that feature too.
Is it possible to end a workflow when an autoindex workflow changes a document's field?
For example, I've got a Resume Processing worflow that sends resmumes to hiring mangers for review. What I'd like to know, is if there is a way to end the Resume Processing workflow instance for resumes still under consideration once another person has been selected for the position?
To be even more specific, resumes have a position request ID field and a position request status field. I have an autoindex worflow that will update the position request status to "Filled" for all resumes with the same position request ID field once someone has been hired. Is there a way to end the Resume Processing workflow for all currently active resumes when the position request status changes to "Filled"?