The value of attribute "dn" can contain context variables.
属性“dn”的值可以包含上下文变量。
The value of attribute "baseDN" can contain context variables.
属性“baseDN”的值可以包含上下文变量。
It can contain context variables like %htm:property.myProperty%.
该属性可以包含诸如 %htm:property.myProperty%等 上下文变量。
The value of the attribute "filter" can contain context variables.
属性“filter”的值可以包含上下文变量。
The attribute "name" is mandatory and can contain context variables.
属性“name”是强制的,并且可以包含上下文变量。
The attribute "groupName" is mandatory and can contain context variables.
属性“groupName”是强制的,并且可以包含上下文变量。
Human Task Manager supports the following context variables for staff resolution.
HumanTaskManager支持将下列上下文变量用于人员解析。
The use of multi-value context variables is limited to one per staff query element.
多值上下文变量的使用限于每个人员查询元素一个。
Be aware that this is the reason for the restricted number of multi-value context variables.
请注意,这就是限制多值上下文变量数量的原因。
The name attribute is mandatory, and can contain context variables that resolve to a single value.
name属性是强制的,并且可以包含解析到单个值的上下文变量。
Not all the values of context variables are always available during the task or escalation lifecycle.
并不是所有上下文变量的值在任务或升级生命周期中始终都可用。
Multiple multi-value context variables would result in a matrix multiplication and are not supported.
多个多值上下文变量将产生矩阵乘法,并且不受支持。
The number of multi-value context variables is restricted to one variable per <sur:user .../> element.
多值上下文变量的数量仅限于每个 <sur:user .../>元素一个变量。
The number of multi-value context variables is restricted to one variable per <sur:search .../> element.
多值上下文变量的数量仅限于每个 <sur:search .../>元素一个变量。
The number of multi-value context variables is restricted to one variable per <sldap:user .../> element.
多值上下文变量的数量仅限于每个 <sldap:user .../>元素一个变量。
The parameter value is exactly the value you would enter in the task editor, including context variables.
参数值正是您要在任务编辑器中输入的值,其中包括上下文变量。
Because inline human tasks have access to the process context, they can access process context variables.
因为内联人工任务可以访问流程上下文,它们可以访问流程上下文变量。
The plug-in supports static staff assignments and context variables, but not retrieval of e-mail addresses.
该插件支持静态人员分配和上下文变量,但不支持对电子邮件地址的检索。
Inline human tasks have access to the process context and thus they can also access process context variables.
内联人工任务可以访问流程上下文,因此它们也可以访问流程上下文变量。
The number of multi-value context variables is restricted to one variable per <sur:usersOfGroup .../> element.
多值上下文变量的数量仅限于每个 <sur:usersOfGroup .../>元素一个变量。
The number of multi-value context variables is restricted to one variable per <sldap:usersOfGroup .../> element.
多值上下文变量的数量仅限于每个 <sldap:usersOfGroup .../>元素一个变量。
For inline human tasks that have access to the business process context, additional context variables are available.
对于能够访问业务流程上下文的内联人工任务,还有附加的上下文变量可用。
At run time, the plug-ins are invoked with the deployed query and a list of resolved context variables as parameters.
在运行时,将使用已部署查询和已解析的上下文变量列表作为参数来调用该插件。
If a percent sign is required to be used within a string where context variables can be used, then use double percent signs (% %).
如果需要在可以使用上下文变量的字符串内部使用百分号,则应使用两个百分号(% %)。
A possible reason for context variables not being replaced, is that staff resolution happens before the context information has been set.
上下文变量未替换的可能原因是人员解析发生在设置上下文信息之前。
Such unreplaced context variables may lead to failing staff queries, and you should check for them if your staff query fails unexpectedly.
此类未替换的上下文变量可能导致人员查询失败,如果人员查询意外失败,您应该检查这些上下文变量。
GroupDN is a mandatory attribute that specifies the distinguished name of the LDAP object to be retrieved and can contain context variables.
groupDN是一个强制属性,用于指定要检索的LDAP对象的专有名称,并且可以包含上下文变量。
Single value context variables evaluate to a string that is replaced in the parameter context, for example %wf:process.starter% evaluates to sarah.
单值上下文变量计算为在参数上下文中替换的字符串,例如,%wf:process.starter%计算为sarah。
In case of name collisions with context variable resolved by the Human Task Manager, the intermediate result overrides any "normal" context variables with the same name.
在名称与HumanTaskManager解析的上下文变量冲突的情况下,中间结果将覆盖任何具有相同名称的“普通”上下文变量。
If a certain rule is matched, the rule name and its destination are stored in WebSphere DataPower context variables var://context/dw/route and var://context/dw/ruleName.
如果某个规则匹配,则将规则名称及其目的地存储在WebSphereDataPower上下文变量var://context/dw/routeand var://context/dw/ruleName 中。
应用推荐