Display a record view in an interface

Design it from interface not from site pages. Take a attribute that differs the roles use it in If condition

a!localVariables(
  local!isusermember:a!isUserMemberOfGroup(loggedInUser(),"Group"),
/*  or some other rule that defines the attributes your role*/,
  if(
    local!isusermember,
rule!gridxyz,
rule!Summarypage 
/*(pass the id of the single user)*/
  )
)

Something like this. 

Design it from interface not from site pages. Take a attribute that differs the roles use it in If condition

a!localVariables(
  local!isusermember:a!isUserMemberOfGroup(loggedInUser(),"Group"),
/*  or some other rule that defines the attributes your role*/,
  if(
    local!isusermember,
rule!gridxyz,
rule!Summarypage 
/*(pass the id of the single user)*/
  )
)

Something like this. 

The problem is I need to see the record view, not an interface, and that is what I don't know how to do

AFAIK directly launching record view is not possible as of now . 

javierm0004 said:

I need to see the record view, not an interface

Unless i'm mistaking what you're referring to - a "record view" is still an interface.  And if we're talking about the default record list - that can just be added to an interface by building a grid, and shown conditionally.

As far as i understood he wants to see all the other tabs too

It is not exactly the same. In a record view (maybe I am using a wrong word) you can see few interfaces, each of one defined in the record object, the record actions, etc

So you're saying you want to automatically link to the record entry itself.  Unfortunately that isn't possible.  You have the choice of either showing some of the essential record details there, or providing a link directly to the relevant record, but you can't just redirect to a record entry conditionally like this.

javierm0004 said:

defined in the record object, the record actions, etc

we can replicate everything  in the interface . Record action field  for showing record actions .. And for that header we can use richtext...

If I'm understanding correctly, and you want to display all the tabs of a record, I second what  venkat Avuluri  suggested 

You can replicate all components of the record layout using rich text, buttons and other common interface components.

 javierm0004 

Something like this would give you a good start. Hope this helps. 

a!localVariables(
  local!selectedView: "SUMMARY",
  local!recordViews: {
    "Summary",
    "Record View 2",
    "Record View 3",
    "Related Actions"
  },
  a!headerContentLayout(
    header: {
      a!cardLayout(
        contents: {
          a!richTextDisplayField(
            value: {
              a!richTextItem(text: "Record Title", size: "LARGE")
            }
          )
        },
        style: "ACCENT",
        marginBelow: "NONE",
        showBorder: false()
      ),
      a!cardLayout(
        contents: {
          a!buttonArrayLayout(
            buttons: {
              a!forEach(
                local!recordViews,
                a!buttonWidget(
                  label: fv!item,
                  saveInto: { a!save(local!selectedView, fv!item) },
                  style: if(local!selectedView = fv!item, "SOLID", {})
                )
                
              )
            },
            align: "START"
            
          )
        },
        style: "STANDARD",
        marginBelow: "NONE",
        showBorder: false()
      )
    },
    isHeaderFixed: true(),
    contents: {
      a!match(
        value: local!selectedView,
        equals: "SUMMARY",
        then: {
          /*Record Summary View Interface*/
        },
        equals: "Record View 2",
        then: {
          /*Record Summary View Interface*/
        },
        equals: "Record View 3",
        then: {
          /*Record Summary View Interface*/
        },
        /*
        Other Record Views
        .
        .
        .
        .
        .
        .*/
        default: {}
      )
    }
  )
)

Luis Beteta said:

You can replicate all components of the record layout using rich text, buttons and other common interface components.

It's possible.  It's also a lot of work to allow the user to avoid having to click to the actual record item.

Don't re-invent the wheel --  I would suggest a middle approach, where selected basic details can be shown in the default interface, and a "more details" click can link them to the record itself.