The question is unfortunately not clear. What do you mean by 'template'?
Processes in EDQ are run on data, where data is captured into EDQ using a variety of different ways, but normally from an EDQ data store. If you have data existing on your client that you cannot easily upload to the server for processing, create a client-side data store and run a snapshot to capture the data. You can then run a process that reads from this snapshot. If the file remains connected only via the client then you cannot run scheduled jobs to capture the data repeatedly as the client may be disconnected.
So the source of the data is an xls file. So i created an EDQ data store, pointing to that file. I also created a new snapshot, thus have staged the data in EDQ. I then exported, and saved the output in a temp file, on my client. This is what i was referring to as a template. I also have created, simple/test business rules under processes, and i want to be able to run a job to capture the data repeatedly, with the results passing, until my template is viable to be exported. Does this make sense?
It makes sense but your snapshot and export are both to client-side data stores, meaning they cannot be configured as part of a job. Jobs need to run entirely on the server so cannot use client connections.
If you want to automate this type of process you will need to upload your Excel spreadsheet to the server (e.g. using the SFTP interface) and use server-side data stores.