Home > Forum > Processes > Starting Multiple Workflow Instances from an Excel File

Starting Multiple Workflow Instances from an Excel File
0

Hi,

If a user has an XLSX file with 100 rows, where each row represents a new item, is it possible to allow them to start new instances of a given process based on that file?

In this case, the goal would be to automatically create 100 new workflows.

MVP
In reply to: Bjoern Poller

Hi Piotr,

let's first solve your IMPORT-problem. I attached a screenshot with an example of loading an excel-file into an itemlist.
I hope i did understand your problem right.

Bye,
Bjoern

FOR YOUR INFO: This example is a different one to PIC 1 !!!!
----------------------------------------------------
Hi Piotr,

after successfully importing the EXCEL-File, I myself always use a path to an end-step.

There I add an Action "on Entry":
-Tab BASIC: Selecting the new workflow process with its path (like in the PIC 2)
-Tab DATA: Here i use a SELECT to put the item list value from one row into a single target sub-workflow
-> For all itemlist rows: SELECT {itemlist column 1 of actual row} AS {target form field of new instance in the sub-workflow}..... (see PIC 2)

I hope, this helps,
bye,
Bjoern

In reply to: Maksymilian Stachowiak

I'd need some more context to answer if it's possible in your use case :)
What are current list items?
What columns do they store?
Should it happen on the form?
On path transition?
What data should be moved from one to another? Maybe some examples?

I have one application in which I want to enable launching multiple workflows using an XML file.
I have one list of items called 'Importer'
And another list of items, let's call it 'Target'.

In 'Importer' I have a field 'Gross' as a floating-point number, and the same in the 'Target' list.

In the starting step, I created a new path that registers bulk orders (start subprocesses (SQL)).

Configuration in the attachment.

There will be more fields, but for now I'm trying to do only this one field.

MVP
In reply to: Piotr

I understand the ideas, but I can't find the error.
'DB' means database field name

Subworkflows start, but fields do not complete, they are empty

Thanks for this: 'DB' means database field name -> different name cause of different language CHECK
-------
Hi Piotr,

I’m sorry – everything looks good.

One last idea/question: your TARGET isn’t an itemlist form field, is it?

In my example, I’m using the itemlist to start the sub-workflow, copying the itemlist values into “normal” form fields for each row (each row -> new sub-workflow instance).

Bye,
Bjoern

Did you know that with WEBCON you can automate virtually any process? Even baking cookies 🍪
 
Speaking of cookies: we use the ones that are essential for our website to function properly, as well as additional ones that help us customize our content to your preferences. If you don’t mind cookies, click Accept. If you want to learn more, explore settings.
Settings