Skip to content

Commit

Permalink
fix: set info user task assignee for saas and sm
Browse files Browse the repository at this point in the history
  • Loading branch information
nathansandi committed Dec 23, 2024
1 parent 19bba98 commit 3ad0868
Show file tree
Hide file tree
Showing 4 changed files with 36 additions and 0 deletions.
9 changes: 9 additions & 0 deletions docs/components/modeler/bpmn/user-tasks/user-tasks.md
Original file line number Diff line number Diff line change
Expand Up @@ -36,6 +36,15 @@ attributes can be specified simultaneously:
- `candidateUsers`: Specifies the users that the task can be assigned to.
- `candidateGroups`: Specifies the groups of users that the task can be assigned to.

:::info
When specifying the assignee attribute, ensure that the provided identifier (e.g., userId or email) aligns with the intended use case:

- Self-Managed: If the user is identified by userId, it must be case-sensitive.
- SaaS: If the user is identified by an email address, it must be case-insensitive.

This distinction ensures proper task assignment behavior in both self-managed and SaaS scenarios. Inconsistent formatting may lead to unexpected assignment issues.
:::

:::info
Assignment resources can also be used for set user task restrictions ([SaaS](/components/concepts/access-control/user-task-access-restrictions.md)/[Self-Managed](docs/self-managed/concepts/access-control/user-task-access-restrictions.md)), where users will see only the tasks they have authorization to work on.
:::
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -56,6 +56,15 @@ attributes can be specified simultaneously:
- `candidateUsers`: Specifies the users that the task can be assigned to.
- `candidateGroups`: Specifies the groups of users that the task can be assigned to.

:::info
When specifying the assignee attribute, ensure that the provided identifier (e.g., userId or email) aligns with the intended use case:

- Self-Managed: If the user is identified by userId, it must be case-sensitive.
- SaaS: If the user is identified by an email address, it must be case-insensitive.

This distinction ensures proper task assignment behavior in both self-managed and SaaS scenarios. Inconsistent formatting may lead to unexpected assignment issues.
:::

Typically, the assignee, candidate users, and candidate groups are defined as [static values](/docs/components/concepts/expressions.md#expressions-vs-static-values) (e.g. `some_username`, `some_username, another_username` and
`sales, operations`), but they can also be defined as
[expressions](/components/concepts/expressions.md) (e.g. `= book.author` and `= remove(reviewers, book.author)` and `= reviewer_roles`). The expressions are evaluated on activating the user task and must result in a
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -35,6 +35,15 @@ attributes can be specified simultaneously:
- `candidateUsers`: Specifies the users that the task can be assigned to.
- `candidateGroups`: Specifies the groups of users that the task can be assigned to.

:::info
When specifying the assignee attribute, ensure that the provided identifier (e.g., userId or email) aligns with the intended use case:

- Self-Managed: If the user is identified by userId, it must be case-sensitive.
- SaaS: If the user is identified by an email address, it must be case-insensitive.

This distinction ensures proper task assignment behavior in both self-managed and SaaS scenarios. Inconsistent formatting may lead to unexpected assignment issues.
:::

:::info
Assignment resources can also be used for set user task restrictions ([SaaS](/components/concepts/access-control/user-task-access-restrictions.md)/[Self-Managed](docs/self-managed/concepts/access-control/user-task-access-restrictions.md)), where users will see only the tasks they have authorization to work on.
:::
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -36,6 +36,15 @@ attributes can be specified simultaneously:
- `candidateUsers`: Specifies the users that the task can be assigned to.
- `candidateGroups`: Specifies the groups of users that the task can be assigned to.

:::info
When specifying the assignee attribute, ensure that the provided identifier (e.g., userId or email) aligns with the intended use case:

- Self-Managed: If the user is identified by userId, it must be case-sensitive.
- SaaS: If the user is identified by an email address, it must be case-insensitive.

This distinction ensures proper task assignment behavior in both self-managed and SaaS scenarios. Inconsistent formatting may lead to unexpected assignment issues.
:::

:::info
Assignment resources can also be used for set user task restrictions ([SaaS](/components/concepts/access-control/user-task-access-restrictions.md)/[Self-Managed](docs/self-managed/concepts/access-control/user-task-access-restrictions.md)), where users will see only the tasks they have authorization to work on.
:::
Expand Down

0 comments on commit 3ad0868

Please sign in to comment.