Hi all, a supplement of salutations would be a good thing for forms and especially for the autmatic email. Of course you could do that via a form field "Salutation", but I think it would be a relief and not a big hassle to implement this idea. A problem that I see is that already created account would have to supplement their salutation afterwards. As an example: Dear #Fall / Creator / Salutation #Fall / Creator / Surname ...more »
In order to control the execution of tasks on a daily basis, the integration of a holiday calendar is essential.
Introduce a governance workflow so that any Dictionary additions have to be approved by a "Guardian" role.
While the Dictionary tool is useful, it is not powerful enough to act as a Business Concept Model. I would like to be able to have a business-friendly, visual model of the key concepts that are important to a business and the relationships between those concepts. I would also like to be able to document attributes of each concept. Currently, the dictionary does not allow me to show relationships between entries (e.g., ...more »
As of today (22.02.2019) it is only possible to collect information in "list format", for example by taking a number field and allowing several entries. Often, however, tabular entries are necessary or very useful Practical example: I would like to record ideas for the further development of a software in a workflow, every idea (often you have more than one) should get a priority and a cost estimate. Idea 1 Prio 1 Effort ...more »
When using the annotation function, it would be helpful to be able to comment on comments from others. In addition, it should be possible for those whose comments have been commented to receive an email as an indication. This would allow for a better exchange and, in the event of an ignored or rejected suggestion for improvement, a justification could be sent to the commenter. / When using the comment function, it would ...more »
Expand the legend in the HUB with all the symbols used. As an example the risk / control overlay attributes could be explained there.
It would be very helpful to have the possibility to reference one dictionary entry from another (like attached documents).
As the only way to have all participants of a process (on process step level) is the usage of additional participants sometimes the process diagram gets "overloaded" with these symbols required more or less only for RACI purposes. The idea is to have a "switch" per type of responsibility which controls the visibility of the additional participants symbols within the process diagram on process level. The attached picture ...more »
The fields to be maintained can be configured by the administrators in case of risk and controls, similar to the quick model. This allows each administrator to configure and set the columns that are important to the business for the users.
For better coordination of interfaces and for process optimization, it would be useful if the output of a task / process would have to be matched with at least one input of a follow-up task / process. This would then again be confirmed by a "handshake" of both process owner / manager.
If a comment changes to a Released process, the status should not require a new release.