Home > Forum > Processes > Dictionary Process allowing Documentation

Dictionary Process allowing Documentation
0

Hello all,

Not sure if you might know the answer but it's possible that Dictionary processes do not allow to have attachments?
In the form configuration, the attachment's preview is there but the field attachments is not visible. I need to create a directory so a dictionary would be create but some of the lines might have attachments.

Thank you!

MVP
In reply to: Pawel Jawien (WEBCON)

Hi Andrea

Look at the article:
https://community.webcon.com/posts/post/dictionary-processes/112 .
The dictionary process prevents you from adding attachments to workflow instances.

You can user a "standard" process as a dictionary (with no limitation).

Best Regards
Pawel Jawien

Is there any way to use import/export functionality with 'standard' process used as 'dictionary'?
It might be an important drawback if there is no way - at least i dont remember any.

MVP
In reply to: Maksymilian Stachowiak

Is there any way to use import/export functionality with 'standard' process used as 'dictionary'?
It might be an important drawback if there is no way - at least i dont remember any.

Hi,

export/import is only available for processes of type "Dictionary" and "Document template" . The later one may be an option for this situation. Just because it's named "Document template" doesn't mean, that it has to be a template used in combination with Word or so.

There's one alternative for standard workflows if you really need it:
https://github.com/WEBCON-BPS/RestApi-DataImporter

I haven't used it though.

Best regards,
Daniel

Privacy overview

This website uses cookies so that we can provide you with the best user experience possible. Cookie information is stored in your browser and performs functions such as recognizing you when you return to our website and helping our team to understand which sections of the website you find most interesting and useful.


To see a full list of the cookies we use and learn more about their purposes, visit our Privacy Policy.