(...) pplications or processes should be included in the migration. Of course, an “All” option should remain available as well. I am aware that it is possible to create an action at the process level to manual ly select specific WFD_IDs and include them when assigning permissions. However, since we already have a powerful tool available at the administrator level, it would be a valuable improvement to enhan (...)
(...) e brings always an error - as expected. That's why I gave the "verify process" a try and I hope to get some warnings due to broken references. Unfortunately there is no warning and I had to search manual ly and found a broken one in a "data source value" filter as shown in the screenshot. Why isn't this indicated in the warning tab of the process verification? Kind regards Sébastien
(...) saved without clear intent or context. - Weak traceability: No consistent link between a change and a requirement, bug, or external ticket (e.g., Jira). - Inconsistent documentation: Teams rely on manual conventions, which quickly diverge. - Difficult audits: Reviewing history becomes time-consuming and error-prone. - Limited collaboration: Understanding someone else’s change requires digging into (...)
(...) introduce this feature? This functionality is quite important to us. Users frequently revisit past leaves to check specific details (approvals, comments, workflow history). Currently, they have to manual ly search for the request using its signature, which is time-consuming and frustrating. Enabling a single click on the historical chart would resolve this issue and unify the user experience for both (...)
(...) Hi, I noticed that after migrating BPS groups with a package, the group owner field appeared blank (grayed out). I click "Add" and can specify a person, but this grayed-out line needs to be manual ly deleted. Furthermore, if I didn't set a group owner, the save failed (the system cleared the group name and ID) and nothing happened. After a while, I accessed these BPS groups, and the group owner fi (...)
(...) gives me the information that I must have Cumulative update 29 (15.0.4410.1) installed to continue. The problem is that I haveall the most recent updates and when I try to install the desired update manual ly, I get: "A SQL Server update with a higher version has already been installed on SQL Server instance MSSQLSERVER, so the current SQL Server update cannot be applied. The version of the SQL Server (...)
(...) on set depending on how it was processed. For some organizations, granting broad/global access to archived elements is not acceptable due to security, compliance, and confidentiality requirements. manual permission assignment is also not realistic when dealing with large volumes of archived data. We have already consulted this case with WEBCON. Based on the analysis, this scenario cannot currently (...)
(...) Hi, it would be very helpful to have a centralized path name picker in WEBCON BPS. Instead of naming each workflow path manual ly and independently, devs could select predefined path names from a central configuration, for example: * Close * Cancel * Save * Approve * Reject * Send back * Forward * Archive Each predefined path name should also allow translations and assigning a default (...)