Hi I disabled all the viewoption actionlist items.viewoptions actionlist=";"But the user submit the DCR through a WF and he will get an emailto verify the DCR before publishing. At this stage I want to enable viewoptions [font=Times New Roman][color=#000000]actionlist="preview;"[/font][/color]How to achieve this ?Thanks -Vin
Why disable everything to begin with? I generally leave Save and Preview and remove everything else (e.g.: Save As, Generate, etc.) - this allows for fairly normal operations to take place both outside and inside the context of a workflow, and allow the workflow to control the generate process.
In my PT , am using iwpt_get_flag_param('-oprefix') , The WF uses the DB scripts to update the database, it also generates the html files . After running the WF and they preview , it will point to the staging web server , where they can see the actual generated pages ( which is updated with db)
If they preview directly from TS ( without running the WF), it will still point to the staging web server , but the db will not update at that time , I am trying some way to avoid preview before running the WF
Thanks
-Vin
In my PT , am using iwpt_get_flag_param('-oprefix') , The WF uses the DB scripts to update the database, it also generates the html files . After running the WF and they preview , it will point to the staging web server , where they can see the actual generated pages ( which is updated with db) If they preview directly from TS ( without running the WF), it will still point to the staging web server , but the db will not update at that time , I am trying some way to avoid preview before running the WF Thanks -Vin
I don't think it is possible to dynamically change the viewoptions in templating.cfg. Either you have to entirely disable the preview button or entirely enable it. Think of some other alternative of giving the user option to preview. May be in the workflow only. Just an idea.
I've done this a lot of times - it requires having another environment set up - e.g.: a Preview environment as well as a Production environment (and sometimes a Staging environment too) - the Edit DCR Preview option is for viewing the generated output outside the context of the web server / app server - the workflow takes care of deploying the files (and metadata) to the Preview environment and provides a means for the reviewers to access the file(s) in the Preview environment for their review, and when everything is approved the files get deployed to the Production environment (or to the Staging environment until some later process comes along and releases approved changes to the Production environment).
