So, I came up with my own solution. I'm sure it is not a novel solution for this sort of thing, but it is similar to a strategy I've used before.
You see, I like to stay within the LF toolbox whenever possible. Integration with SQL is great, but also involves a DBA and adding to a DB. Down the road when you make changes to the environment it is something you will need to remember and check the documentation for.
So, if it isn't too hard and functions, I do it within LF.
Solution:
- Initial form filled out in Forms.
- Use a workflow service task to call the workflow
- Worfklow reads the current count from a field in a specific document protected from access by all other accounts.
- Increment the number, format the token as needed, set the BP variable to pass back to Forms.
- Write the incremented value back to the field value.
- Workflow ends
- Forms continues with new value.
This way, no DB or stored procedures.
This technique has many uses - creating variables, templates of documents, address lists, etc. - in the repository to be used by WF as needed. Users can be given access to these as needed and can keep you from having to edit hard-coded workflows.
Another solution for the future admins out there. May it help someone out someday.