search results

(...) Hi, it would be great to have the possibility to comment directly to comment s. This would help to focus on the different contexts in the comment s section. On top a like button would be nice with a function that returns the sum of all comment s. Kind Regards Sébastien Anselment

(...) Description of change: In the low-code system in the comment s field, the System Administrator should be able to delete a comment added by a user. First option: The deleted comment will not be visible to normal users. (as if it had never been added) OR Second option: The deleted comment will be replaced by the default type text: {username} delete added comment (something like deleting a mess (...)

(...) Hello, I have a process, in which the "pathId" transition paths require adding comment . However, in SDK I am unable to find a way to move the document along this path due to missing comment . private async Task CancelInstance(DocumentsManager manager, int documentId, int pathId) { ___var document = await manager.GetDocumentByIdAsync(documentId); ___await document.comment .Addcomment Async("Adding com (...)

(...) The system looks inconsistent — we can easily change colors for group headers and tab panels, but not for the comment s and attachments sections. These sections look similar to tab panels, so it would make sense to allow color changes there too.

(...) hi, It would be useful to know at what stage the comment was added. The name of the step could appear next to the user name and date in the comment header. Regards.

(...) It would be great to have the possibility to move the Attachments and comment s sections inside a tab. This would make the forms much cleaner and better organized, especially in more complex workflows.

(...) Hi everyone, As far as I know, WEBCON BPS doesn’t provide a built-in option to send email notifications when a comment is added to an instance. Has anyone found a good workaround or implemented a solution for this?

(...) ments: Currently its only possible to "lock" Attachments in certain steps while breaking the form-inheritence. It would be great if we could have a "readonly" for Attachments in the Field-Matrix. comment s: In some cases its necessary to "lock" also comment s (but existing comment s should be visible). Kind regards Ernst

(...) Hi, It seems that the visibility of the save comment button also in the form editing mode would be more useful and understandable for users. Please consider adding this option. Regards

(...) Hi, it would be great, if the comment (WFD_Description) would be extended with step name in which the comment has been added. Maybe the information could be stored in the format: STPID#DefaultLabel$$DE$$Translated Label" This would allow us to select the correct label if we are parsing the comment ourself. Best regards, Daniel

(...) 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 "cancel (...)

(...) following colors: Red – system fields e.g. instance ID, instance number, process, workflow, current step, form type, modification date, created date, author, modified by, current version, comment field. Blue – the fields defined in the process (configured) e.g. text fields, numerical fields, choice fields. Keys in the WFElements table: WFD_ID – main key (instance ID) (...)

(...) type   Below, in the “Standard” tab there is the “Append mode” which allows you to add a message below the text field with the date of saving and author’s comment . The entries added in this way cannot be edited later. The last option to select is the position of the text field name, where the user can select whether the name is next to (default setting) or a (...)

(...) form at the Registration step.   Fig. 4. The main form   On the left, there is information about the contractor and invoice details. On the right – the attachments and comment s section. Below them, there is a chart displaying the values of the unpaid invoices. At the bottom of the form on the item list, all invoices registered for this contractor are listed. By default, (...)

(...) e – when the workflow instance triggers this action, their parent instance will be updated (after selecting this mode as active – only the choice fields of the parent process and entering comment remain) Form field value – the “Instance identifier” field will become active. You must enter a variable which refers the form field that contains the instances ID. The instance t (...)

(...) "id": 11, "guid": "34e8eb1b-cb17-4ece-97f8-26aeeb2d2d94", "svalue": "3.00", "value": 3.0 } ] } ] } ], "comment s": { "existingEntries": [ { "author": "Tom Green", "comment ": "test", "date": "2020-01-31T14:07:55+01:00" } ], "newcomment ": "" }, "attac (...)

(...) translations. This can be useful in a situation where users from different countries/using different languages are assigned to the same workflow. This applies especially to user-completed text boxes, comment s, and the content of attachments.   Application language The application language can be set in WEBCON BPS Designer Studio (Fig. 6).   Fig. 6. The change of the applicat (...)

(...) ;The configuration of the “Change value of single field” action   Field – all form fields related to the form used in the process, and also system fields such as [System] comment and [System] Parent workflow instance ID. comment author – selecting “[System] comment ” enables you to select the comment author and set the comment value. Selecting the “[ (...)

(...) oke privileges   At the “Eligibility for equipment” step, the employee must return the equipment listed in the item list. The person responsible for the offboarding process can comment and confirm that the item has been returned.     Fig. 6. The Handwritten signature form field on the form - eligibility for equipment   The last step is to sign the doc (...)

(...) ction – this section is visible. Attachments are added by default on the right panel of the form. The attachment can be added to the form only by the user who has the modification privileges. comment s section – this section is visible. comment s are added by default on the right panel of the form. The comment can be added by the user who has the read privileges.   Additionally, (...)