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

New job link in standard version

DebSaunders

Why 'new job' link in standard version is different then professional version.
'new job' does work fine with professional interface but, if we click 'new job' link in standard interface version it give exceptions. Any idea why it is different. Where i can find more information about this?

Find more posts tagged with

Comments

motlnt

Why 'new job' link in standard version is different then professional version.
'new job' does work fine with professional interface but, if we click 'new job' link in standard interface version it give exceptions. Any idea why it is different. Where i can find more information about this?

what kind of exception are you getting?also what are you logged in as(editor/master)?
It works fine for me.

ISCBorisB

Why 'new job' link in standard version is different then professional version.
'new job' does work fine with professional interface but, if we click 'new job' link in standard interface version it give exceptions. Any idea why it is different. Where i can find more information about this?

Do you have an [thread=27422]evil twin[/thread] or just use several UIDs on DevNet?

DebSaunders

I get following exception:

"Could not find available new_job workflow templates for user Test1 (editor, ) "

even though we have specified in available_templates.cfg file still it is not finding it....available_templates.cfg settings:

'template_file name='Add Branch Groups' path='test/Add_branch_groups.wft'>
command_list>
command value='new_job' include='yes'/>
command value='all' include='no' />
/command_list>

role_list>
role value='master' include='yes' allusers='yes'/>
role value='admin' include='yes' allusers='yes'/>
role value='editor' include='yes' allusers='yes'/>
role value='all' include='no' />
/role_list>

branch_list>
branch value='^//[^/]+/default/main/nonportal/TEST' include='yes' />
branch value='all' include='no' />
/branch_list>
/template_file>'

Didn't seen anything wrong in above config settings. Any idea what is wrong?

ISCBorisB

Branch_list is what's wrong with your configuration, at least as far as CC Standard is concerned.
I've [post=128085]pointed that to you[/post] once before, so let's try one more time.

Unlike CCPro, in CCStd logged-in Contrubutor does not maintain *Location* attribute. Standard 'iw_branch'
and 'iw_workarea' WF Instantiator Tags are blank. Similar CCPro mode exists within Workflow Tab, "New Job"
widget there demonstrates the same behavior as in CCStd.

To cover it you can remove Branch Constraints altogether or modify existing Branch Regex or add another branch
tag to the branch_list (with value="$^"), etc...

DebSaunders

Why it is so different for standard version. so if iw_workarea is blank how we can get this in standard version. Where i can get more information about standard version changes.

Adam Stoller

Why it is so different for standard version. so if iw_workarea is blank how we can get this in standard version. Where i can get more information about standard version changes.

In CCPro - you are in a branch / workarea context.
In CCStd - at least from the main portal view - you are not in a branch / workarea context.

Another difference is that if you have a CGITask as your start task:
In CCPro, a new window is launched for selecting the workflow, filling in the instantiation form, and then reused for the CGITask. When you close the CGITask window you're back to your GUI.
In CCStd, the wizard runs within the TS GUI window to let you select the workflow, fill in the instantiation form, and then reused for the CGITask. When you close the CGITask window - your TS GUI is gone!

I think you can customize the CCStd interface to provide a Submit or New Job link within the workarea browsing view - which would solve the first issue - it doesn't, as far as I know, solve the second issue (which only applies if you want a CGITask as your start task)

DebSaunders

Thanks for the reply ghoti...it realy helps in deciding right things...
To customize the CCStd interface i have to recompile the interface. Is it possible to make these changes without recompiling the interface???