WELCOME TO THE COMMUNITY
find what you are looking for or ask a new question
Home > Forum > Latest posts

latest posts

Business case: due to organization regulation it is required to fill in a specific form and attach it as PDF to a WEBCON case. The problem is how to assure that such PDF file matches prefedined format and that is is filled with reasonable contect
Expectation: dedicated action that will take two attachments: template in PDF or WORD and actual document in PDF or WORD and will calculate similarity score from 0 - documents differ completely to 1.00 - documents match perfectly. Alternatively TRUE (document matches template and has reasonable content) or FALSE (document doesn't match)
I look for WEBCON integrated solution
Any ideas?

MVP

We did something similar few years ago. The user had to be able to choose and also sort documents, we then merged to one pdf.

It was the time when I introduced the first version of the modal dialogues, which Daniel Krüger improved a lot.
Have a look at https://daniels-notes.de/posts/2022/modal-dialog.

We used a menu action that opened the form in a dialogue. The form has an itemlist, which we initialize with the attachments of the calling element. And some more to name and categorize the merged pdf. The workflow only has a path to merge the selected pdf's and add the merged document to the attachments.

You could do something similar to send selected attachments in an email.

I’m missing the option to select multiple attachments (for example, to sign them or send them via email).
I'm not referring to using any naming pattern or attachment group, but rather giving the user full flexibility to manually select the desired attachments.
Has anyone found a way to achieve this? Perhaps it would be possible to use a Item List that would dynamically display all attachments and allow them to be selected?

MVP
In reply to: Daniel Krüger (Cosmo Consult)

Hi,

this is really an interesting behavior.

While it is possible the below case is possible , this is not possible for the current workflow instance.
- Checkout workflow instance 1 / open in edit mode
- Execute REST action from workflow 2 to delegate a task of workflow 1
- Edit and save workflow 1
- Changes and delegated task is shown after saving workflow 1

I have to admit that I didn't come up with delegating task via the API. This is a lot easier than creating a path on each step to update the tasks. At least if the original task owner should still be assigned.. If this shouldn't be the case, then there's no way around than using paths.

While this is an interesting finding it doesn't help much.

If you want to stick to the delegation option, then I see only one reliable solution. Start a "technical delegation workflow", populate and item list with all the workflow instances which should be updated:
- Instance id
- Assigned to user
- Delegate to user
Add a timer to the step in which the workflow has been saved and this will then execute the delegation with a short delay. This would allow that the button execution is finished before the delegation has been executed. Even if the delegation would fail, the users could continue to work and you could create a task/mail to look at this technical workflow.

The only other alternative would be a path. If you don't want to show it as a path but as a button. You could hide the path with a form rule and add a hyperlink action to the button with:
javascript:MoveToNextStep({PH:355})


Best regards,
Daniel

I just came back here to say, that this javascript:MoveToNextStep({PH:355}) in hyperlink action is genius, never thought about that one, don't have a use case, but whoa!

MVP
In reply to: Marcin Borowiec

bump, anyone got any idea on how to fix it?

Hi,

this is really an interesting behavior.

While it is possible the below case is possible , this is not possible for the current workflow instance.
- Checkout workflow instance 1 / open in edit mode
- Execute REST action from workflow 2 to delegate a task of workflow 1
- Edit and save workflow 1
- Changes and delegated task is shown after saving workflow 1

I have to admit that I didn't come up with delegating task via the API. This is a lot easier than creating a path on each step to update the tasks. At least if the original task owner should still be assigned.. If this shouldn't be the case, then there's no way around than using paths.

While this is an interesting finding it doesn't help much.

If you want to stick to the delegation option, then I see only one reliable solution. Start a "technical delegation workflow", populate and item list with all the workflow instances which should be updated:
- Instance id
- Assigned to user
- Delegate to user
Add a timer to the step in which the workflow has been saved and this will then execute the delegation with a short delay. This would allow that the button execution is finished before the delegation has been executed. Even if the delegation would fail, the users could continue to work and you could create a task/mail to look at this technical workflow.

The only other alternative would be a path. If you don't want to show it as a path but as a button. You could hide the path with a form rule and add a hyperlink action to the button with:
javascript:MoveToNextStep({PH:355})


Best regards,
Daniel

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