The CallProfileAndPassBackDataResponse (Responder) can be assigned to a profile in Phase 6 for a response path. It transfers the content defined for the response path to another profile (e.g. a cron job), waits for its response (e.g. via CronPassBackDataResponse (Responder)) and then transfers it as a return value to the profile caller (e.g. an HTTP or portal profile).
When creating the response path the category Custom class must be selected so that the CallProfileAndPassBackDataResponse (Responder) is selectable under Class:

In the Additional parameters field, a parameter list with the parameters listed below must be specified. Only the first parameter (Profile name) is 'required'.
Parameter | Designation | Required? | Default | Description |
|---|---|---|---|---|
1 | Profile name | Profile name or a message queue with profile name (Notation: | ||
2 | Backup change |
|
| |
3 | Error change |
|
| |
4 | Force trigger cron job |
|
| |
5 | Use direct trigger job |
|
| |
6 | Apply result vars |
|
| |
7 | Fail on inner error |
|
|
Examples
Parameter list with direct profile call
The following parameter list calls a profile named CronFetchDB. The further parameters define that:
The input file is kept as backup (Backup change:
false).An e-mail notification is sent in cases of error (Error change:
false).The response path is still considered error-free in cases of error in the called profile (Fail on inner error:
false).
â–ºNOTEâ—„ For all parameters 'without value' the default value is true (see table above for meaning).
Example parameter list with profile name:
CronFetchDB;false;false;;;falseParameter list with profile call via a message queue
The following parameter list calls a profile with the name my_profile in context my_context using the Message Queue my_queue.
Example parameter list with profile name:
my_context:my_queue:my_profileâ–ºNOTEâ—„ For the optional parameters 2 to 7 ('without value') the default value is true (see table above for meaning).