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

Customize Workflow

Bern

Does anyone know if it's possible to customize Workflow so that after leaving one form it prompts the user with another one?

Find more posts tagged with

Comments

Migrateduser

I think you'll need to go into much more explanation about what you're trying to do.

Dave

Current Environment(s):
(1) TS 6.1 SP2 on W2K3
(2) TS 6.1 SP2 on W2K

Adam Stoller

Are you talking about multiple job instantiation forms or from Job instantiation form to cgitask script form? or from cgitask script form to another cgitask script form?

The first is not supported - the second and third are supported under certain conditions (I suggest you download and read the Workflow Tutorial Supplement)

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

Bern

Well it's set up right now after finishing a particular form a script runs that makes a basic HTML form pop up. Now the issue is is that we're only able to have one instance of the script running and also that it just doesn't look right being prompted a regular HTML form while proceeding through. So I'm wondering if it's at all possible to have Workflow do this instead.

Migrateduser

What TS version are you using?
What OS are you on?
How is this pop up being called (menu item, CGI task, etc.)?
What does this form do?
Does the script only show HTML and do some backend stuff (in other words, why is there a restriction on having only one instance of it running at a time, even though this doesn't seem like it would be a big deal in the end)?

Dave

Current Environment(s):
(1) TS 6.1 SP2 on W2K3
(2) TS 6.1 SP2 on W2K

Bern

To answer you questions Dave... we are currently using version TS 6.1 SP1 on Solaris. The pop up is being called by a CGI task and all the form does is take a value from drop down list. The resritction is that since it's a CGI task it must execute from the cgi-bin and has to be shared between our test and development work areas. So simply put we're just wondering if there's any other way to do this without using a CGI task and so that there won't be this issue of having to share between work areas.

Migrateduser

If I understand correctly, you're not making use of the iw-bin directory? Many times, people prefer to put their cgitask scripts into the <iw-home>/httpd/iw-bin directory. From the WF, you don't need to specify the directory location, as this is the default location for cgi tasks. This way, you can reuse this script across all workareas on your TS instance.

Dave

Current Environment(s):
(1) TS 6.1 SP2 on W2K3
(2) TS 6.1 SP2 on W2K

Bern

We are using <iw-home>/httpd/iw-bin but we don't want both workareas using the same cgi script. One work area is development and the other is testing. Do you have any ideas of how to provide the same type of popup form without doing it this way.

Adam Stoller

I see several possibilities here - if I understand your dilemma correctly.
1) have the cgitask script determine which workarea its running from ($task->GetArea()) and if it's a "test" workarea do one thing, if it's a "non-test" workarea do something else.
2) have the wft determine which workarea its running from (__VALUE__('iw_workarea'); or prompt) and use that to determine whether or not to set $cgitask to be your "test" script or your "real" script and use __INSERT__($cgitask); for the command parameter of your cgitask definition.

If these don't seem to resolve your issue - you will probably need to be a lot more explicit and descriptive in terms of what you are trying to accomplish.

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

jbonifaci

Ideally you would have separate environments for Development and QA. That aside, another possibility is to create a Development and QA sub-directory in each of the current directories where you have scripts. All code from your Development branch would reference the scripts in the Development sub-directories and all code from your QA branch would reference the scripts in your QA sub-directories.