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

Auto Include of Config files during workflow

System

Hi Guys,

I have two scenarios.

The first one is,Whenever i choose a Dcr and submit automatically its generated page should also be selected with the worflow and the second one is based on template i need to auto add certain config files to the workflow.

Kindly advise.

Thanks

Find more posts tagged with

Comments

ravio

I respect the fact that you are trying to figure things out by yourselves, But sometimes it is best to invest in training to give you a head start and it will help you in the longer run.

The fact is that you will normally receive a very general answer to whatever you post.

This is because we don't know what your exact requirement is and can only point you in a general direction.

And to be able to translate that generalized info into specific details, you need to know what you are doing really well.

Whether you like it or not, that's my honest opinion.

Migrateduser

I respect the fact that you are trying to figure things out by yourselves, But sometimes it is best to invest in training to give you a head start and it will help you in the longer run.

The fact is that you will normally receive a very general answer to whatever you post.

This is because we don't know what your exact requirement is and can only point you in a general direction.

And to be able to translate that generalized info into specific details, you need to know what you are doing really well.

Whether you like it or not, that's my honest opinion.

I understand what u say but i am in middle of the project so not this time may before my next project i will go

Thanks

kaalraa

Hi,

I hope your DCR is getting atached automatically. Next there are some relevant question to be answered from you so that requirements would be understand easily:

1. The generated page name and path is based on certain values with in the DCR or its just a name given on a default path.

2. The config files to be attached are some default or again based on certain values. Also why you have to attach the config files to the workflow?

Hi Guys,

I have two scenarios.

The first one is,Whenever i choose a Dcr and submit automatically its generated page should also be selected with the worflow and the second one is based on template i need to auto add certain config files to the workflow.

Kindly advise.

Thanks

Migrateduser

Hi,

I hope your DCR is getting atached automatically. Next there are some relevant question to be answered from you so that requirements would be understand easily:

1. The generated page name and path is based on certain values with in the DCR or its just a name given on a default path.

2. The config files to be attached are some default or again based on certain values. Also why you have to attach the config files to the workflow?

1. Yes The generated page name and path is based on certain values with in the DCR.

2.Sorry its not config file some common xml files that need to be updated using workflow

chetansethi

Are you using customized submit workflow or standard provided by IWOV?

kaalraa

Then in case... my first solution to you is to add an external task within your workflow e.g. attach_and_populate. The task reads on the values within DCR and gets the name of generated file along with path. Also update the common xmls.

After having list of all the files, just add them all in your workflow through task object.

1. Yes The generated page name and path is based on certain values with in the DCR.

2.Sorry its not config file some common xml files that need to be updated using workflow

Migrateduser

Are you using customized submit workflow or standard provided by IWOV?

Standard provided by iWOV

chetansethi

You would need to customize your workflow and as proposed by Kaalraa you would need to add an external task which would pick all files generated out of the DCR and the config files and attach it to the workflow using the task object.

Standard provided by iWOV

JonathonG

You DO need to customize the workflow.

You do NOT need to add an external task. Within the wft file itself, you can add Perl code to handle any processing and attach the files. You'll want to look into the <files> element on your start task for attaching the files.

madmonkey

Hey, you could as Kaalraa said, go for an external task that picks up the dcr that you just submitted and generate a page and then attach that page to your workflow. This task basically should read your directory in which your dcr is, come out of it and go into the presentation dir, pick the tpl and generate the page. for generation you can use command line tool which has to be handled by a subroutine. get back if this helps. good luck !

jbonifaci

Hey, you could as Kaalraa said, go for an external task that picks up the dcr that you just submitted and generate a page and then attach that page to your workflow. This task basically should read your directory in which your dcr is, come out of it and go into the presentation dir, pick the tpl and generate the page. for generation you can use command line tool which has to be handled by a subroutine. get back if this helps. good luck !

As Jonathon just pointed out, a better solution is to do this directly in the wft and not add an external task.

~Jeff

kaalraa

Still, my suggestion would remain the same to use an external task. As it has much more capabilities (also with ease) than writing the code within the wft itself.

As Jonathon just pointed out, a better solution is to do this directly in the wft and not add an external task.

~Jeff

jbonifaci

Still, my suggestion would remain the same to use an external task. As it has much more capabilities than writing the code within the wft itself.

I'd be very curious as to what those extra capabilities are... Could you please elaborate...?