How to load a interface with record type object in Appian 19.4

you can load data in your process in the form of a specific cdt (the objects of a record type are basically data in cdt shape). pass this loaded data as process variable to the user input task (and to your form). Then call just the attributes of your CDT object in the form as you like

HI Richard , I am using report object in site. And also i want to re use views and related action created in record instead of creating new form . Correct me if my understanding is worng

To understand:
you have built a report . lets say with a column chart. You show this report on a site. There you reference to a specfic "record type object". Then you want to click on this element (record link), but instead of jumping to the "object" you want to see this data in your form. Do I get this right?

yes i have build a report , in that report i wanted to show record detail. I dont want to use record link to show the record detail , i wanted to show it on loading 

hi,

quick idea (of different possible approaches):

Try a dynamic link with a rule.

a!dynamicLink(
    label: "yourLinkLabel,
    saveInto:{
        a!save(
            target: local!yourVariable,
            value: rule!EXA_yourRule(id: local!yourRecordId)
        )
    }
)

The rule uses a code like this.

cast(
    'type!yourcdt',
    a!queryEntity(
        entity: cons!EXA_EXAMPLE_DATA_STORE,
        query: a!query(
          filter:  a!queryFilter(
              field: "id",
              operator: "=",
              value: ri!recordId
           ),
           pagingInfo: a!pagingInfo(1, 1)
        )
      ).data
)

hi,

quick idea (of different possible approaches):

Try a dynamic link with a rule.

a!dynamicLink(
    label: "yourLinkLabel,
    saveInto:{
        a!save(
            target: local!yourVariable,
            value: rule!EXA_yourRule(id: local!yourRecordId)
        )
    }
)

The rule uses a code like this.

cast(
    'type!yourcdt',
    a!queryEntity(
        entity: cons!EXA_EXAMPLE_DATA_STORE,
        query: a!query(
          filter:  a!queryFilter(
              field: "id",
              operator: "=",
              value: ri!recordId
           ),
           pagingInfo: a!pagingInfo(1, 1)
        )
      ).data
)

thank you for responding. my requirement is to  show the record view and related action as it is in record on loading of report tab  . I am not sure if this can be achieved or not in 19.3 

the record view is basically a form.
any issue not using it? 
The header and tabs functions are not able to be copied.  That you have to rebuild manually.
But what is the exact requirement? Why need it to be the exact same view? Is similar sufficient? 

i am using search criteria form . on click of submit button , it will show grid with data. in one column i am calling record link to view its detail for eg , employee details on click of id . if i come back to search screen , search result is cleared out because form is reloaded. 

I thought about DB approach where you can store the criteria in db and loading of screen show the previous result . But i want to know if there is another approach, I hope you have understood my requirement

i am using the related action in other tabs too and User want same look and feel

Then it is more question of how to structure your form and process than a real display issue.
1.) if you leave a form via submit, you leave the form and it is realoading the initial status from scratch. (basically spoken) -> perhaps try a search button on the same form without submitting it and just switching via showwhen conditions between the different views (perhaps take a local variable with a bool value as identifier of the content to show.
2.) if a submit is necessary, save your search data in a rule input, bring it into your process and refill it afterwards again as initial content of your search. perhaps you can create an if clause with "isnull()" check for values in your rule input. If there is any, take them and search, if not take your current not loaded situation.

i think option 1 might work, thank you