I have a workflow for a client that uses metadata for a document to progress through a series of approvals and processes.
At one step, a report needs to be generated to allow an employee to import data into another system. To do this, we are using an ODBC connection to a XLS.
When the process gets to the part of filling out the XLS file and bringing it into Laserfiche, it follows these basic steps:
- Prep tokens with the information needed to be filled in.
- Create Entry - Document to receive the XLS when finished.
- Script activity to copy a blank XLS to the location of the ODBC XLS
- Insert Data into XLS
- Attach document from server to created entry
We are noticing that step 3 is sometimes occurring on 1 workflow, while another workflow is between steps 4 and 5. What this causes is a blank XLS file to be brought into the Laserfiche repository.
I want to figure out a way to handle this sequence of activities that will enforce a rule of only 1 workflow instance to be in that stage at a time, and if their are multiple waiting to be in that stage, then to handle how they will determine the order in which they will perform these activities without overlapping each other.