Currently a Service can process files one by one. Therefore, I want to the services be able to execute a file batch process. To do that the files needs to be grouped in two possible ways:
Zip file: Once received into the service inbox, the service will upZip it aproceed to process every single file
Work Order: This one will be a Json structure in a text/json file. is a serialized class that contains work / job info like user name, date issued, status, error list (collection) and file list (collection of files in serialised base64 format).
At the end of the service process, the service must be able to upadte the work order status filed and the error list collection if needed.
Recodemos un hecho ineresante: los servicios aceptan parametros de entrada al iniciarse, y uno de llos es la lista de archivos a monitorizar en el directorio Inbox. Se puede crear una instancia del servicio especial solo pra procear archivos "Work Order" (con extension json?).
The aferementioned "work order" must be produced by the WorkFlow API. The problem is the API is still getting build on the garage!
Currently a Service can process files one by one. Therefore, I want to the services be able to execute a file batch process. To do that the files needs to be grouped in two possible ways:
At the end of the service process, the service must be able to upadte the work order status filed and the error list collection if needed.
Recodemos un hecho ineresante: los servicios aceptan parametros de entrada al iniciarse, y uno de llos es la lista de archivos a monitorizar en el directorio Inbox. Se puede crear una instancia del servicio especial solo pra procear archivos "Work Order" (con extension json?).
The aferementioned "work order" must be produced by the WorkFlow API. The problem is the API is still getting build on the garage!