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

require_workarea=false is not working...

sandy123

Hi All

I am using teamsite 6.7.1, and by setting require_workarea=false in the available_templates.cfg is not working for me. It is still asking me for workarea and branch selection, when I invoke new job from workflow tab.

Does any one faced this issue before. Any clues will help ...

Thanks,
Sandeep.

Find more posts tagged with

Comments

Adam Stoller

Hi All

I am using teamsite 6.7.1, and by setting require_workarea=false in the available_templates.cfg is not working for me. It is still asking me for workarea and branch selection, when I invoke new job from workflow tab.

Does any one faced this issue before. Any clues will help ...

Thanks,
Sandeep.

If you're invoking a new job from the workflow tab - you need to prompt for workarea - so it may be doing the right thing despite the setting. More to the point though - there are very few (if any) good reasons to initiate a job from the workflow tab (IMO).

kaalraa

Hi All

I am using teamsite 6.7.1, and by setting require_workarea=false in the available_templates.cfg is not working for me. It is still asking me for workarea and branch selection, when I invoke new job from workflow tab.

Does any one faced this issue before. Any clues will help ...

Thanks,
Sandeep.

Could you please share your requirement as in which case you require to initiate a workflow without mentioning the workarea?

sandy123

My requirement is - Many of our users use the standard UI and the process of content development and deployment is like
- they invoke the new job
- Choose the workflow they want to use
- Create New Form entry by clicking the link on the tas details window also attaches new documents or pdfs to the job either by selecting import files link or attach existing file link
- Then the workflow deploys the attched file and newly created DCR's to the destination

Since they dont go to any specific workarea and invoke the WF, the workarea is not know untill they choose specific workflow. The workarea is hardcoded in each of different workflow. Since it is hardcoded in each WF, we dont want users to choose workarea when they invoke WF from workflow tab or when invoke it through standard UI.

setting require_workarea=false is working well in dev server but it is not working in Prod server. Versions and all other settings are same on both the servers.

Please let me know if I am not making myself clear.
Any ideas why it is not working in prod server while it is working in Dev server?

Adam Stoller

My requirement is - Many of our users use the standard UI and the process of content development and deployment is like
- they invoke the new job
- Choose the workflow they want to use
- Create New Form entry by clicking the link on the tas details window also attaches new documents or pdfs to the job either by selecting import files link or attach existing file link
- Then the workflow deploys the attched file and newly created DCR's to the destination

Since they dont go to any specific workarea and invoke the WF, the workarea is not know untill they choose specific workflow. The workarea is hardcoded in each of different workflow. Since it is hardcoded in each WF, we dont want users to choose workarea when they invoke WF from workflow tab or when invoke it through standard UI.

setting require_workarea=false is working well in dev server but it is not working in Prod server. Versions and all other settings are same on both the servers.

Please let me know if I am not making myself clear.
Any ideas why it is not working in prod server while it is working in Dev server?

The hard-coding of the areavpath in the workflow should obviate the need for prompting for the workarea during instantiation (I'm not sure I like the "design" of this, but that's neither here nor there).

You say it's working on DEV and not on PROD
- Are you sure the versions of the software are identical (including service packs and patches)?
- Are you sure you don't have a typo somewhere on PROD that negates the attempt to disable the prompting for the workarea?

If you're sure about both of those things - I suggest you open a case with Support.

mdang

The following description is in the available_templates.cfg.

The require_workarea attribute of the available_templates tag is implicitly set
to true. That means the workflow templates selection screen will include a
branch/workarea chooser if workarea context is not present during the workflow
instantiation. If require_workarea attribute is set to false explicitly,
workflow templates selection will ignore any branch/vpath restriction when a
workarea context is not present during workflow instantiation. Most of the out
of the box workflow template examples require the require_workarea attribute to
be true to work properly.

So it should work, just as your dev box. Make sure your prod is exactly configed as your dev.

sandy123

The version on DEV and PROD are simmilar including the service packs and patches. I dont understand why this is working on Dev server and not on prod server.

I even copied the available_templating.cfg of prod server to dev server and it worked awesome...

Not sure what other configurations i should check to see what is going wrong on the prod server. Any pointers will help.

Adam Stoller

The version on DEV and PROD are simmilar including the service packs and patches.

You say "similar"[sic] - but you don't say "identical" - how are they different?

sandy123

Yes they are identical. I think you should be able to understand what I mean to say.
THanks for clarifying.

Adam Stoller

Yes they are identical. I think you should be able to understand what I mean to say.
THanks for clarifying.

I understood what you said, not what you meant to say - I do the latter with people I've known for more than a year not with people I don't know posting in public forums.

That being said - I see two choices:

mdang

[QUOTE=ghoti]I understood what you said, not what you meant to say - I do the latter with people I've known for more than a year not with people I don't know posting in public forums.

That being said - I see two choices:

The second option is probably what support will ask you to do after you go with the first option.

sandy123

Thanks Ghoti .

I can do a iw-home directory comparison but was wondering are there any specific set of files you want me have a look or just the teamsite configuration files ?

Adam Stoller

Thanks Ghoti .

I can do a iw-home directory comparison but was wondering are there any specific set of files you want me have a look or just the teamsite configuration files ?

Personally, with a problem this strange - I'd want to know every file (ascii or binary) that's different - and for the ascii files what content is different.

If the two systems are supposed to have the same exact version on them, then the only files with differences should be customizations and configuration files - and those you should be able to look at and figure out whether the differences make sense (e.g.: hostname or IP address differences make sense)

If you find that any product files (binaries or ascii files that you're sure weren't modified locally) are different - then you have reason to suspect that the two systems aren't identical - and that might lead you to determining why this feature only works on one of them.