Good morning René,

You can accomplish this by creating a task and set this task as your startobject. The task can start a processflow which can finally open the landing page you would like to show. On this landing page you can implement a checkbox which says 'Don't show again’. If the user chooses to check the checkbox this will be saved in the database.

The next time the user starts the GUI and the startobject task will run again you can check the checkbox value and use a process procedure to skip opening the landing page and immediately stop the processflow.

I hope this helps you out.

Kind Regards,

Roel

That works .

For common interest; I've set up a process flow as below:

Where in the first task executing is decided if the document ‘intro’ must be opened, or skipped using a suppressed message:

if @a_condition_when_not_to_showbegin  exec dbo.tsf_send_message ‘suppress’, null, 1end

Where suppress is a suppressed message (Message location: None):

The second task is a question which will save the @a_condition_when_not_to_show variable.

I do have one more question; After opening the ‘Open document intro’ step it immediately executes the next task, which is a bit prompting (takes away the attention from the intro doc). Is it possible to open the task after closing the ‘intro’ document?

I've tried this without success:

I'm not sure if ‘Close document’ is a valid entry point for a process flow.

I forgot to mention that you also have to configure a start object at ‘Group preferences’, this can be done in IAM and cannot be overriden by end users:

This start object needs to be the first task (user_first_start in the example).

I do have another question:

The ‘intro’ document is a view with only a ‘preview’ component in it. When the ‘intro’ is opened again, it reloads to the beginning. Is it possible that this subject doesn't reload?

Take this example below: I open ‘Documentation’, when I open another subject and switch back it suddenly restored to the begin page, in stead of the page where I left (‘Naming’).

Hi René, 

Close document can not be used as a process flow trigger at the moment. Feel free to submit an idea for that.

I cannot reproduce the reload of the preview after switching between documents. Did you happen to enable auto-refresh for the subject? Or is this perhaps a side effect of the Close document process flow?

By the way, the preferred way to disable subsequent steps in a process flow is to clear the order number of the process action using the process flow logic. I'm not sure the suppresses message will work in all (future) GUIs.

See here for more info.

I've tested it again, it only occurs on the web gui I see. The Windows GUI works as expected. I'll add an issue to TCP if we consider using this (we also have another idea regarding ‘onboarding new users’, which is we think even better).