So, when I create a new vendor with the Vendor Approval workflow enabled, when I save the new vendor it gives the vendor a 'Not Submitted' status until I submit it through Workflow, then it is assigned to my approver(s) for the first and only step I have in that workflow, as per your screenshot above.
If I pull up a existing vendor that existed before I activated the Vendor Approval workflow, it has a status of 'Workflow Not Activated'.
If I make a change to this pre-existing vendor and save changes, then when I pull it up again, it has the status of 'Not Submitted'. Submitting this pre-existing vendor through approval, it's still routed to the approver(s) of my one and only workflow step, no different than the new vendor.
Based on your screenshots, since you have the one and only workflow step set to 'Action is always required for this step', each time you submit a vendor through workflow, whether pre-existing or new, it should be routing to the approver(s) you have listed in this step.
I also see you have a 1 hour time limit, so after an hour, since you also have the 'always require at least one approver', it will then look for an alternate final approver, which you have specified, and route the vendor workflow to that person(s) for approval. If you didn't have an alternate final approver specified, it would route it to the workflow manager(s) of the Vendor Approval workflow.
Although, you also have the 'Escalate to' option marked under 'When a task is overdue', so I'm thinking that after an hour, if the approver(s) of the 'Approval' workflow step haven't taken action on the workflow yet, it'll first try to route to the person(s) you have specified there, then if it can't route to those person(s), it'll then route to the specified alternate final approver and then workflow manager, as mentioned above.
If, for whatever reason, the application can't verify the AD account specified as the approver of a Workflow step, it may then start moving through the next level approvers which would be the alternate final approver and then workflow manager.
This all being said, it wouldn't make any difference if I'm submitting a brand, new vendor through workflow for approval or it is an existing vendor that I made changes to, saved the changes and then submitted for approval. There's no functionality in Workflow to differentiate between a new and pre-existing workflow, it only goes by the workflow status assigned to the object.
If you're seeing differently, we may need to have a support case opened with us so we can look at it with you and determine why it's routing incorrectly.
Thanks
