IFrame in Portal

Do you want to decouple your project and Portal when start a task to reduce your migration effort? If the answer is yes, this chapter will help you.

Since Portal 8, we introduce new feature that a process/task could be started inside IFrame, means that you can feel free to design your html dialog independent from Portal, it is rendered inside IFrame in order to reduce migration effort.

How to configure

There are 3 levels:

• Task level: in Task custom fields, set the embedInFrame String field to

  • true: start inside IFrame

  • false: not start inside IFrame

  • Don’t set to check case level

  

• Case level: in Case custom fields, set the embedInFrame String field to

  • true: start inside IFrame

  • false: not start inside IFrame

  • Don’t set to check application level

  

• Engine level:

  • Portal Administrator could choose the option that all of the tasks in whole engine are started inside IFrame or not via the EMBED_IN_FRAME Portal variable in Global settings

Important

If there is no configuration, a process/task is started inside IFrame as default.

How to use

Follow the steps:

1. Configure as the above instruction to start your task inside IFrame

2. In your task, open a HTML User Dialog independent from Portal:

   • Create a dialog with the frame-8 template in designer, or use your own template to separate your css styles from Portal (highly recommend)

3. To pass some supported params in IFrame such as process steps, refer to IFrameTaskTemplate