Interrogation of controls during Application Discovery
Please, I need a clarification regarding interrogation of controls during Application Discovery in Pega Robotics. I have read in PDN that you need to interrogate representative controls of the use case. I don't know if it is due to a language misunderstanding (English is not my mother tongue). What is exactly the meaning of "representative controls"? Do they mean only A FEW of them (or at least one) of each type of control involved in the use case? Or should be interrogated ALL controls involved in the use case?
I think the correct answer is the first one, but I'm not sure, because I can found in the forum reasons in both directions:
A FEW (or at least one): It is quick. It has sense if you can start the interrogation with the full use case design not finished (as I have read too), but maybe you can miss controls with problems and have a block in the future.
ALL: You are going to find for sure all controls with problems, but how to do it if maybe the use case design is not finished yet?
A few (or at least one) of each control 'class' is generally a best practice. This way you can verify that all controls types/classes interrogate correctly and have the functioning methods that you need.You do not need to interrogate every control during app discovery.