K2 Five

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. Consistent names of constructs across all designers and reports

    Process/Workflow, Step/Activity, Task/Event, Date Field/Variable, reports still use old actual object names while Designers are using newer friendlier names - confusing

    Use the corrected modern names in all manifestations of the product where they are found. This simplifies documentation, tutorials, and the understanding of the platform.

    Specific: Set values in Data Fields, or something kind of like a Variable but the task is set Data Field. Are we talking process data fields, or variable, or step or activity data fields? Because these constructs persist, they are a field and variable is an incorrect term. Move to "Environment Data Fields", "Workflow…

    0 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Workflow  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  2. Task User - Action Result not in K2 5.2

    In the K2 Five (5.2; 5.1) version, when designing the process, there is no possibility to provide information on the decision made (Action Result property).

    In earlier versions 4.7 and earlier such functionality existed and could be passed as a process field. After obtaining the information, these data are only selectable in the K2 Five 5.3 version.

    I attach the information from K2:

    https://help.k2.com/onlinehelp/k2five/userguide/5.3/default.htm#Whats-New-Five/Whats-New-Five.htm

    https://help.k2.com/onlinehelp/k2five/userguide/5.3/default.htm#How-Tos/WorkflowTaskActionResult/Workflow-Task-Action-Result.htm

    We need this functionality in versions of K2 Five 5.2 - in particular in this version where it is used by most customers

    0 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Workflow  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  3. Validation before the removal / renaming of a workflow

    I believe there should be something like a validation before the removal / renaming of a workflow for any workflows using the to remove workflow as a subflow and with open errors on the subflow step.

    If these occur you should be prompted with a message to resolve the errors first

    0 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Workflow  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
1 2 3 4 6 Next →
  • Don't see your idea?

Feedback and Knowledge Base