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

ui variation-Workflow modeler

Nexus

Hi All,

We are using ts 671/livesite and workflow modeler.
The requirement says :
the ui screen will display or not some checkboxes depending on current user role ?
How could i achieve that with workflow modeler ?

thanks

Find more posts tagged with

Comments

Faizi

Hi All,

We are using ts 671/livesite and workflow modeler.
The requirement says :
the ui screen will display or not some checkboxes depending on current user role ?
How could i achieve that with workflow modeler ?

thanks

Would you post your requirement with explanation, So that we understand and try to find pointer.

Adam Stoller

Hi All,

We are using ts 671/livesite and workflow modeler.
The requirement says :
the ui screen will display or not some checkboxes depending on current user role ?
How could i achieve that with workflow modeler ?

thanks

I'm not sure about the LiveSite part of the equation - but for WFM - you need to create a branch-specific custom instantiation form (the process for doing so is in the WFM manual) - the form is very similar to a DCT and can utilize FormAPI functions for hiding/exposing fields, including methods like IWDatacapture.getRoles() - read the FormAPI manual for more information.

SampleForCrossTabTooltipHyperlink.rptdesign

Nexus

Gothi...Faizi many thanks for your answers .
Gothi formapi is not a problem at all WFM remains a little bit mysterious

here's the sentence stating our requirement :

[The next screen gives a Yes / No option against “Review Required”.

At this stage we would want to force Authors to send their content for review (so the Yes / No options should be removed)

Editors should still have the option to select Yes or No as on occasions they may want to send their content to another editor for approval.]

Best

N

Faizi

Gothi...Faizi many thanks for your answers .
Gothi formapi is not a problem at all WFM remains a little bit mysterious

here's the sentence stating our requirement :

[The next screen gives a Yes / No option against “Review Required”.

At this stage we would want to force Authors to send their content for review (so the Yes / No options should be removed)

Editors should still have the option to select Yes or No as on occasions they may want to send their content to another editor for approval.]

Best

N

Hi,
I got your requirement, you need to customize the instantiation screen of workflow. There is file named custom_instantiation.cfg, which need to manipulate. As you want to remove the Review Required radio button, you need to replace it with textbox and set default value is true, make it hidden so that it will not display on instantiation screen.
For more detail look this thread.

Hope this fulfills your requirement.

Adam Stoller

Gothi...Faizi many thanks for your answers .
Gothi formapi is not a problem at all WFM remains a little bit mysterious

here's the sentence stating our requirement :

[The next screen gives a Yes / No option against “Review Required”.

At this stage we would want to force Authors to send their content for review (so the Yes / No options should be removed)

Editors should still have the option to select Yes or No as on occasions they may want to send their content to another editor for approval.]

Best

N

Nxues - I'm glad I was of help - but it would be nicer if you learned to spell my "name" correctly ;-)

The answer has already been provided - you need to do the reading of the WFM manual and follow the instructions for creating a customized instantiation form - and then you can utilize the FormAPI code of which you say you understand.

Nexus

Amazing GothihtGO
thanks all