WELCOME TO THE COMMUNITY
find what you are looking for or ask a new question

search results

for path

(...) ng an issue with selection attributes. If a user types a value but doesn’t explicitly confirm the selection, the value still appears in the field after saving the form or moving along the workflow path . However, the problem is that the value change rules are not triggered in this case, which often results in the form not being populated correctly. Has anyone encountered this behavior or found a (...)

(...) as the original language within the business rule that sets me the field along the way. I use this technical field within our dashboards but it always defaults to English no matter what I do,. The path gets triggered by a subworkflow. If I the author myself go on the path the translation is ok but if I manage it through the sub-worflow from a superior for example.. it defaults to the English tex (...)

(...) I have a Step with a "cancel" path . On this path I have enabled "comment required" => User always should enter a comment if he is cancelling the workflows. Now I have a "housekeeping" timer in that step. The timer exections an action (Change field value => [System]Comment) and has path transistion after action execution "cancel" => Timer throws an error: field validation "Comment" on path "can (...)

(...) hat doesn’t When using “Add an attachment to a list”, the file upload fails with: 401 Unauthorized 🔍 Logs / details From WEBCON: Execute WCFCsomService .../AddAttachmentToSPList Error in On path action Add attachments to Extranet (Step: Signing → Prepare for mailing) The remote server returned an error: (401) Unauthorized. Stack trace: System.Net.WebException: (401) Unauthorized at Mic (...)

(...) are not global or static. They are often assigned individually to each workflow element based on: - the author of the element, - process participants, - actions executed during the process, - the path the element followed, - business-specific permission logic. This means that every element can have a different permission set depending on how it was processed. For some organizations, grantin (...)