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 automatically inside IFrame as default in order to reduce migration effort.
How to use¶
Important
If there is no configuration, a process/task is started inside IFrame as default.
Follow these steps:
Your HTML User Dialog must be independent from Portal, could use the
frame-8
template in designer, or your own template, Portal will render it automatically in IFrameTo pass some supported params in IFrame such as process steps, refer to IFrameTaskTemplate
If you don’t want to use the default configuration, follow one of these 3 levels to open your task(s) in IFrame:
Task level: in Task custom fields, set the
embedInFrame
String field totrue
: start inside IFramefalse
: not start inside IFrameDon’t set to check case level
Case level: in Case custom fields, set the
embedInFrame
String field totrue
: start inside IFramefalse
: not start inside IFrameDon’t set to check engine 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 settings, refer to HowTo: Update Portal settings