The task is assigned to an invalid group XXXX in realm jazn.com. The routing slip is associated with the task definition default/DisconnectedProvisioning!2.0/ManualProvisioningTask.
(Doc ID 2413999.1)
Last updated on FEBRUARY 21, 2020
Applies to:
Identity Manager - Version 11.1.2.3.0 and laterInformation in this document applies to any platform.
Symptoms
The OOTB DisconnecteProvisioning composite was customized so fulfilment are sent to an admin group instead of the default xelsysadm user
On requesting a disconnected application instance the request fail with the following error in the SOA logs:
[2018-06-21T11:34:47.315-06:00] [SERVERNAME] [WARNING] [] [oracle.soa.services.notification] [tid: [ACTIVE].ExecuteThread: TID for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: <anonymous>] [ecid: ECID] [APP: soa-infra] <.> With the current setting, only Email notifications will be sent; Notifications via voice, SMS or IM will not be sent. If you would like to enable them, please configure corresponding sdpmessaging driver. Then modify the accounts and set NotificationMode attribute to ALL in workflow-notification-config.xml
[2018-06-21T11:34:47.365-06:00] [SERVERNAME] [ERROR] [] [oracle.soa.services.workflow.task] [tid: orabpel.invoke.pool-4.thread-7] [userId: weblogic] [ecid: ECID] [APP: soa-infra] [composite_instance_id: 210105] [component_instance_id: IE] [composite_name: DisconnectedProvisioning!2.0] [component_name: ManualProvisioningTask] <.> Error in routing slip.[[
The task is assigned to an invalid group CUSTOM_GROUP in realm jazn.com. The routing slip is associated with the task definition default/DisconnectedProvisioning!2.0/ManualProvisioningTask.
Verify that the group is specified correctly in the routing slip in the task definition.
ORABPEL-30050
Error in routing slip.
The task is assigned to an invalid group CUSTOM_GROUP in realm jazn.com. The routing slip is associated with the task definition default/DisconnectedProvisioning!2.0/ManualProvisioningTask.
Verify that the group is specified correctly in the routing slip in the task definition.
at oracle.bpel.services.workflow.task.impl.WorkflowUtil.validateGroup(WorkflowUtil.java:1014)
at oracle.bpel.services.workflow.task.impl.WorkflowUtil.validateTaskAssignment(WorkflowUtil.java:898)
at oracle.bpel.services.workflow.task.impl.RoutingSlipInterpretorHelper.validateTaskAssignment(RoutingSlipInterpretorHelper.java:251)
at oracle.bpel.services.workflow.task.impl.RoutingSlipInterpretor.setTaskAttributesFromParticipant(RoutingSlipInterpretor.java:3409)
at oracle.bpel.services.workflow.task.impl.RoutingSlipInterpretor.evaluate(RoutingSlipInterpretor.java:2881)
at oracle.bpel.services.workflow.task.impl.RoutingSlipInterpretor.evaluateOnOutcomeUpdatedOrInfoSubmitted(RoutingSlipInterpretor.java:2680)
at oracle.bpel.services.workflow.task.impl.RoutingSlipInterpretor.evaluateOnOutcomeUpdatedOrInfoSubmitted(RoutingSlipInterpretor.java:2712)
at oracle.bpel.services.workflow.task.impl.RoutingSlipInterpretor.evaluate1(RoutingSlipInterpretor.java:637)
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Cause |
| Solution |