Webdynpro Development Component Callable Object Escalation

[Former Member]

Hi,

In gp sequential block workflow using webdynpro development component callable objects When the initiator intiates a workflow ,it is assigned to the first approver.Now if the approver does not take any action within 2 days i want to escalate the task to the second approver.How can i do this escalation?

There is a standard parameter call <b>due date</b>...in action.How can I set this value dynamically from my application..

During escalation , the next approver has to be taken by executing an rfc in the background

Please help....

Thanks,

Shamila

[ankur_garg5 · Accepted solution]

Hi Shamila,

Have a look at the following thread:

Bye

Ankur

Do reward points if it helps!!

[Former Member · Accepted solution]

hi,

Thread which you have specified looks similar to my scenario.

Can to tell somthing about <b>custom application service</b> and about <b>Background Callable object</b>.How these two can be used to do escalation?

Please Help.................

Regards,

Shamila.

[former_member4529 · Accepted solution]

Hi,

You can define a CAF Core application service (implemented in the CAF Core layer) or a background CO (implemented by a J2EE class interface) which can call a RFC to get the next approver and return the next approver's user id as an output parameter. You can use dynamic user assignment in the next action (approval), by selecting the processor as "Filled From Context Parameter" (at the Roles tab in block level) and select the user id output parameter of the background CO/CAF app service CO.

You can get more details on different types of CO at the CAF Tutorial Center @SDN

Thanks,

Dipankar

[Former Member]

I would suggest to create External Service of RFC which is going to give you the approver ( you have to make sure that this approver is also defined in portal-because it is portal user which executes the GP Steps). By defining the External Services you are getting away from hassle of maintinng JCO connection and others. Create a remote entity called RApprover - tie it up to External Service. In the backGround Callable object read this entity ( which will give you the backend user) and assign it to the process step which you want. Again there has to be trigger to this CO - Action on due date.