500-440 · Question #86
In Cisco Finesse, which two workflow action types can be configured via the administration page? (Choose two.)
The correct answer is A. HTTP Request D. Browser Pop. Cisco Finesse workflow actions configured via the administration page are limited to HTTP Request (A) and Browser Pop (D) - these are the only two action types natively supported in the Finesse Admin UI for triggering external integrations and screen pops when contact center even
Question
In Cisco Finesse, which two workflow action types can be configured via the administration page? (Choose two.)
Options
- AHTTP Request
- BTimer Action
- CScheduled Call Back
- DBrowser Pop
- ERun Macro
How the community answered
(45 responses)- A91% (41)
- B2% (1)
- C2% (1)
- E4% (2)
Explanation
Cisco Finesse workflow actions configured via the administration page are limited to HTTP Request (A) and Browser Pop (D) - these are the only two action types natively supported in the Finesse Admin UI for triggering external integrations and screen pops when contact center events occur.
Why the distractors are wrong:
- B (Timer Action) - not a Finesse workflow action type; timers are not a built-in action category in Finesse workflows.
- C (Scheduled Call Back) - this is a contact center feature (e.g., in Cisco ECE or UCCX), not a Finesse workflow action type.
- E (Run Macro) - macros exist in some CTI/desktop environments (like Cisco Agent Desktop), but Finesse workflows do not expose a "Run Macro" action through the admin page.
Memory tip: Think "H-B" = HTTP + Browser - Finesse workflows let you hit an endpoint (HTTP Request) or pop a browser window (Browser Pop). Everything else is out of scope for the admin workflow UI.
Topics
Community Discussion
No community discussion yet for this question.