Hiding Appian Record Header in Related action View

Hello Anjali,

Instead of accessing the related actions from the 'Related Actions' view, you can enable users to access them through 'Related Actions shortcuts' on the summary or any other views. This approach eliminates the need to view the record header and title, and the related action will open in a dialog box.



If you prefer, you have the option to hide the 'Related Actions' tab as well.

Thanks for the response, however I think I was not able to explain my question.

Let's say that I have a related action to update a record, I have an interface (suppose home page) where I created a "link to the record related action, and set it to open in new tab".

See the image below for instance, here the Update case related action is shown in this grid.

When the user clicks on 'UPDATE CASE', a new tab opens and the Update record interface shows up, however in this new tab, we can see the 'Record Header' on top along with Headers of all the views of that record like Summary, etc. Like this-

The requirement is to hide the tabs from top of the page on Update Case interface. I hope I was able to explain the question.

Why would you want to navigate to the related actions view first? I my mind, it would make sense to open the related action directly from that button in your grid.

I don't think it is possible to hide the record headers by opening the related actions in a new tab. Ideally, you can achieve this by doing the following:

1. As mentioned earlier, configure the related action to open in a dialog box.

2. Otherwise, you can use 'a!startProcessLink' to start a process and navigate the user through any start form or the first chained attended node and any subsequent chained forms. This way, you will not see any headers at the top; however, the form will be opened in the same tab.

Thanks Madhurambika, these 2 options are certainly there. I was wondering if we could have related actions work in a new tab, seems like we can't. 

Cheers!

Hey  

I am trying to open related actions from the button itself. The question was whether it is possible to not see the record headers and the names of different record views when update case page opens up.

I think there is a good reason to show the header. It provides the necessary context to the user to know what he is doing.

BTW, did you consider to open the related actions in a dialog?

Yes, dialog box does work however the form is bigger and the dialog box doesn't do justice with it.

Also, albeit I understand the point of showing the Record Header (for eg, Case name...) for context, but why do we not have the option the hide the tabs with labels of the different record views (summary, audit, etc.). It creates a distraction for the user opening the record action and if they mistakenly click on Summary tab, they immediately leave the form and that can be confusing. 

At this point, I feel my best bet is to go with a!startprocesslink(), notwithstanding that I really wanted to make use of Record Related actions feature. 

The reason is, that Appian follows a specific paradigm for implementing such things. And while you can customize a lot, in my experience doing so does not make development and usage any better or easier.

I try to understand what the Appian product had in mind and follow these lines. With great success in the last 14 years.

One last question: Did you configure the dialog size to its maximum?

Yes I tried maximum dialog box size but that is not acceptable to the end user.

I am thinking to make use of a!startprocesslink() for this use case. In that scenario, user clicks to open Update form, after that if they simply click away from the screen, how do we cancel the task in the process model? I am aware that we can use time-based exception in the task, but do you have any suggestions regarding how to immediately end that task if user click away from the screen?

Did you try to use the process start form feature?

I really recommend to use the Appian features. Trying to work around it will just increase the cost of development and result in inconsistent UX across applications.

We cannot react on the event a user closing a window or navigating away. The only option is this: https://appian.rocks/2022/06/23/task-exceptions-quick-tasks/

Did you try to use the process start form feature?

I really recommend to use the Appian features. Trying to work around it will just increase the cost of development and result in inconsistent UX across applications.

We cannot react on the event a user closing a window or navigating away. The only option is this: https://appian.rocks/2022/06/23/task-exceptions-quick-tasks/