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; } } }

Simplify all job instantiation screen into 1 screen

ivanho

Hi,

Would like to check how do i simplify the workflow instantiation screen all into one screen.

Right now there's some default screen like Task Comment, Metadata etc.

Can i put everything into the 1st screen and submit deploy when submit ?

Find more posts tagged with

Comments

Adam Stoller

Hi,

Would like to check how do i simplify the workflow instantiation screen all into one screen.

Right now there's some default screen like Task Comment, Metadata etc.

Can i put everything into the 1st screen and submit deploy when submit ?

Generally speaking - the answer is "yes" - but without knowing more details it is difficult to provide a more enlightened response.

nipper

I am not so certain about Adam's response.

Yes in External/CGI tasks you can put read WF variables to get data, say from the instantiation screen.

However you also mention transition comments, I do NOT think you can get rid of those (there have been a lot of threads about that). Even if you could to, how would you fill out a review comment before the review has happened ?

ivanho

Ghoti:

What version of TeamSite (including service pack and patch information)?
> 7.0 without patch.

Is this a WFM or a WFM? Is this a custom workflow or an OOTB workflow?
> It is a custom workflow model. Btw, what's the other "a WFM"

Nipper:

However you also mention transition comments, I do NOT think you can get rid of those (there have been a lot of threads about that). Even if you could to, how would you fill out a review comment before the review has happened ?
> I am thinking to combine the custom screen with the default screen for the review comment. Is that NOT possible ?

Adam Stoller

Ghoti:

What version of TeamSite (including service pack and patch information)?
> 7.0 without patch.

Is this a WFM or a WFM? Is this a custom workflow or an OOTB workflow?
> It is a custom workflow model. Btw, what's the other "a WFM"

Nipper:

However you also mention transition comments, I do NOT think you can get rid of those (there have been a lot of threads about that). Even if you could to, how would you fill out a review comment before the review has happened ?
> I am thinking to combine the custom screen with the default screen for the review comment. Is that NOT possible ?

A "WFM" is a "Workflow Model" - a "WFT" is a "Workflow Template" - if you're using Workflow Modeler then you're dealing with WFMs.

Now - where are you expecting the review comment to be entered?
If you're trying to put it into the instantiation screen, that implies that the review took place before the workflow was ever started - which doesn't make a lot of sense.

You either need to do a much better job of describing what you are trying to do - or you need a heck of a lot more training (or hire someone with more experience).

image.png

ivanho

I am just replying to your "Is this a WFM or a WFM?".

I would like to simplify this both Screen 1 and Screen 2 all into 1 Screen. What i mean by comment box is actually a Task Comment box (not the reviewer).

Agree with you reviewer comment comes after the instantiation. But I dont need to do anything with that one.

Hope to get some enlighten answer from DevNet members.

Thanks.

Adam Stoller

I am just replying to your "Is this a WFM or a WFM?".

Doh! Okay my bad - the first one was supposed to be "WFT" - sorry for casting aspersions based solely on that.

I would like to simplify this both Screen 1 and Screen 2 all into 1 Screen. What i mean by comment box is actually a Task Comment box (not the reviewer).

Agree with you reviewer comment comes after the instantiation. But I dont need to do anything with that one.

Hope to get some enlighten answer from DevNet members.

Thanks.

Since I don't know what your workflow is doing it is difficult to understand what you are trying to do - the second image is clearly a task-transition comment, which shows up as the result of transitioning a task (like if your start task is a metadata CGI task) and as far as I know there's no way to either get rid of it or merge it into the job instantiation form (which I still don't believe makes any sense).

Can you describe your workflows process flow? Especially what is your 'start' task?

ivanho

Ghoti,

Yes. The start task is a metadata CGI task --> then the default task-transition comment box will be shown ---> fill up the comment ---> transit to generate HTML.

What we are trying to achieve, can I include the default task-transition comment box (Screen 2) into my (Screen 1).

It becomes something like this:

metadata CGI task + fill up comment (1 screen) ---> transit to generate HTML.

Adam Stoller

Ghoti,

Yes. The start task is a metadata CGI task --> then the default task-transition comment box will be shown ---> fill up the comment ---> transit to generate HTML.

What we are trying to achieve, can I include the default task-transition comment box (Screen 2) into my (Screen 1).

It becomes something like this:

metadata CGI task + fill up comment (1 screen) ---> transit to generate HTML.

In short - no - the flow is:
[instantiation]->[CGI]->[transition comment]->[generate...]

There's no way that you can put the transition comment on the instantiation form or the instantiation form after the CGI.

It would be nice to find a way to omit the transition comment window after the metadata CGI task, but I'm not sure it that's possible [in a supported way]

The other possibility is that you write your own CGI for capturing the metadata (or running the OOTB metadata capture form) and do not use the actual Metadata Task in the workflow (I have a feeling it might be the specifications of the task itself which forces the transition comment window to be displayed but I haven't spent any time trying to verify it.