(...) Hello, we are using the API to create workflow instance s by another system. We are also checking if this workflow has already been created. Now to the problem: Unfortunately we are not able to access the archived instances with api-call and check for existing workflows: api/data/v5.0/db/{{dbid}}/applications/{{applicationid}}/search?search=xxxx:xxxx if the workflow instance is not yet archived we are abl (...)
(...) needs access rigts for the app/process it need access, and that's clear. But, api actions are also performed by that user, and this name is visible (for example - if we start the workflow over API, workflow instance is started by "something - Registered App"). So, how can I change the user name from ""something - Registered App" to anyfing else, like just "something" ? I don't want my users to see "something - (...)
I am trying (without any success) to read data (ie. employee id) from an existing text-based PDF (test pdf created via MS Word). The documentation is explaining the different actions (ie. wait for ocr ai, wait for text-layer), but not how they actually work together or how to use them. Maybe I am completly wrong in trying to use "OCR AI recognition", "Wait for OCR AI" etc..... My goal is:
Hi everyone, We have a workflow, where a lot of attachments are being passed around departments, in this case it's over 10 files, but there are some outliers with even 30. With this workflow we've also implemented a 'copy form' functionality, which creates new instance with filled in data and copied attachments. The thing is, sometimes in the copy of the document we only need 20 from those 30
(...) Hello community, I need to start a workflow instance for each email address in a text, where the addresses are separated by semicolons. My plan was to initialize the Item List using an SQL query, and then to start a subworkflow (SQL) instance for each row (email). Since our WEBCON environment doesn't support STRING_SPLIT, I fabricated a custom SQL query to split the long string into individual rows with email a (...)