nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

WFM - custom initialisation

thatfish

Hi,

I've a WFM workflow with a custom initialisation screen.

When I choose a file and "New Job" the custom initialisation screen fires up and the job instantiates as expected. All is great.

However, when I do not choose a file and try to start the Job with nothing attached I get the default initialisation screen (NOT the custom one).

Have I forgotten something fundamental about how Workflows operate or is this expected behaviour ?

i.e. the requirement I am having difficulty with is for the custom initialisation screen to be used always upon a "New Job" whether or not a file is attached upon Instantiation.

thx - steve

Linux | TS 672

Find more posts tagged with

Comments

Faizi

Hi,

I've a WFM workflow with a custom initialisation screen.

When I choose a file and "New Job" the custom initialisation screen fires up and the job instantiates as expected. All is great.

However, when I do not choose a file and try to start the Job with nothing attached I get the default initialisation screen (NOT the custom one).

Have I forgotten something fundamental about how Workflows operate or is this expected behaviour ?

i.e. the requirement I am having difficulty with is for the custom initialisation screen to be used always upon a "New Job" whether or not a file is attached upon Instantiation.

thx - steve

Linux | TS 672

It seems a strange behavior. It should come with custom instantiation screen. Check out the defaul_config and custom_instantiation. It should be parallel. If not configured with branches.

What happens with Assign and Submit?

thatfish

Its not configured with any branches.
Assign and Submit are OK which is what I'd expect because a file has to be attached initially.

It is odd that the instantiation screen ignores the customisation configuration when no file is initially attached.

Faizi

Its not configured with any branches.
Assign and Submit are OK which is what I'd expect because a file has to be attached initially.

It is odd that the instantiation screen ignores the customisation configuration when no file is initially attached.

Ok. As mentioned you are using TS 6.7.2, there might be a bug with this version. There is already released SP1 of TS 6.7.2 which resolved some bugs.
So you can raise a case to Autonomy Interwoven support or upgrade.

Adam Stoller

There is already released SP1 & SP2 of TS 6.7.2 which resolved some bugs.

I think you're a bit premature here - I don't believe that SP2 has been released at this time (not even sure if it exists internally).

Faizi

I think you're a bit premature here - I don't believe that SP2 has been released at this time (not even sure if it exists internally).

Oops! it was written by mistake.
Thanks for the pointing.