An integration definition can be used as an activity
-
True
-
False
This statement is false. An integration definition CANNOT be directly used as an activity in a BPD. Instead, you must wrap the integration definition in an undercover agent (UCA) or service, and then call that UCA/service from an activity in the process.
False is correct. In PRPC/Pega, an Integration definition (a Connector rule, e.g. Connect-SQL, Connect-SOAP, Connect-REST) defines how the application talks to an external system — it is its own rule type, invoked FROM an activity via a Connect-* method step. It is not itself a type of activity and cannot be dropped in as an activity step the way a sub-activity can. The two rule types serve different purposes (integration definition vs. procedural logic) and aren't interchangeable, hence the statement is false.