Thank you for your question. I am willing to know at what kind of use cases do we user the data type as ‘Page Name’. I read that it has to be defied in the pages and classes tab if we want to define a parameter of data type ‘Page Name’. But the question is what is the use case that we can leverage the page name as data type in the parameter. Please see the screenshot below from an activity . I just made up a Parameter Name ‘LeverageIt’.
It can be used in many situations, in fact it should be used when you are trying to build a reusable activity where you want the calling activity to pass in a page name as per their wish and you can then process data on that particular page.
For e.g. let's say you have an activity "A" defined which called a connect-soap and gives back data. Now if you want this activity "A" to return data on a page which is defined by the calling activity then you will have to set the data on parameter page and let the calling activity pass any page name to get the data back.
Using this will make your activity more reusable in same manner as does any other parameters.
Thank you for your reply. I have a use case where there is a Property (an , Attribute, say X). The X is a filter condition and can take one or more values to be passed as the request parameter for a REST call. I was looking at the possibility of using X as a Parameter with the data type of Page Name, but again there are multiple values like (for example):