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

workflow validation

sunsun

can anyone tell me how to varify or debug workflows to be proper without having access to the admin privileges.

I am soon going to be working on creating workflows as an editor and dont know if i would have access to the available_templates file or the wft folder. I have not worked before in any company.

I know how to create workflows, but my main concern is how to varify if they are running properly without having access to any configuration files or wf folders and without actually running the workflow as a job.

all your help will be appreciated

Find more posts tagged with

Comments

nipper

Well

If you can't do that you will find it tought to do your job.

Someone will need to change available_templates.cfg that should be an easy change.

Do you have a dev server ? Is there is a config branch ? There should be. You could make the
changes on the config branch & then have opendeploy push it to iw-home. That is a very good
way to do it. Otherwise you will need permission to change the files directly in iw-home, even worse
if you do not have a dev server, you will make the changes on the prod server.

Make a test branch where you can do a submit. If you have an OpenDeploy step, make a new deployment that
will do a simulated deploy, so you do not get yourself in trouble.

sunsun

Thanks for your reply

You said "use open deploy to push it to iw-home." what do you mean by that? are there any files i can configure at my end without asking for any permissions from my administrator?

does an editor in any company usually have access to the configuration files? because i had heard that the editors usually dont get access to the stuff like CLTs or configuration files and folders. So i wonder how do they varify the workflows they have created.d

Before I start my job, it would help me if I know these things in advance.

Thank you again for your help

nipper

the answer is no. Unless this was setup this way before, you are hosed.

You will likely need an administrator to make a test branch for you. You will also
need permission (filesystem) to edit the files you need.

One cannot tell you how you will be able to do you job without seeing the
environment first. If this was set up well, with a config branch and a dev server,
you can easily do your job. If, on the other hand, those are not available, you
will need to have administrator or root access to change the files (or have them
change the perms for you). Help from a TS Admin will also be required.

Migrateduser

Using OpenDeploy to push the config files is a good idea but this is assuming you're able to edit files underneath <od-home>, which I'm assuming you're not able to do.

As a far less elegant but workable solution, you COULD implement a custom menu item which performs basic shell commands for you. So, you could do something like "cp file1 file2", etc. and this would seem to address your workflow issue. However, this is far less elegant, as I mentioned, and this assumes you have access to rebuild the UI -- which I can probably assume you don't have.

I'd ask myself the following questions, "What am I required to do and why aren't I given the proper tools to do my job?" -- because this is basically your situation. You need to be able to develop and test your wft files before implementing it and, from what it sounds like, you haven't been given the resources on the system that your work requires.

Dave

Current Environments:
(1,2) TS 6.5 on W2K3
(3) Vignette V7 Portal on Solaris 9

nipper

OpenDeploy is how I configure a dev server and config branch. There are many
ways to do it. The point is that a WF developer will already have a set of constraints
to work under and you will need to see them before ou can decide if you can do the job.

Post your environment when you start working & maybe we can help

Adam Stoller

You are using the terms "editor" and "admin" - do you mean these as TeamSite roles?
TeamSite roles have nothing to do with access rights in IWHOME - where changes to things like the available_templates.cfg and IWODHOME where OpenDeploy configuration files live.

If you have access to make changes in the IWHOME and IWODHOME directories - it shouldn't matter that you can only login to TeamSite as an Editor (it's still a questionable limitation, but ...) - however, if you do have this access, it would make sense to see about creating an IWHOME branch, where you could store all configuration and customizations files and use OD to deploy them from TeamSite to the local disk (as suggested). However, you would need more than "editor" access in TeamSite to create the branch and workarea for doing this.

If you're working closely with a TeamSite Administrator (not the TeamSite role - the organizational role) who *does* have "master" priveleges in TeamSite - then you can work together to get things like this done so that you can do your development work with little need to go through red-tape everytime you want to scratch your nose...

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

sunsun

hello fish

when i said editor or admin, I mean not the roles but the responsibilities of them.
I am going to start working somewhere where i am not hired for doing admin jobs but to creating templates and workflows as from what i know thats what an editors job is to create templates and workflows. For templates i know i dont need to have access to too many configuration files but for creating and testing workflows, i sure would.

thanks again